Reviewed: https://review.openstack.org/300210 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6dcdb15dce4952cdf3782d57431d0c5f7ba6e53b Submitter: Jenkins Branch: master
commit 6dcdb15dce4952cdf3782d57431d0c5f7ba6e53b Author: Sławek Kapłoński <[email protected]> Date: Wed Mar 30 21:21:43 2016 +0000 LinuxBridge agent's QoS driver bw limit for egress traffic QoS service plugin provides for now bandwidth limit rules for egress traffic only (from VM point of view). QoS extension driver for Linuxbridge agent now configures limits in proper way on tap interface so limited is traffic which is outgoing from VM. Linuxbridge agent's QoS extension configures egress bandwidth limit and burst value in exactly same way how openvswitch is doing it with tc. Old methods in TcCommand class will stay untouched because they can be used later to implement also ingress bandwidth limits in QoS. Change-Id: Id2b0463f49df52744e5bc3979a4cfd0ff06f9248 Closes-bug: #1563720 ** 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/1563720 Title: Bandwidth limiting for linuxbridge agent works for ingress traffic instead of egress Status in neutron: Fix Released Bug description: QoS traffic bandwidth limitation is applied for ingress instead of egress traffic by Linuxbridge L2 agent. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1563720/+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
