Validate pci_passthrough_whitelist when starting n-cpu
Loading up CONF.pci_passthrough_whitelist in the Whitelist
object performs a bunch of validation and can fail in several
different ways (invalid json, invalid values, invalid combinations
of keys, devices not found, etc). This happens today when
creating the PciDevTracker in the ResourceTracker when updating
available resources. If the configuration is bad, it kills the
periodic task to update available resources on the compute node.
We should just load up the pci_passthrough_whitelist (if set)
when starting the nova-compute service so we can fail fast and
kill the service on any misconfiguration rather than run with
a broken service.
Reviewed: https:/ /review. openstack. org/342301 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=3a61ae35d4b 713f423219c7b71 4126e1584694e8
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3a61ae35d4b713f 423219c7b714126 e1584694e8
Author: Matt Riedemann <email address hidden>
Date: Thu Jul 14 13:37:05 2016 -0400
Validate pci_passthrough _whitelist when starting n-cpu
Loading up CONF.pci_ passthrough_ whitelist in the Whitelist
object performs a bunch of validation and can fail in several
different ways (invalid json, invalid values, invalid combinations
of keys, devices not found, etc). This happens today when
creating the PciDevTracker in the ResourceTracker when updating
available resources. If the configuration is bad, it kills the
periodic task to update available resources on the compute node.
We should just load up the pci_passthrough _whitelist (if set)
when starting the nova-compute service so we can fail fast and
kill the service on any misconfiguration rather than run with
a broken service.
Change-Id: If50fb837b49004 2bb5ef20e9ad843 b28f871a44e
Closes-Bug: #1603034