QoS rules

Review the Quality of Service (QoS) rule types for defining network policies.

The rule types include the following.

Minimum bandwidth (minimum_bandwidth)
Provides minimum bandwidth constraints on certain types of traffic. If implemented, best efforts are made to provide no less than the specified bandwidth to each port on which the rule is applied.
Bandwidth limit (bandwidth_limit)
Provides bandwidth limitations on networks, ports, floating IPs (FIPs), and router gateway IPs. If implemented, any traffic that exceeds the specified rate is dropped.
DSCP marking (dscp_marking)
Marks network traffic with a differentiated services code point (DSCP) value.
Minimum packet rate (minimum-packet-rate)
Provides minimum rate of packet transmission constraints on certain types of traffic. If implemented, best efforts are made to provide no less than the specified rate of packet transmission to each port on which the rule is applied. Currently, only placement enforcement is supported.

QoS policies can be enforced in various contexts, including virtual machine instance placements, floating IP assignments, and gateway IP assignments.

Depending on the enforcement context and on the mechanism driver you use, a QoS rule affects egress traffic (upload from instance), ingress traffic (download to instance), or both.

Note

In ML2/OVN deployments, you can enable minimum bandwidth and bandwidth limit egress policies for hardware offloaded ports. You cannot enable ingress policies for hardware offloaded ports. For more information, see Enable QoS policy capabilities in the Networking service.

Table 1. Supported traffic direction by driver (all QoS rule types)

Rule [1]

Supported traffic direction by mechanism driver

ML2/SR-IOV

ML2/OVN

Minimum bandwidth

Egress only

Egress only [2]

Bandwidth limit

Egress only [3]

Egress and ingress

DSCP marking

N/A

Egress only [4]

[1] RHOSO does not support QoS for trunk ports.

[2] In ML2/OVN deployments, minimum bandwidth rules are enforced in the physical device. You cannot configure this enforcement on bond interfaces.

[3] The mechanism drivers ignore the max-burst-kbits parameter because they do not support it.

[4] ML2/OVN does not support DSCP marking on tunneled protocols.

Table 2. Supported traffic direction by driver for placement reporting and scheduling (minimum bandwidth only)

Enforcement type

Supported traffic by direction mechanism driver

ML2/SR-IOV

ML2/OVN

Placement

Egress and ingress

Technology Preview [1]

[1] See OSPRH-507.

Table 3. Supported traffic direction by driver for enforcement types (bandwidth limit only)

Enforcement type

Supported traffic direction by mechanism driver

ML2/OVN

Floating IP

Egress and ingress

Gateway IP

Egress and ingress