Merge "Do not block qos for direct-physical ports"

This commit is contained in:
Zuul 2022-01-11 17:34:01 +00:00 committed by Gerrit Code Review
commit 32e9aae234
4 changed files with 16 additions and 1 deletions

View File

@ -177,6 +177,9 @@ supported:
* Open vSwitch (``openvswitch``) vnic_types: ``normal``, ``direct``
* SR-IOV (``sriovnicswitch``) vnic_types: ``direct``, ``macvtap``
From the Yoga release the ``direct-physical`` vnic_type is now marked supported
for the SR-IOV (``sriovnicswitch``) agent.
neutron-server config
~~~~~~~~~~~~~~~~~~~~~

View File

@ -85,6 +85,10 @@ traffic directions (from the VM point of view).
direction and only for networks without tunneled traffic (only VLAN and
flat network types).
.. note:: The SR-IOV agent does not support dataplane enforcement for ports
with ``direct-physical`` vnic_type. However since Yoga the Placement
enforcement is supported for this vnic_type too.
.. table:: **Neutron backends, supported directions and enforcement types for Minimum Packet Rate rule**
============================ ========================== ==================== ============== =====

View File

@ -50,7 +50,8 @@ class SRIOVNICSwitchDriver(base.DriverBase):
name='sriovnicswitch',
vif_types=[portbindings.VIF_TYPE_HW_VEB],
vnic_types=[portbindings.VNIC_DIRECT,
portbindings.VNIC_MACVTAP],
portbindings.VNIC_MACVTAP,
portbindings.VNIC_DIRECT_PHYSICAL],
supported_rules=SUPPORTED_RULES,
requires_rpc_notifications=True)

View File

@ -0,0 +1,7 @@
---
features:
- |
Neutron now supports the placement enforcement for the guaranteed minimum
bandwidth QoS rule type with direct-phyisical vnic_type as well. The data
plane enforcement of such rule and vnic_type combination is still not
supported.