openstack
/
os-refresh-config
Code Issues Proposed changes
Restart services and coordinate data migration on Heat config changes.
23 Commits 1 Branch 76 Tags 1.3 MiB
Python 68.6%
Shell 31.4%
Go to file
James E. Blair d137cbceb5 Have tox install via setup.py develop 
tox 1.6 was released, which means that we can now take advantage of
the feature we added to it - which is using setup.py develop to
install the code into the virtualenv. The logic was taken from
run_tests.sh - so the performance issues around using tox vs. using
install_venv should now be gone.

Additionally, override the tox pip install command to avoid using the
"--pre" option which is the default in tox.  "--pre" means "Include
pre-release and development versions."  By default, pip will only
install stable versions of software, and that is the behavior we want.

Change-Id: Ida5e440d1bdb9f8e9031277ea53a02d2ef171438
Co-Authored-By: Monty Taylor <mordred@inaugust.com>
 		2013-12-11 09:00:34 -08:00
os_refresh_config Add a lockfile. 2013-07-17 09:00:18 -07: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 `os-refresh-config` README enhancement 2013-12-03 14:07:22 +08:00
requirements.txt Updated to OpenStack standards 2013-08-13 13:45:14 -03: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 Have tox install via setup.py develop 2013-12-11 09:00:34 -08: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/migration.d
/opt/stack/os-config-refresh/post-configure.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. Migrate(migration.d),
  4. Activate(post-configure.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.