Rework OVN QoS implementation in order to configure it through OVS QoS
table instead of running tc command directly bypassing OVS.
This series allows to apply QoS rules on the localnet port related to
logical switch ports running on the same datapath. Considering the
following netowrk configuration:
LSP{0,1} -- LogicalSwitch -- Localnet0
It is possible to apply the following QoS rules on Localnet0 on egress traffic
entering the cluster from LSP{0,1}:
- LSP0: min-rate r0, max_rate R0
- LSP1: min-rate r1, max_rate R1
https://bugzilla.redhat.com/show_bug.cgi?id=2129742
Changes since v4:
- do not remove ovn-egress-iface parameter
- rebase on top of ovn main branch
Lorenzo Bianconi (7):
controller: remove tunnel interfaces from egress_ifaces sset
controller: convert egress_ifaces to smap
controller: configure qos through ovs qos table and do not run tc
directly
controller: improve ovs port lookup by name and qos
controller: use unsigned long long int for
qos_max_rate/qos_min_rate/qos_burst
northd: introduce qos_physical_network in port_binding other_config
column
update NEWS with new QoS info
NEWS | 6 +
controller/binding.c | 478 +++++++++++++++++++-----------------
controller/binding.h | 4 +-
controller/ovn-controller.c | 29 ++-
controller/ovsport.c | 32 +++
controller/ovsport.h | 5 +
northd/northd.c | 34 ++-
northd/ovn-northd.8.xml | 12 +
ovn-sb.xml | 5 +
tests/ovn-northd.at | 2 +
tests/ovn-performance.at | 5 -
tests/system-ovn.at | 151 +++++++++++-
12 files changed, 505 insertions(+), 258 deletions(-)
--
2.40.0
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
