Since inspector already adds it in capabilities field, it should be fine for OOB inspection to add the pci data to capabilities insted of any other field. It will essentially follow the same spec as implemented in inspector. https://github.com/openstack/ironic-inspector-specs/blob/master/specs/generic-pci-resource.rst
SO ideally it would be like this: 1. Add a new section [pci] in ironic.conf 2. Add pci_alias example in ironic.conf under [pci] as given in https://docs.openstack.org/admin-guide/compute-pci-passthrough.html and https://github.com/openstack/ironic-inspector/blob/7fff708b2cdd61938fe1ea41303a8b71cebdba02/example.conf#L705-L714 3. The inspection returns the list of pci devices based on aliases in ironic.conf. 4. ironic updates the node.properties as node.properties.capabilities = "alias1:count1,alias2:count2"
Since inspector already adds it in capabilities field, it should be fine for OOB inspection to add the pci data to capabilities insted of any other field. It will essentially follow the same spec as implemented in inspector. https:/ /github. com/openstack/ ironic- inspector- specs/blob/ master/ specs/generic- pci-resource. rst
SO ideally it would be like this: /docs.openstack .org/admin- guide/compute- pci-passthrough .html and https:/ /github. com/openstack/ ironic- inspector/ blob/7fff708b2c dd61938fe1ea413 03a8b71cebdba02 /example. conf#L705- L714 .capabilities = "alias1: count1, alias2: count2"
1. Add a new section [pci] in ironic.conf
2. Add pci_alias example in ironic.conf under [pci] as given in https:/
3. The inspection returns the list of pci devices based on aliases in ironic.conf.
4. ironic updates the node.properties as node.properties