Open Stack

There is currently a cross project specification under review that changes how and where the config files are written for an OpenStack installation.  If config options and how they are presented to you are important to you, I strongly suggest you go out , read the spec/review and comment on both the aspects that work for you and the aspects that don't work for you.  Be clear on explaining why something doesn't work, as the developers believe what they are proposing is what you would want.  You also might want to read the comments on version 6 of this review.

--Rocky

The review is here:
https://review.openstack.org/#/c/295543/

The commit message is:
This spec looks at how to get a better configuration option experience
for operators and (to a lesser extent) developers.
The summary is:
Operators currently have to grapple with hundreds of configuration options
across tens of OpenStack services across multiple projects. In many cases
they also need to be aware of the relationships between the options.
In particular, this makes the initial deployment a very daunting task.

This spec proposes a way projects can use oslo.config in a way that leads
to better experience for operators trying to understand all the configuration
options, and helps developers better express the intent of each configuration
option.

This spec re-uses and builds on the ideas in this recent Nova specification:
http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/centralize-config-options.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160408/fdd6d87d/attachment.html>