-
Notifications
You must be signed in to change notification settings - Fork 257
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
Does OVN (with Yoga release) use OVS or Linux TC for QoS implementation? #256
Comments
@LorenzoBianconi Do you have any comments for this issue ? |
@nhtung96 I guess ovn/ovs for incoming traffic rate limiting is using ovs-meters instead of tc (tc qdisc are used for egress traffic shaping if ovs-kdp is used). Can you please try dumping ovs meters? |
@LorenzoBianconi Thank you for your reply. I did try dumping ovs meters at compute node but didnt see the meter with the rate I configured. (actually I don't how meter id link to ovn nb/sb db qos rule, just grep the rate). ======OVS check==== |
Hi team, I got a problem that my VM port does not have traffic rate limit, although it has been applied QoS policy (100Mbps) . I checked the northbound ovn-nbctl qos-list and found qos rule associated to VM port. It is OK. However, I looked at ovs-vsctl list interface <vm_tap_port> and I saw ingress_policing_rate=0 (burst=0 also), it means OVS didn't play a role in QoS rate limit, didnt it? I also tried to set ingress_policing_rate=100000 but it did not have improvement for actual rate limit.
The text was updated successfully, but these errors were encountered: