|
|
| (36 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | | + | merge back to: |
| − | ===API for whitelist===
| + | https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support |
| − | 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.
| |
| − | | |
| − | ===Use cases ===
| |
| − | | |
| − | ====admin inspect PCI devices (discuss)====
| |
| − | admin might want to know if there are some pci device avaliable to use, eventhough admin should know such infomation but if the inspect works, it's convenience. there is 2 methods to implemt inspect.
| |
| − | # via database
| |
| − | currently pci device in the databse is after filter, if want inpect the deive on node, we should let all device going in to database. so problem is db will too large then eventually slow down query, became a scale problem. another problem is whitelist take effective the libvirt layer not in compute node (pci traker), this becuase same thing, reduce un-necessary infomation.
| |
| − |
| |
| − | # via RPC call
| |
| − | for inspect one node, use RPC call to get reulst from a node, show it to admin. this need investigate more.
| |
| − | | |
| − | ====admin create global groups ====
| |
| − | suppose data center have some identical hosts with same configration, so the address for same device will have same address, then amdin want group the address '0000:01:00:7' and '0000:01:01:7' to a group say 'QucikAssist'
| |
| − | | |
| − | than admin can create the white list in one cmd:
| |
| − | nova pci-config create white-list set description='xx' address='0000:01:00:7','0000:01:01:7' group=''QuickAssist'
| |
| − | the API call then will be :
| |
| − | create/v2/{tenant_id}/os-pci-config/white-list
| |
| − | with data:
| |
| − | { 'group':'QuickAssist', 'address': ['0000:01:01:7', '0000:01:00:7'], 'description': "xxx"}
| |
| − | | |
| − | ====admin create per host groups ====
| |
| − | say data center have a special powerfull machine with a powerfull PCI 'QucikAssist' card located at '0000:01:00:7', admin want group it's VF to 'PowerDecode'.
| |
| − | | |
| − | create the white list in one cmd:
| |
| − | nova pci-config create white-list compute-node-id=<hostid> description='xx' address= '0000:01:00:7' group=''PowerDecode'
| |
| − | the API call then will be :
| |
| − | create/v2/{tenant_id}/os-pci-config/white-list/
| |
| − | with data:
| |
| − | { 'group':'PowerDecode', 'address':'0000:01:00:7', 'description': "xxx" , 'compute-node-id':'hostid'}
| |
| − | | |
| − | ====Check if white list work well ====
| |
| − | after about 30 seconds, white list take effect, so admin want to check is the white list work corretly, so use this:
| |
| − | ( this API is covered by another bp(list it here for a full picture view): https://blueprints.launchpad.net/nova/+spec/pci-api-support )
| |
| − | | |
| − | nova pci-list node_id
| |
| − | | |
| − | ====admin configures alias that request device from a specific group====
| |
| − | | |
| − | to allocate the device from a group, you need to create alias for it firstly, the flow is in same way as white list,except alias always global.
| |
| − | | |
| − | create the alias in one cmd:
| |
| − | nova pci-config create alias set name='GetMePowerfulldevice' group=''PowerDecode'
| |
| − | the API call then will be :
| |
| − | create/v2/{tenant_id}/os-pci-config/alias
| |
| − | with data:
| |
| − | { 'group':'PowerDecode', 'name': "GetMePowerfulldevice"}
| |
| − | | |
| − | ====admin configures flavours use above flavor ====
| |
| − | nova flavor-key m1.small set pci_passthrough:alias=GetMePowerfulldevice:2
| |
| − | | |
| − | | |
| − | ====admin boot VM with this flavours ====
| |
| − | nova boot mytest --flavor m1.small --image=cirros-0.3.1-x86_64-uec
| |
| − | | |
| − | | |
| − | ====admin want to modify a white-list ====
| |
| − | if want to chang a white list, ie, want use just intel's accelerator, and remove a specify address from group:
| |
| − | nova pci-config list white-list
| |
| − | | |
| − | to get detailed infomation about this whitelist:
| |
| − | nova pci-config list white-list 01
| |
| − | | |
| − | we get id of white-list we want modify, say 01
| |
| − | nova pci-config white-list 01 delete address= '0000:01:01:7'
| |
| − | nova pci-config white-list 01 update vonder_id= '8086'
| |
| − | | |
| − | these cmd then convert to API call:
| |
| − | get/white-list/
| |
| − | get/white-list/01
| |
| − | delete/white-list/01
| |
| − | | |
| − | ====admin want to delete a whole white-list ====
| |
| − | if want to chang delete one white-list, first get it UUID:
| |
| − | nova pci-config list white-list
| |
| − |
| |
| − | then delete it:
| |
| − | nova pci-config delete white-list 01
| |
| − | | |
| − | these cmd then convert to API call:
| |
| − | get/white-list/
| |
| − | delete/white-list/01
| |
| − |
| |
| − | | |
| − | ====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 ====
| |
| − | # the config file for alias and whitelist defination is going to deprecated.
| |
| − | # if database is not NULL , configration is ommit and given deprecated warning.
| |
| − | # 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 : data base of this k,v pair
| |
| − | UUID: which alias/whitelist k,v belong to
| |
| − | compute_node_id: easy to query per host configration, NULL for global configration
| |
| − | object : easy to query by object whitelist/alias
| |
| − | key
| |
| − | value
| |
| − | value_type: string, RE, list # for further enhancement
| |
| − | }
| |
| − | | |
| − | alias is always 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.
| |
