openstack
/
neutron
Code Issues Proposed changes

Add both directions for minimum bw rule in doc 

Changed QoS backend/rule support table in devref documentation to show
that Minimum Bandwidth rule can support both Egress and Ingress
directions in case of placement based enforcement.
Added a new table to show which directions are supported for Minimum
Bandwidth rule by the network backends, and how that depends on the
enforcement type (dataplane or placement).

Change-Id: I97ab4815d134d306917a84a7b308b734d6db2dd2
Depends-On: https://review.openstack.org/580387
Partial-Bug: #1578989
See-Also: https://review.openstack.org/502306 (nova spec)
See-Also: https://review.openstack.org/508149 (neutron spec)
This commit is contained in:
Lajos Katona 2018-07-16 15:31:44 +02:00
parent 360fde9f88
commit f849eba286
1 changed files with 25 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
doc/source/contributor/internals/quality_of_service.rst
View File

@ -299,17 +299,33 @@ 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 | - |
+----------------------+----------------+----------------+----------------+
| DSCP Marking | Egress | - | Egress |
+----------------------+----------------+----------------+----------------+
+----------------------+--------------------+--------------------+--------------------+
| 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+) | |
+----------------------------+----------------+----------------+----------------+
Open vSwitch