[openstack-dev] [ironic][nova] Suggestion required on pci_device inventory addition to ironic and its subsequent changes in nova
Nisha Agarwal
agarwalnisha1980 at gmail.com
Wed Apr 5 17:33:38 UTC 2017
Hi,
I suggested to add few pci devices related attributes to ironic
inspection(out-of-band as well inband).
https://review.openstack.org/#/c/338138.
I got the suggestion to convert them to standard pci device format which
nova understands. For example( as given in Nova code):
[{"count": 5, "vendor_id": "8086", "product_id": "1520",
"extra_info":'{}'}],
For above to be supported for ironic scheduling, we will require changes at
two places:
1. nova - This should require a small code changes as pci_passthrough
filter already exists in nova. The ironic virt driver should be able to
consume the pci_device structure from ironic node/database and pass it on
to scheduler for scheduling and it should add pci_passthrough filter in
ironic nodes filter list.
2. ironic - this definitely needs a spec which will suggest to add the
pci_device data structure to ironic node.
The ironic side work may take some time but Nova side looks to be a small
change. IMO we can have the nova side changes and ironic database changes
(to add pci_device field) parallely.
Inspection can populate that new pci_device field for the node to get
scheduled.
AFAIK, ironic-inspector already has the plugin to discover pci devices in
the format nova has it today. If we get the scheduling enabled based on
pci_devices for ironic nodes, then inspector can write this data to ironic
node object by default.
What do you people think on this idea? Does it make sense? If its worth to
do this way i can own up this work.
Regards
Nisha
--
The Secret Of Success is learning how to use pain and pleasure, instead
of having pain and pleasure use you. If You do that you are in control
of your life. If you don't life controls you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170405/df8b5ea4/attachment.html>
More information about the OpenStack-dev
mailing list