Comment 11 for bug 1639186

I just did a quick review of this issue and how trunk ports and QOS work in OVN. OVN implements both trunk ports and QOS in a different way and does not suffer from this issue.

QOS is implemented as queues on egress interfaces and we have flows that set the proper queue id based on the source of the packet.

It should work if you try qos with devstack and networking-ovn if anyone wants to poke around at how it works. http://docs.openstack.org/developer/networking-ovn/testing.html