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 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron (master) | #1 |
| Changed in neutron: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/neutron 10.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 38c1812015b6977
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