Description of problem:
For OVS-DPDK the ingress rate-limiting or egress policer do not provide any queuing or traffic shaping, so there is no way to do minimum bandwidth guarantee per VM? User can only do Max TX bandwidth per VM with Ingress Rate limiting. Egress policer uses token-bucket mechanism with no support for hierarchical queues based on TX port
OVS QoS supports linux queuing mechanisms linux-htb, linux-hfsc that allows user to create output queues based on TX port and set the min and max bandwidth.
DPDK supports Hierarchical Schduler using Token Bucket metering
RTE Traffic Metering
Traffic metering algorithms:
1. Single Rate Three Color Marker (srTCM): defined by IETF RFC 2697
2. Two Rate Three Color Marker (trTCM): defined by IETF RFC 2698
We need to bring these into OVS-DPDK for traffic shaping usecases, if we want to support minimum bandwidth
RHOSP 14 needs maximum bandwidth and RHOSP15 needs min bandwidth
The usecase is every server has a single 25Gb NIC for all traffic - datapath, storage, control-plane, Management/API
Datapath traffic rate should not be affected if there is a huge burst of traffic for storage or control plane. A minimum bandwidth should be guaranteed for datapath.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:2944