nova/tools/config
Davanum Srinivas af2d6c9576 Switch to using oslo_* instead of oslo.*
The oslo team is recommending everyone to switch to the
non-namespaced versions of libraries. Updating the hacking
rule to include a check to prevent oslo.* import from
creeping back in.

This commit includes:
- using oslo_utils instead of oslo.utils
- using oslo_serialization instead of oslo.serialization
- using oslo_db instead of oslo.db
- using oslo_i18n instead of oslo.i18n
- using oslo_middleware instead of oslo.middleware
- using oslo_config instead of oslo.config
- using oslo_messaging instead of "from oslo import messaging"
- using oslo_vmware instead of oslo.vmware

Change-Id: I3e2eb147b321ce3e928817b62abcb7d023c5f13f
2015-02-06 06:03:10 -05:00
..
README Updates tools/config/README 2013-08-22 10:15:14 +08:00
analyze_opts.py Switch to using oslo_* instead of oslo.* 2015-02-06 06:03:10 -05:00
check_uptodate.sh Sync latest config file generator from oslo-incubator 2014-01-31 22:03:01 +00:00
generate_sample.sh Sync latest config file generator from oslo-incubator 2014-01-31 22:03:01 +00:00
oslo.config.generator.rc Switch to using oslo_* instead of oslo.* 2015-02-06 06:03:10 -05: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/config/generate_sample.sh -b ./ -p nova -o etc/nova

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/config/analyze_opts.py