Skip to content

Commit 9e0c9dd

Browse files
Zuulopenstack-gerrit
authored andcommitted
Merge "[doc] Document the L3 QoS support in Neutron" into stable/2025.1
2 parents c14fb99 + c8af0f1 commit 9e0c9dd

File tree

1 file changed

+66
-7
lines changed

1 file changed

+66
-7
lines changed

doc/source/admin/config-qos.rst

Lines changed: 66 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -138,19 +138,63 @@ Valid DSCP mark values are even numbers between 0 and 56, except 2-6, 42, and
138138
L3 QoS support
139139
~~~~~~~~~~~~~~
140140

141-
The Neutron L3 services have implemented their own QoS extensions. Currently
142-
only bandwidth limit QoS is provided. This is the L3 QoS extension list:
141+
The Neutron L3 services have implemented their own QoS extensions. It is
142+
possible to apply QoS policies to the floating IPs and to the routers; in the
143+
last one (routers), the QoS policy will be applied on the gateway port.
143144

144-
* Floating IP bandwidth limit: the rate limit is applied per floating IP
145-
address independently.
145+
The rule support depends on the ML2 backend used.
146+
147+
148+
ML2/OVS
149+
-------
150+
151+
The ML2/OVS L3 QoS supports only rate limit rules:
152+
153+
* Floating IP bandwidth limit: rate limit is applied per floating IP address
154+
independently.
146155

147156
* Gateway IP bandwidth limit: the rate limit is applied in the router namespace
148157
gateway port (or in the SNAT namespace in case of DVR edge router). The rate
149158
limit applies to the gateway IP; that means all traffic using this gateway IP
150159
will be limited. This rate limit does not apply to the floating IP traffic.
151160

152161

153-
L3 services that provide QoS extensions:
162+
ML2/OVN
163+
-------
164+
165+
The ML2/OVN L3 QoS supports both rate limit and DSCP rules. Both floating IP
166+
and gateway port QoS policies are applied using the QoS metering rules.
167+
168+
* Floating IP: the traffic should match the gateway port and the floating IP
169+
address. The port can be centralized or distributed.
170+
171+
* Gateway port: the traffic should match the gateway chassis port.
172+
173+
174+
Because both floating IP and router can have QoS policies and both QoS policies
175+
will match the same traffic, the floating IP policy has a higher priority and
176+
will match this one only. In case of having port policies, that will apply to
177+
the virtual machine private port, the private port rule will be applied first.
178+
This is the QoS rules precedence and result:
179+
180+
* Rate limit rules: if both private port QoS and router/floating IP rules are
181+
applied, because both will be executed, the minimum rate limit value will
182+
apply.
183+
184+
* DSCP rules: if both private port QoS and router/floating IP rules are
185+
applied, the router/floating IP DSCP mark will be applied on the egress
186+
packet.
187+
188+
189+
.. note::
190+
191+
In case of having both router and floating IP QoS policies, the floating IP
192+
QoS policy has precedence always over the router QoS one. See `[OVN] Change
193+
the OVN QoS rule priority for floating IPs <https://review.opendev.org/q/If01a8783ac998b2a1f1249ab6f555dd1a5148ea8>`_.
194+
195+
196+
L3 services that provide QoS extensions
197+
---------------------------------------
154198

155199
* L3 router: implements the rate limit using `Linux TC
156200
<https://man7.org/linux/man-pages/man8/tc.8.html>`_.
@@ -162,16 +206,31 @@ L3 services that provide QoS extensions:
162206
The following table shows the L3 service, the QoS supported extension, and
163207
traffic directions (from the VM point of view) for **bandwidth limiting**.
164208

165-
.. table:: **L3 service, supported extension, and traffic direction**
209+
.. table:: **L3 service, supported extension and traffic direction for
210+
bandwidth limiting**
166211

167212
==================== =================== ===================
168-
Rule \\ L3 service L3 router OVN L3
213+
L3 service L3 router OVN L3
169214
==================== =================== ===================
170215
Floating IP Egress \\ Ingress Egress \\ Ingress
171216
Gateway IP Egress \\ Ingress Egress \\ Ingress
172217
==================== =================== ===================
173218

174219

220+
The following table shows the L3 service, the QoS supported extension, and
221+
traffic directions (from the VM point of view) for **DSCP marking**.
222+
223+
.. table:: **L3 service, supported extension and traffic direction for
224+
DSCP marking**
225+
226+
==================== =========== ========
227+
L3 service L3 router OVN L3
228+
==================== =========== ========
229+
Floating IP - Egress
230+
Gateway IP - Egress
231+
==================== =========== ========
232+
233+
175234
Configuration
176235
~~~~~~~~~~~~~
177236

0 commit comments

Comments
 (0)