OpenStack Release Bot
This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for victoria. See also the PTI in governance . : https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: I8127e92439d2393ec7a4797a5ee7776ecc29c2d1
|2 months ago|
|os_refresh_config||3 months ago|
|releasenotes/notes||1 year ago|
|tests||8 years ago|
|zuul.d||2 months ago|
|.coveragerc||6 years ago|
|.gitignore||3 years ago|
|.gitreview||2 years ago|
|.stestr.conf||3 years ago|
|LICENSE||8 years ago|
|README.rst||3 years ago|
|requirements.txt||4 years ago|
|setup.cfg||1 year ago|
|setup.py||1 year ago|
|test-requirements.txt||3 months ago|
|tox.ini||6 months ago|
os-refresh-config uses dib-run-parts to run scripts in a pre-defined set of directories:
/opt/stack/os-config-refresh/pre-configure.d /opt/stack/os-config-refresh/configure.d /opt/stack/os-config-refresh/post-configure.d /opt/stack/os-config-refresh/migration.d /opt/stack/os-config-refresh/error.d
/opt/stack/os-config-refresh is the default base directory. You can set OS_REFRESH_CONFIG_BASE_DIR environment variable to override the default one.
Its intended purpose is to separate scripts execution into 4 phases:
It runs through all the phases above to ensure configuration is applied and enabled on a machine. It will run the scripts in error.d and then exit with a non-zero exit status if any phase has a problem. The scripts in each phase should not depend on each other having worked properly.
Note: Earlier versions of os-refresh-config ran migration before post-configure. This was an oversight in the initial design, as migrations are intended to be online migrations after the host is fully configured.
For things which must happen while the service is quiesced, that should be done in the post-configure scripts which control the service state.