b184558ab6
In I77650be5f04775a72e2bdf694f93988825a84b72 we added vnic_type direct to the ovs mechanism drivers supported vnic_types. This cause problems when working with ovs and sriovnicswitch mechanism drivers in that order. In this case the ovs will bind the direct port instead of the sriovnicswitch. This change make ovs mech driver to bind the direct port only if user requested --binding-profile '{"capabilities": ["switchdev"]}' in the direct port if a user don't request this capability the SR-IOV legacy NIC mode is used. When enable-sriov-nic-features will be implemented in nova and libvirt will expose the switchdev capability then nova will be able to select a host which supports SR-IOV nic with switchdev mode. [1] - https://review.openstack.org/#/c/435954/11/specs/pike/approved/enable-sriov-nic-features.rst [2] - https://www.redhat.com/archives/libvir-list/2017-August/msg00583.html Closes-Bug: #1713590 Change-Id: I0b5f062bcbf02381bdf4f694fc039f9bb17a2db5 |
||
---|---|---|
.. | ||
agent | ||
mech_driver | ||
__init__.py |