Reviewed: https://review.openstack.org/442375 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a7e6d3b175b740b8286d2030fccba538e875e6df Submitter: Jenkins Branch: master
commit a7e6d3b175b740b8286d2030fccba538e875e6df Author: Reedip <reedi...@gmail.com> Date: Tue Mar 7 05:36:02 2017 -0500 Add check for Bandwidth Limit Rules Currently it is possible to create 2 rules in the same policy where the Max Bandwidth ( from the Bandwidth Limit Rule ) can be less than Minimum Bandwidth defined in ( Minimum Bandwidth Rule) , which can be pretty confusing. This patch raises an exception if such an issue occurs. Change-Id: Ib748947bcd85253aa22e370a56870afbfbafa19b Closes-Bug: #1667138 ** 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/1667138 Title: Minumum bandwidth can be higher than maximum bandwidth limit in same QoS policy Status in neutron: Fix Released Bug description: Currently at least SR-IOV driver supports both QoS rules: bandwidth limit and minimum bandwidth. User can set in one policy both of such rules and set higher minimum bandwidth (best effor) then maximum available bandwidth for port. IMO such behaviour will be undefined on backend and should be forbidden somehow on API level. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1667138/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp