d860109bf6
Now supported_vnic_types is hardcoded to the mechanism drivers, but that can depend on several factors, like type of the NIC, admin decision, etc. With this patch we put the right to decide which vnic types are supported for ovs agent into the hands of the admin, by allowing blacklisting items from the mechanism driver specific list. Background: http://eavesdrop.openstack.org/meetings/neutron_qos/2018/ neutron_qos.2018-07-31-15.00.log.html#l-58 Change-Id: Iad9e2e966df53b4164d2a56a93215c69825b5241 Partial-Bug: #1578989 See-Also: https://review.openstack.org/502306 (nova spec) See-Also: https://review.openstack.org/508149 (neutron spec)
10 lines
363 B
YAML
10 lines
363 B
YAML
---
|
|
other:
|
|
- |
|
|
Add new configuration group ``sriov_driver`` and new configuration option
|
|
under it ``vnic_type_blacklist``, to make the previously hardcoded
|
|
``supported_vnic_types`` parameter of the SriovNicSwitchMechanismDriver
|
|
configurable.
|
|
The ``vnic_types`` listed in the blacklist will be removed from the
|
|
supported_vnic_types list.
|