ea7018fe5f
This syncs Keystone with oslo-incubator commit hash 2fd457bf2ccbeb2b84ffb204778b6417cd5405ba . In keystone: $ rm -r keystone/openstack/common In oslo-incubator: $ python update.py ../keystone The newer lockutils requires posix_ipc. It's already in global-requirements. Keystone uses gettextutils and versionutils from oslo-incubator so those should be in openstack-common.conf. They were pulled in as dependencies of other oslo-incubator modules but Keystone shouldn't rely on that. Keystone doesn't use log_handler directly so that module was removed from openstack-common.conf. log_handler is available in the oslo.messaging library. Change-Id: I6082f4e0995ca35372f9b061d8f76890aa93250c |
||
---|---|---|
.. | ||
check_uptodate.sh | ||
generate_sample.sh | ||
oslo.config.generator.rc | ||
README |
This generate_sample.sh tool is used to generate sample config files from OpenStack project source trees. Run it by passing the base directory and package name i.e. $> generate_sample.sh --base-dir /opt/stack/nova --package-name nova \ --output-dir /opt/stack/nova/etc $> generate_sample.sh -b /opt/stack/neutron -p nova -o /opt/stack/neutron/etc Optionally, include libraries that register entry points for option discovery, such as oslo.messaging: $> generate_sample.sh -b /opt/stack/ceilometer -p ceilometer \ -o /opt/stack/ceilometer/etc -l oslo.messaging 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. This check_uptodate.sh tool is used to ensure that the generated sample config file in the OpenStack project source tree is continually kept up to date with the code itself. This can be done by adding a hook to tox.ini. For example, if a project already had flake8 enabled in a section like this: [testenv.pep8] commands = flake8 {posargs} This section would be changed to: [testenv.pep8] commands = flake8 {posargs} {toxinidir}/tools/config/check_uptodate.sh