abfbe5d54d
Today the sriov qos service plugin blindly blocks creating ports with minimum bandwidth qos and with direct_physical vnic_type. This was originally added when only dataplane enforcement was the scope of the qos service plugin. However in the last many releases we created placement enforcement for this qos rule regardless of the vnic_type. So now blindly blocking the port creation is now preventing using the placement enforcement for this rule for direct_physical ports. This patch removes this limitation by marking minimum bandwidth as supported rule for the sriov qos service plugin. The limitation that data plane enforcement is not supported for this rule remains. The agent will not even try to apply any kind of rules to these ports as port binding is not forwarded for the sriov agent at all. The documentation is extended to explain that placement enforcement now works while data plane enforcement still not supported. This is somewhat similar to the case when the support for egress direction is added to the minimum bandwidth rule, while the sriov data plane enforcement was not (could not) been implemented for this direction in the sriov agent. Today the sriov agent simply ignores the egress direction rules in the minimum bandwidth qos rule during applying the data plane enforcement. Closes-Bug: #1949877 Change-Id: I20ad32eac414ff90b551bff940d92cbcfa848101
OpenStack Neutron
Neutron is an OpenStack project to provide "network connectivity as a service" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., Nova).
To learn more about neutron:
- Documentation: https://docs.openstack.org/neutron/latest/
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
- Source: https://opendev.org/openstack/neutron
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute, please read the CONTRIBUTING.rst file.