-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OVN: QoS max bandwidth / burst only works if your packet will travel via tunnel #150
Comments
Hi @mangelajo When I'm using OVN with docker in “overlay” mode, the docker network(with global visibility) is used to connect containers in local OVS that are controlled by local ovn-controller and docker is responsible to provide floating ip. I'm thinking the packets are not traveling through tunnel port and can't limit max bandwidth / burst. Steps to apply qos: Step 2 Step 3 Step 4
Do you have any idea how to solve this problem? I'm following this tutorial. |
This needs to be fixed in ovn-controller, it has to create a queue on the network interface associated to the provider network bridge. I'm unsure by your description of your exact topology. Can you do: $ ovs-vsctl list Open . And show me what you have ? and a $ ovs-vsctl show |
In DC1(hostname) with IP 10.7.229.135:
In DC2(hostname) with IP 10.7.229.141:
Each VM has one container attached in local OVS and they can communicate each other via geneve tunnel. The local OVS has two ports, one to remote IP and another to container |
Logical topology(OVN-Northbound):
Physical topology(OVN-Southbound):
|
When I execute ping from container(192.168.200.2) in DC1(10.7.229.135) to container(192.168.200.3) in DC2(10.7.229.141), tcpdump in DC1 show:
|
I encounter the same problem, how can I fix it? [root@worker1 ~]# ovs-vsctl --version |
This patch (2 years ago) introduces a regression in combination with distributed floating ip, or direct port attachment to provider network.
openvswitch/ovs@a6095f8
If you have a port which is directly attached to a provider network, or that is configured with a distributed floating ip, the packets will never travel through the tunnel port, and the traffic won't be limited.
The text was updated successfully, but these errors were encountered: