6e4f3df557
As part of Debian migration, the sysinv procedure to check DPDK
compatibility for each host interface was also updated in order to make
it customizable in case one would like to use other virtual switch than
the delivered OVS with DPDK support [1].
For other virtual switches, that might or not rely on DPDK, the ELF
target that sysinv uses to verify interfaces compatibility must be
customizable and the query_pci_id script is already able to use custom
values [2].
This change adds to puppet the system configuration that will write, if
defined, the correct value for the ELF path. This platform parameter can
be overridden on the hiera data so puppet will update sysinv.conf
accordingly.
For now, when deploying StarlingX with vswitch_type=ovs-dpdk we will
override it to the query_pci_id script default value (i.e., the
/usr/sbin/ovs-vswitchd ELF) using the respective sysinv puppet module
and let it as an example for anyone that is later using a different
vswitch which requires this customization [3].
[1] https://review.opendev.org/c/starlingx/config/+/872979
[2]
|
||
|---|---|---|
| .. | ||
| puppet-dcdbsync | ||
| puppet-dcmanager | ||
| puppet-dcorch | ||
| puppet-fm | ||
| puppet-mtce | ||
| puppet-nfv | ||
| puppet-patching | ||
| puppet-smapi | ||
| puppet-sshd | ||
| puppet-sysinv | ||
| tox.ini | ||