[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.
Reviewed: https:/ /review. openstack. org/519573 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=c43317e380d 90a9b1eab4f3c50 58b770b43dcf96
Committed: https:/
Submitter: Zuul
Branch: master
commit c43317e380d90a9 b1eab4f3c5058b7 70b43dcf96
Author: Zachary <mazengxie@126.com>
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 /github. com/openstack/ neutron/ blob/master/ neutron/ tests/ agent/test_ ovs_lib. py.
https:/
functional/
[1] http:// docs.openvswitc h.org/en/ latest/ faq/qos/
Change-Id: Id937216a724fbf 776298efd11f74a c71056cfe06
Closes-Bug: #1730605