openstack/nova
Code Issues Proposed changes
559f03ebfa
nova/tools/conf
History
Mark McLoughlin 94d87bce21 Remove nova.config.CONF 
Modules import nova.config for two reasons right now - firstly, to
reference nova.config.CONF and, secondly, if they use one of the
options defined in nova.config.

Often modules import nova.openstack.common.cfg and nova.config
which is a bit pointless since they could just use cfg.CONF if
they just want to nova.config in order to reference CONF.

Let's just use cfg.CONF everywhere and we can explicitly state
where we actually require options defined in nova.config.

Change-Id: Ie4184a74e3e78c99658becb18dce1c2087e450bb
2012-11-20 00:00:21 +00:00
..
analyze_opts.py Added script to find unused config options. 2012-09-18 13:36:03 -07:00
extract_opts.py Remove nova.config.CONF 2012-11-20 00:00:21 +00:00
generate_sample.sh Allow generate_sample.sh to be run from toplevel dir 2012-08-23 10:37:38 +01:00
README Added script to find unused config options. 2012-09-18 13:36:03 -07:00

README 

This generate_sample.sh tool is used to generate etc/nova/nova.conf.sample

Run it from the top-level working directory i.e.

  $> ./tools/conf/generate_sample.sh

Watch out for warnings about modules like libvirt, qpid and zmq not
being found - these warnings are significant because they result
in options not appearing in the generated config file.


The analyze_opts.py tool is used to find options which appear in
/etc/nova/nova.conf but not in etc/nova/nova.conf.sample
This helps identify options in the nova.conf file which are not used by nova.
The tool also identifies any options which are set to the default value.

Run it from the top-level working directory i.e.

  $> ./tools/conf/analyze_opts.py