-
Feature
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
False
-
-
False
-
?
-
?
-
?
-
?
-
50% To Do, 0% In Progress, 50% Done
-
-
OSP QoS Support
Egress QoS capability involves traffic classification based on DSCP and five tuples and traffic shaping or enforcement of the policy to honor CIR (Committed Information Rate) and PIR (Peak Information Rate) together with Peak Burst Size. The enforcement point of the Egress QoS is typically at the point of contention or congestion so that high-priority traffic gets preferential treatment and the low-priority traffic is dropped where the aggregate traffic exceeds the egress interface capability. The CIR value of the Egress QoS policy provides guaranteed bandwidth for the specified traffic class where as PIR provides the maximum allowed traffic rate beyond the CIR for the given traffic class.
Use Case
Telco Service Provider wants to configure the Egress QoS policy to guarantee a minimum bandwidth for a given traffic class. Any traffic rate beyond the CIR and below the PIR should get preferential treatment using established traffic shaping mechanisms. Users should be able to apply QoS policy at each of the individual contention/congestion points in the host including virtual and physical interfaces. Additionally, an E2E QoS paradigm should be enabled at the host level for the given traffic class. Multiple traffic classes must be supported along with traffic classification and traffic shaping capability.
| Requirement | Details | MVP | Priority | EPIC |
|---|---|---|---|---|
| Traffic Classification based on DSCP and five tuples for OVS and OVS-DPDK | No | 3 | ||
| Egress QoS policy enforcement for OVS | Yes | 2 | ||
| Egress QoS policy enforcement for OVS-DPDK | Yes | 2 | ||
| Egress QoS policy enforcement at OVN | Yes | 2 | ||
| DSCP remarking for the specific traffic class | No | 3 | ||
| Tripple O / Director / Next Gen support for Day 1 operation | Yes | 2 | ||
| Egress QoS policy enforcement at NIC | Yes | 1 | OSPRH-2661 | |
| DSCP remarking at NIC | No | 2 | ||
| Traffic Classification based on five tuples at NIC | No | 3 | ||
| HQoS support - Virtual interface and Physical interface level | In order to support E2E QoS capability, user must be able to specify HQOS policy parameters for virtual and physical interfaces in the data path at a host level. This could include level 1 policy at OVS or OVS-DPDK and level 2 policy at PF of the NIC | No | 3 | |
| Neutron support for E2E Egress QoS | Support for neutron to configure Egress at E2E level that includes QoS at backend level, QoS at NIC level and QoS for instance placement | Yes | 2 |
QoS Concept and Configuration for Network Devices
