Difference between revisions of "PCI configration Database and API"

Revision as of 01:47, 6 December 2013

API for whitelist

not only the whitelist, the alias API also meaningful for administrator's pespective. the horizon could utilized the alias db to find what kind of device is avaliable to the tenants, and these configration more reasonable in form of API.

white list/ alias on demand is all some kind of (k, v) pairs, PCI API can exploit this to achive high flexibility.

and the group key configration is kind of policy for PCI and won't change rapidly, it's hould stay in the config file.

User cases

admin inspect PCI devices (discuss)

there is 2 method to implemt inspect

1. DB : db will too large, whitelist in the libvirt not pci traker
2. RPC call:

admin uses list to create groups and attach labels as required

nova pci-list node_id

( this API is covered by another bp(list it here for a full picture view): https://blueprints.launchpad.net/nova/+spec/pci-api-support )

admin configures flavours that add PCI devices from a specific group

user requests SRIOV

or other PCI passthrough with similar thing (I want to see what data is stored in neutron vs nova here)

transite config file to API

1. the config file for alias and whitelist defination is going to deprecated.
2. if database is not NULL , configration is ommit and given deprecated warning.
3. if database is NULL, config if read from the file, also given a deprecated notice, which will be remove start from next release.

with this solution, we move pci config from file to API.

DB for pci configration

  talbe: pci_config{
               id 
               compute_node_id 
               object : whitelist/alias/group on demand
               key 
               value
               value_type:  string, RE, list  # for further enhancement 
           }

alias and on-demand group key is global.

DB API：

   pci_config_get(context, obj_name):

   pci_config_get_by_node(context, obj_name, node_id):

   pci_config_update(context, obj_name, node_id, vlaues):
       update the one object one time, ie, the white list on host "A":  pci_config_update(context, 'whitelist', "A", {"vendor_id":"v1", "proudect_id":"p1", "address":"a1"  }):

PCI releated Objects

  Objects: white list/ alias/ group keys(on demand grop)
  objects property:  sets of k,v
   

API interface

   config-object-name:  whitelist/alias/group

   GET/v2/​{tenant_id}​/os-pci-config
    show the pci configraion objects name.
    {"pci_config": ['alias', 'whitelist', 'group']}

   GET/v2/​{tenant_id}​/os-pci-config/{config-object-name}
   show the pci configraion object's detail
    i.e {config-object-name} is pci_alias:
     {"pci_alias": [{'product_id':'8086', 'group':'nic-g1', 'compute-node-id':""}]}

   GET/v2/​{tenant_id}​/os-pci-config/{config-object-name}/{compute-node-id'}
   show the pci configraion object's detail
    i.e {config-object-name} is pci_whitelist:
     {"pci_whitelist": {'product_id':'8086', 'group':'nic-g1', 'compute-node-id':"3"}}

   PUT/v2/​{tenant_id}​/os-pci-config/{config-object-name}/{compute-node-id}
   ie.   i.e {config-object-name} is pci_whitelist:
    {"pci_whitelist": {'product_id':'8086', 'address':'a1' , 'group':'nic-g1'}}
   PUT/v2/​{tenant_id}​/os-pci-config/{config-object-name}/
   change a global configration. 
   
   DELETE/v2/​{tenant_id}​/os-pci-config/{config-object-name}/{compute_node_id}
   DELETE/v2/​{tenant_id}​/os-pci-config/{config-object-name}/

  UPDATE//v2/​{tenant_id}​/os-pci-config/{config-object-name}/
  UPDATE//v2/​{tenant_id}​/os-pci-config/{config-object-name}/{compute_node_id}
   make config 'config-object-name' take effect.