[OVN] QoS doesn't work with DVR, vlan tenant networks or provider networks.

[Yury Zaitsev]

I created two instances on different compute nodes and attached them to provider network. When I try to apply policy to the port via Neutron it has no effect.

[Russell Bryant (russellb)]

I was able to verify this bug by reviewing the code. The problem is in OVN itself.

QoS will work when the packets leave the host on a tunnel, but not if it goes straight to a provider network. This needs to be fixed in OVN.

Thanks for the report!

[Yury Zaitsev (zaja1kun)]

I checked some other scenarios like 2 VM's connected via private net on the same node and on different nodes, with and without floating ip's. And none of them seems to work.
I can see my policy in ovn-sb's Port_Binding table, but OVS Queue and QoS tables are empty, logical port QoS field is empty and there are no actions like set_queue in br-int openflow dump.
Seems that ovn-controller ignores qos options in ovn-sb.

[Miguel Angel Ajo (mangelajo)]

This also happen if you are using "DVR", the packets will not go through tunnelling, hence not hitting the queue core ovn configures on the tunnel interfaces.

I opened this bug:

https://github.com/openvswitch/ovs-issues/issues/150

Yeah, you won't see Queue entries in ovs, they are created directly on the kernel. But they work when it's compute to compute through tunnelling (we have tests running that and they pass, although, as soon as you try to run those tests with DVR, or by using vlan tenant networks, it stops working.

[Lucas Alvares Gomes (lucasagomes)]

The OVN driver now lives in the neutron repository. Moving this bug to their tracker.