openstack/nova
Code Issues Proposed changes
476f15d610
nova/tools/conf
History
Mark McLoughlin ce27bca549 Try out a new nova.conf.sample format 
The current format strikes me as fairly bizarre:

  - Having the help message after the option it's documenting seems
    backwards to me. Compare to the glance or swift samples.

  - Printing the type as e.g. "(StrOpt)" isn't very user friendly

  - We're creating a global pound symbol shortage

Switch to a new format that looks much more like a normal config file.

Change-Id: Ifba0a181667f3b81cad400f1cdd3812e388a9d64
2013-01-10 11:53:52 +00:00
..
analyze_opts.py Added script to find unused config options. 2012-09-18 13:36:03 -07:00
extract_opts.py Try out a new nova.conf.sample format 2013-01-10 11:53:52 +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