neutron/neutron/agent/common
Zachary c43317e380 [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
2017-12-13 09:33:34 +08:00
..
__init__.py Empty files should not contain copyright or license 2014-10-20 00:50:32 +00:00
base_polling.py OVS agent support on Hyper-V 2015-03-25 13:48:33 -07:00
ip_lib.py Refactoring agent linux&ovsdb config 2017-08-25 10:41:39 -04:00
ovs_lib.py [Qos] ingress bandwidth limit by ovs is not accurate 2017-12-13 09:33:34 +08:00
polling.py Fixes "OVS Agent doesn't start on Windows" 2016-03-15 03:14:05 +00:00
utils.py Merge "Refactoring db config options" 2017-11-01 23:58:06 +00:00