openstack
/
os-refresh-config
Code Issues Proposed changes
Restart services and coordinate data migration on Heat config changes.
27 Commits 1 Branch 77 Tags 1.3 MiB
Python 68.6%
Shell 31.4%
Go to file
James Slagle 9963e411cc Add argparse to requirements.txt 
argparse is a requirement of os-refresh-config, so it should be listed here.
Likely this error is never encountered b/c argparse is part of python 2.7. But,
for older distros like RHEL that are still on python 2.6, it needs to know to
install it explicitly.

Change-Id: I63bd54bf42d99d2ef7f6534848afc396471cd802
 		2014-02-27 07:19:01 -05:00
os_refresh_config Move migration to run after post-configure 2014-02-07 12:15:49 -08:00
tests Initial commit 2013-02-06 16:59:40 -08:00
.gitignore Conform .gitignore with other OpenStack projects. 2013-08-16 08:25:33 -07:00
.gitreview Update stackforge references to openstack 2013-08-17 23:00:11 -04:00
.testr.conf Add tox.ini and fix pep8 problems 2013-06-13 09:50:52 +01:00
LICENSE Adding setup.py to make for an easier installation 2013-02-12 07:04:28 -08:00
README.rst Move migration to run after post-configure 2014-02-07 12:15:49 -08:00
requirements.txt Add argparse to requirements.txt 2014-02-27 07:19:01 -05:00
setup.cfg Support building wheels (PEP-427) 2013-11-19 10:33:09 +01:00
setup.py Updated from global requirements 2013-10-10 20:26:21 +00:00
test-requirements.txt Updated from global requirements 2013-12-10 23:44:45 +00:00
tox.ini Remove tox locale overrides 2014-02-10 03:09:03 +00:00

README.rst

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 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 exit with an error 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.