[openstack-dev] [docs] Can we get the "configuration reference" of master more often?

Ronald Bradford me at ronaldbradford.com
Thu Mar 3 15:13:10 UTC 2016

On Thu, Mar 3, 2016 at 9:51 AM, Andreas Jaeger <aj at suse.com> wrote:

> On 2016-03-03 15:37, Markus Zoeller wrote:
> > The "configuration reference" manual at [1] is really helpful to get
> > an overview of the options and we (Nova folks) were wondering if we
> > could have that updated more often [2].
> >
> > Right now it is from November 2015 [3] and we (Nova folks) put a lot of
> > effort this cycle in improving the help of our config options but they
> > aren't yet (fully) reflected in that guide.
> >

>From what little I have read, this Nova work is around consolidation and
grouping of existing options, and not the addition of new options?
The nova.flagmappings files [5] defines a relationship of the displayed
table of options (the heading in the nova.headers file) and the options.
The group information can be specified as a prefix to the option,
e.g. database/backend database.

the "Description of conductor configuration options" table for example in
[1] (sorry no direct linking possible, feature perhaps?) , where a table
may contain options from multiple groups or namespaces.

> > Different options would be:
> >     A: per milestone
> >     B: per merge of a commit which contains "DocImpact" in its message
> >     C: daily/nightly
> >
> > Personally I think daily/nightly would be sufficient.
> >
> > AFAIK the generation of that guide is done with [4] and IIUC there is
> > no necessity of human intervention in that process, or did I miss
> > something?

I have been looking into this process at present in free time to understand
and see how docs are generated. From my discussion with Gauvain it is both
manual and time consuming.

> The flagmappings file is manually updated - if a new option shows up, we
> need to know to which table it should be added. Doug and Gauvain

table or tables.  There is a 1 to n mapping of option to table, expressed
as one line in the file. The nova file has no example, cinder is a place to
look at.

> discussed automating this in the future but this needs first some changes,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160303/e4fc4d7e/attachment.html>

More information about the OpenStack-dev mailing list