Restart services and coordinate data migration on Heat config changes.
No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.
pengyuesheng 84d84645d1 Switch to Ussuri jobs hace 4 meses
os_refresh_config Adjust test suite for new psutil versions hace 3 años
tests Initial commit hace 7 años
zuul.d Switch to Ussuri jobs hace 4 meses
.coveragerc Change ignore-errors to ignore_errors hace 4 años
.gitignore Switch to stestr hace 1 año
.gitreview OpenDev Migration Patch hace 10 meses
.stestr.conf Switch to stestr hace 1 año
LICENSE Adding setup.py to make for an easier installation hace 7 años
README.rst Update links in README hace 2 años
requirements.txt Updated from global requirements hace 2 años
setup.cfg Add Python 3 Train unit tests hace 7 meses
setup.py Updated from global requirements hace 3 años
test-requirements.txt Sync Sphinx requirement hace 4 meses
tox.ini Update the constraints url hace 5 meses

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.