openstack/deb-python-os-refresh-config
Code Issues Proposed changes
RETIRED, further work has moved to Debian project infrastructure
73 Commits 3 Branches 36 Tags 186 KiB
519606f749
Go to file
Ben Nemec 519606f749 Fix coverage job 
The setup.py testr command no longer supports running coverage.  It
moved to setup.py test.

Change-Id: If5e60809fe11513d85cf8d67a39132557c64171e
2017-03-31 17:58:39 +00:00
os_refresh_config Adjust test suite for new psutil versions 2017-01-18 20:19:36 +01:00
tests Initial commit 2013-02-06 16:59:40 -08:00
tools Add Constraints support 2016-12-20 14:38:41 +11:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:41:56 +00:00
.gitignore Coverage report was't created 2014-09-26 16:09:51 +09:00
.gitreview Update stackforge references to openstack 2013-08-17 23:00:11 -04:00
.testr.conf Coverage report was't created 2014-09-26 16:09:51 +09:00
LICENSE Adding setup.py to make for an easier installation 2013-02-12 07:04:28 -08:00
README.rst Show team and repo badges on README 2016-11-25 14:21:32 +01:00
requirements.txt Updated from global requirements 2017-03-06 01:16:55 +00:00
setup.cfg Support building wheels (PEP-427) 2013-11-19 10:33:09 +01:00
setup.py Updated from global requirements 2017-03-06 01:16:55 +00:00
test-requirements.txt Updated from global requirements 2017-03-06 01:16:55 +00:00
tox.ini Fix coverage job 2017-03-31 17:58:39 +00:00

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.