Simplify default service selection
Bug #1102503 reported by
Salvatore Orlando
on 2013-01-21
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | neutron |
Medium
|
Unassigned | ||
Bug Description
The current servie type management logic requires to specify a 'default service type' in quantum configuration file.
during the review process for the service type blueprint, it was pointed out that perhaps 'default providers' for each class of service could replace this concept.
This proposal actually simplifies the logic of the service type manager, which should be amended to this aim.
As this implies changes in quantum.conf, it is advisable to fix before grizzly release.
| Changed in quantum: | |
| status: | Confirmed → In Progress |
Salvatore Orlando (salvatore-orlando)
on 2013-01-21
| Changed in quantum: | |
| milestone: | none → grizzly-3 |
Mark McClain (markmcclain)
on 2013-01-30
| tags: | added: api |
Salvatore Orlando (salvatore-orlando)
on 2013-02-19
| Changed in quantum: | |
| milestone: | grizzly-3 → grizzly-rc1 |
Salvatore Orlando (salvatore-orlando)
on 2013-02-27
| Changed in quantum: | |
| milestone: | grizzly-rc1 → havana-1 |
Temporarily untargeting pending refactoring of service type API.
| Changed in quantum: | |
| milestone: | havana-1 → none |
Thsi bug does not make sense anymore after service type refactoring
| Changed in neutron: | |
| assignee: | Salvatore Orlando (salvatore-orlando) → nobody |
| status: | In Progress → Won't Fix |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/