Reviewed: https://review.openstack.org/396651 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=38c1812015b6977f8212723d082222cefb0926e6 Submitter: Jenkins Branch: master
commit 38c1812015b6977f8212723d082222cefb0926e6 Author: Miguel Angel Ajo <[email protected]> Date: Thu Nov 17 09:17:29 2016 -0500 Transition qos notification driver into qos driver This will deprecate the notification_driver config setting, and no config setting will be needed. Also it lays down the foundation for a more decoupled interaction with mechanism drivers. Closes-Bug: #1657379 Related-Bug: #1627749 DocImpact Change-Id: I2f166a43f0b980ad22617f8a3f7b4cc7f4786c48 ** 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/1657379 Title: Refactor the QoS "notification_drivers" into QoS drivers Status in neutron: Fix Released Bug description: Beyond doing a decoupling refactor from the mechanism drivers and the core plugin this change will removes the need to define a notification_driver in the [qos] section of the neutron config file, being those drivers automatically exposed by the loaded mechanism drivers or the loaded core plugin. This is also a preliminary step to make https://bugs.launchpad.net/neutron/+bug/1586056 ( Improved validation mechanism for QoS rules with port types) possible. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1657379/+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
