052f9ded88
Per the original Nova code, these checks need to be able to run on n-1 database data, so they can't rely on the service's object model for database access. Add details about that to the docstring for UpgradeCommands. Also removes a nova-ism from the check docstring. Change-Id: I4fe84988397ae9bd2305811f10fa3d1449c4ac9f |
||
---|---|---|
doc/source | ||
oslo_upgradecheck | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
oslo.upgradecheck
Common code for writing OpenStack upgrade checks
This project contains the common code necessary for writing upgrade checks in OpenStack projects. It includes a module (oslo_upgradecheck.upgradecheck) for the common code as well as an example (oslo_upgradecheck.__main__) of integrating that code into a project.
- Free software: Apache license
- Documentation: https://docs.openstack.org/oslo.upgradecheck/latest/
- Source: https://git.openstack.org/cgit/openstack/oslo.upgradecheck
- Bugs: https://bugs.launchpad.net/oslo.upgradecheck