yahoo-eng-team team mailing list archive

Thread
Date

[Bug 2012613] [NEW] [OVN] Define the OVS port in the LSP to allow OVN to set the QoS rules

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Rodolfo Alonso <2012613@xxxxxxxxxxxxxxxxxx>
Date: Thu, 23 Mar 2023 10:07:38 -0000
Reply-to: Bug 2012613 <2012613@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

Based on this OVN thread: "[RFC ovn 0/3] rework OVN QoS implementation"
(https://mail.openvswitch.org/pipermail/ovs-dev/2023-March/402940.html)

(description from the mail chain):
In the current codebase it is not possible to specify two different QoS rules for two different localnet ports, even if they are running on two different datapaths. Both ports will be configured with the latest QoS rule in the hashmap since it is not possible to link the QoS rule to the
corresponding OVS port. Fix the issue introducing "qos_ovs_port" parameter in the logical swith port option column. The CMS is responsible to configure it with the OVS port used for this QoS rule.

In this case, the CMS is Neutron. Neutron needs to set the
"LSP.options.qos_ovs_port" value for each port, in order to allow ovn-
controller to set the TC settings.

** Affects: neutron
Importance: Undecided
Status: New

--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2012613

Title:
[OVN] Define the OVS port in the LSP to allow OVN to set the QoS rules

Status in neutron:
New

Bug description:
Based on this OVN thread: "[RFC ovn 0/3] rework OVN QoS
implementation" (https://mail.openvswitch.org/pipermail/ovs-
dev/2023-March/402940.html)

In this case, the CMS is Neutron. Neutron needs to set the
"LSP.options.qos_ovs_port" value for each port, in order to allow ovn-
controller to set the TC settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2012613/+subscriptions