Simplify default service selection

Bug #1102503 reported by Salvatore Orlando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
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.

Tags: api
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to quantum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/20157

Changed in quantum:
status: Confirmed → In Progress
Changed in quantum:
milestone: none → grizzly-3
tags: added: api
Changed in quantum:
milestone: grizzly-3 → grizzly-rc1
Changed in quantum:
milestone: grizzly-rc1 → havana-1
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

Temporarily untargeting pending refactoring of service type API.

Changed in quantum:
milestone: havana-1 → none
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.