This service is missing in both SRIOV files with and without Opendaylight.
The following environment file:
Does not contain the NeutronSriovHostConfig as it does:
This service is required to perform operations on the host in order to configure SRIOV capable NICs.
The upstream fix is on its way:
Ricky, please provide doc text of what needs to be manually done to make it work in GA. The fix will go in z1.
"In order to configure SRIOV properly on the compute nodes, in an OpenDaylight environment, we would need to make sure the following services are present in an environment file:
There is an environment file named neutron-opendaylight-sriov.yaml in:
where the user should add the NeutronSriovHostConfig service into the resource registry section. So the environment file would look like:
# A Heat environment that can be used to deploy OpenDaylight with SRIOV
# This file is to be used with neutron-opendaylight.yaml
# Add PciPassthroughFilter to the scheduler default filters
# Number of VFs that needs to be configured for a physical interface
# - devname: "ens20f2"
# physical_network: "datacentre"
Both patches for master and Queens have landed upstream:
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.
If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".
To add draft documentation text:
* Select the documentation type from the "Doc Type" drop down field.
* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
*** Bug 1579137 has been marked as a duplicate of this bug. ***