Restart services and coordinate data migration on Heat config changes.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
pengyuesheng 84d84645d1 Switch to Ussuri jobs 3 months ago
os_refresh_config Adjust test suite for new psutil versions 3 years ago
tests Initial commit 7 years ago
zuul.d Switch to Ussuri jobs 3 months ago
.coveragerc Change ignore-errors to ignore_errors 4 years ago
.gitignore Switch to stestr 1 year ago
.gitreview OpenDev Migration Patch 10 months ago
.stestr.conf Switch to stestr 1 year ago
LICENSE Adding setup.py to make for an easier installation 7 years ago
README.rst Update links in README 1 year ago
requirements.txt Updated from global requirements 2 years ago
setup.cfg Add Python 3 Train unit tests 7 months ago
setup.py Updated from global requirements 3 years ago
test-requirements.txt Sync Sphinx requirement 4 months ago
tox.ini Update the constraints url 4 months ago

README.rst

Team and repository tags

image

os-refresh-config

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:

  1. Quiesce(pre-configure.d),
  2. Configure(configure.d),
  3. Activate(post-configure.d).
  4. Migrate(migration.d),

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.