Make use of oslo.config's new config generator

Registered by John Garbutt on 2015-06-16

Oslo.config have now removed the old way we used to deal with olso.config sample generation, because it has proved very hard to maintain.

You can get more details here:
http://specs.openstack.org/openstack/oslo-specs/specs/juno/oslo-config-generator.html#developer-impact

The problem with maintaining a list of options in Nova, is that because is spread throughout the whole code base, its really easy to forget to add something in the config generator when adding config options.

To make that easier to maintain, we also really need to look at moving all our config options into a single set of config modules. It could look something like this:
https://github.com/openstack/keystone/blob/master/keystone/common/config.py
For Nova, we probably want a few modules in a central location, rather than a single one, but thats the basic idea.

Blueprint information

Status:
Complete
Approver:
Michael Still
Priority:
Medium
Drafter:
John Garbutt
Direction:
Approved
Assignee:
Davanum Srinivas (DIMS)
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 12.0.0
Started by
John Garbutt on 2015-06-22
Completed by
John Garbutt on 2015-07-27

Related branches

Sprints

Whiteboard

Addressed by: https://review.openstack.org/180013
    Use oslo-config-generator instead of generate_sample.sh

Addressed by: https://review.openstack.org/212783
    Use oslo-config-generator instead of generate_sample.sh

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.