Refactor the QoS "notification_drivers" into QoS drivers
Bug #1657379 reported by
Miguel Angel Ajo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Miguel Angel Ajo |
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:/
Changed in neutron: | |
importance: | Undecided → High |
assignee: | nobody → Miguel Angel Ajo (mangelajo) |
importance: | High → Medium |
milestone: | none → ocata-3 |
tags: | added: qos |
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
milestone: | ocata-3 → ocata-rc1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/396651 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=38c1812015b 6977f8212723d08 2222cefb0926e6
Committed: https:/
Submitter: Jenkins
Branch: master
commit 38c1812015b6977 f8212723d082222 cefb0926e6
Author: Miguel Angel Ajo <email address hidden>
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: I2f166a43f0b980 ad22617f8a3f7b4 cc7f4786c48