Switch to single glance.conf.sample generated by oslo config generator

Registered by Dirk Mueller on 2014-02-15

Currently glance is using manually maintained separate sample config files in etc/. Most other projects have switched over to a single project wide config that is geing auto-generated during commits with all options, descriptions and defaults properly added to one sample file, retrieved from the actual code.

Goal of this blue print is to unify the multiple glance configs into one config that is being used by all glance services. Ultimatively this sample configuration can then be automatically generated to avoid that smaple config and code deviate.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
Dirk Mueller
Direction:
Approved
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

I'm not sure it will work best for all glance services to use a single config. How will deployers know that they do not need certain configuration settings in certain services?
markwash more-info 2014-02-15

Needs a bit more information, but it seems maybe this dropped off the radar? Please reassign yourself if you want to bring it back up.
markwash abandoned 2014-03-07

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.