d137cbceb5
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>
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:
- Quiesce(pre-configure.d),
- Configure(configure.d),
- Migrate(migration.d),
- 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.