PCI configration Database and API
nova PCI passthough going to support SRIOV and whitelist became local to host, it's better to get configration into DB and provide API for config the PCI.
Whiteboard
Hi, johnthetubaguy
per your suggest, i merge this bp back to
https:/
and all user cases also move to:
https:/
--Yongli
Can we please include use cases for the APIs, I am not sure I get the flow.
Maybe split things into:
* admin lists PCI devices
* admin uses list to create groups and attach labels as required
* 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)
Please expand on the use cases, and document the API calls for each step.
Can we also cover how we will deprecate the old config and replace with the API, I think just use API data, but if its empty use the stuff from the config, with a view to remove config after Icehouse?
You have two blueprints, but the two blueprints I think we should have are:
* enhance PCI passthrough to support all the groups we need for neutron config (ensure groups can be used in the flavour, etc), this includes the new admin APIs
* use the above support to integrate this with neutron (describe how the mapping between PCI device and neutron port happens)
--johnthetubaguy
