openstack
/
neutron
Code Issues Proposed changes

Remove duplicate QoS backend support table

Browse Source 
Remove the duplicated QoS supported rules and directions from
contributor/internals/quality_of_service page as the table is already in
admin/config-qos page.

Change-Id: I927b90877afb8bfeedb9b9ed0327650780972852
changes/24/705724/2
elajkat 3 years ago
parent f73f39f2cf
commit a1d65ba210
2 changed files with 27 additions and 40 deletions
Show Stats Download Patch File Download Diff File

32
doc/source/admin/config-qos.rst
Unescape View File

@ -49,20 +49,34 @@ traffic directions (from the VM point of view).
.. table:: **Networking back ends, supported rules, and traffic direction**
==================== =================== ================ ===================
Rule \\ back end Open vSwitch SR-IOV Linux bridge
==================== =================== ================ ===================
Bandwidth limit Egress \\ Ingress Egress (1) Egress \\ Ingress
Minimum bandwidth Egress (2) Egress -
DSCP marking Egress - Egress
==================== =================== ================ ===================
==================== ======================= ======================= ===================
Rule \\ back end Open vSwitch SR-IOV Linux bridge
==================== ======================= ======================= ===================
Bandwidth limit Egress \\ Ingress Egress (1) Egress \\ Ingress
Minimum bandwidth Egress \\ Ingress (2) Egress \\ Ingress (2) -
DSCP marking Egress - Egress
==================== ======================= ======================= ===================
.. note::
(1) Max burst parameter is skipped because it is not supported by the
IP tool.
(2) Only for physical bridges (tenant networks, provider networks), tunneled
traffic is not shaped yet.
(2) Placement based enforcement works for both egress and ingress directions,
but dataplane enforcement depends on the backend.
.. table:: **Neutron backends, supported directions and enforcement types for Minimum Bandwidth rule**
============================ ==================== ==================== ==============
Enforcement type \ Backend Open vSwitch SR-IOV Linux Bridge
============================ ==================== ==================== ==============
Dataplane - Egress (1) -
Placement Egress/Ingress (2) Egress/Ingress (2) -
============================ ==================== ==================== ==============
.. note::
(1) Since Newton
(2) Since Stein
In the most simple case, the property can be represented by a simple Python
list defined on the class.

35
doc/source/contributor/internals/quality_of_service.rst
Unescape View File

@ -295,37 +295,10 @@ interface:
* SR-IOV (QosSRIOVAgentDriver);
* Linux bridge (QosLinuxbridgeAgentDriver).
Table of Neutron backends, supported rules and traffic direction (from the VM
point of view)
::
+----------------------+--------------------+--------------------+--------------------+
| Rule \ Backend | Open vSwitch | SR-IOV | Linux Bridge |
+----------------------+--------------------+--------------------+--------------------+
| Bandwidth Limit | Egress/Ingress | Egress (1) | Egress/Ingress |
+----------------------+--------------------+--------------------+--------------------+
| Minimum Bandwidth | Egress/Ingress (2) | Egress/Ingress (2) | - |
+----------------------+--------------------+--------------------+--------------------+
| DSCP Marking | Egress | - | Egress |
+----------------------+--------------------+--------------------+--------------------+
(1) Max burst parameter is skipped because it's not supported by ip tool.
(2) Placement based enforcement works for both egress and ingress directions,
but dataplane enforcement depends on the backend.
Table of Neutron backends, supported directions and enforcement types for
Minimum Bandwidth rule
::
+----------------------------+----------------+----------------+----------------+
| Enforcement type \ Backend | Open vSwitch | SR-IOV | Linux Bridge |
+----------------------------+----------------+----------------+----------------+
| Dataplane | - | Egress | - |
| | | (Newton+) | |
+----------------------------+----------------+----------------+----------------+
| Placement | Egress/Ingress | Egress/Ingress | - |
| | (Stein+) | (Stein+) | |
+----------------------------+----------------+----------------+----------------+
For the Networking back ends, QoS supported rules, and traffic directions
(from the VM point of view), please see the table:
`Networking back ends, supported rules, and traffic direction
<../../admin/config-qos.html#id1>`_.
Open vSwitch

Write Preview
Loading…
Cancel
Save