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

[Rodolfo Alonso]

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.

[Akihiro Motoki (amotoki)]

I marked this as Wishlist as it looks like half bug and half feature.

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Sorry Akihiro, this is not a feature bug a bug in core OVN that needs to be addressed in Neutron. I'm increasing the importance.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron/+/879496

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Rodolfo Alonso <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/neutron/+/879496