https://github.com/openstack/os-refresh-config
Restart services and coordinate data migration on Heat config changes. Mirror of code maintained at opendev.org.
https://github.com/openstack/os-refresh-config
Last synced: 11 months ago
JSON representation
Restart services and coordinate data migration on Heat config changes. Mirror of code maintained at opendev.org.
- Host: GitHub
- URL: https://github.com/openstack/os-refresh-config
- Owner: openstack
- License: apache-2.0
- Created: 2013-08-18T02:03:45.000Z (almost 13 years ago)
- Default Branch: master
- Last Pushed: 2024-10-19T15:39:44.000Z (over 1 year ago)
- Last Synced: 2024-12-07T03:50:24.668Z (over 1 year ago)
- Language: Python
- Homepage: https://opendev.org/openstack/os-refresh-config
- Size: 161 KB
- Stars: 47
- Watchers: 8
- Forks: 14
- Open Issues: 0
-
Metadata Files:
- Readme: README.rst
- License: LICENSE
Awesome Lists containing this project
README
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/tc/badges/os-refresh-config.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
=================
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.