Open Stack

> On 1/12/2016 3:29 AM, gilles.mocellin at nuagelibre.org wrote:
> > Hello,
> > 
> > [...]
> > 
> > What I would like is to have the minimum configuration files for each
> > component, on each server.
> > I know it would not hurt to have more configuration than used, but it
> > would help to really understand what is done by each component.
> > 
> > At the moment, I can't find where I have to put quota configuration
> > (until_refresh and max_age).
> > Is it used by nova-api, nova-scheduler... cinder-api ?
> > Or is it used by nova-compute, cinder-volume ?
> > 
> > I would find very clear if each component had it own config file.
> > It would also avoid to put some passwords (database acces, 
keystone...)
> > on nodes where it's not used.
> > 
> > [...]
> >
> > So, is there a documentation where I could see :
> > - nova-api, reads theses configuration options
> > - nova-compute...

> Markus Zoeller is working on cleaning this up in Nova in Mitaka, see the 

> spec here:
> 
> 
http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/centralize-
> config-options.html
> 
> -- 
> 
> Thanks,
> 
> Matt Riedemann


Yepp, we're working on it in Nova. The current version can be found at 
[1].
The options [DEFAULT].vcpu_pin_set and [serial_console].serialproxy_port
are examples how the help will look like. Let me know if you find this 
useful or if you miss something there.
It will still be one file "nova.conf" but our effort is a prerequisite
to the separated "nova-compute.conf", "nova-scheduler.conf" and so on.
The ongoing effort can be found at [2].

References:
[1] http://docs.openstack.org/developer/nova/sample_config.html
[2] https://review.openstack.org/#/q/topic:bp/centralize-config-options

Regards, Markus Zoeller (markus_z)