Reviewed: https://review.openstack.org/519573 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c43317e380d90a9b1eab4f3c5058b770b43dcf96 Submitter: Zuul Branch: master
commit c43317e380d90a9b1eab4f3c5058b770b43dcf96 Author: Zachary <[email protected]> Date: Tue Nov 14 15:48:54 2017 +0800 [Qos] ingress bandwidth limit by ovs is not accurate According to Open vSwitch FAQ [1], max-rate value which is set for all queues in qos is set as link speed in case when it is not specified. This can lead to inaccurate ingress bandwidth limits in case when QoS is applied e.g. directly on tapXXX port (which is "tun" interface type) and configured bandwidth limit is higher than interface's link_speed. This patch set max-rate parameter in qos's other_config table to not use default value determined by Open vSwitch and to make rate limits more accurate. The modification is covered by functional tests in https://github.com/openstack/neutron/blob/master/neutron/tests/ functional/agent/test_ovs_lib.py. [1] http://docs.openvswitch.org/en/latest/faq/qos/ Change-Id: Id937216a724fbf776298efd11f74ac71056cfe06 Closes-Bug: #1730605 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1730605 Title: neutron qos bindlimit by ovs is not accurate Status in neutron: Fix Released Bug description: 1. openstack version: pike 2. neutron --version 6.5.0 3. ovs-vsctl (Open vSwitch) 2.7.2 4. iperf3-3.1.3-1.fc24.x86_64.rpm egress bw-limiter is never accurate ingress bw-limiter is also not accurte, but using ovs 2.5, ingress is accurate ! To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1730605/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
