tripleo-image-elements/elements/os-refresh-config
Gonéri Le Bouder 9481784a11 sort the element-deps to please dib-lint
Since I43fd90647acba400cea11c665fb587856514b0ee dib-lint
ensure the elment-deps file is properly sorted.

Change-Id: Ie0347951d99a227fe60530645eeda0f4aa55c325
2014-04-24 15:38:03 +02:00
..
install.d Activate venvs in os-*-config elements source install 2014-04-09 17:37:37 +01:00
os-refresh-config refresh-completed always failing 2014-04-09 11:25:05 -04:00
README.md Correct os-refresh-config README.md typo and format 2013-11-28 09:44:04 +08:00
element-deps sort the element-deps to please dib-lint 2014-04-24 15:38:03 +02:00

README.md

Install os-refresh-config

os-refresh-config uses dib-run-parts to run scripts in a pre-defined set of directories. Its intended purpose is to quiesce (pre-configure.d), configure (configure.d), migrate (migration.d), and then activate (post-configure.d) a configuration on first boot or in response to Heat Metadata changes.

To cause a script to be run on every os-refresh-config run, install it into one of the following 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

If you want to have os-refresh-config run on any updates to a particular Resource in the heat stack, you will need at the minimum the following snippet of json in this instance's Metadata:

{
    "OpenStack::Config": {
        "heat": {
            "access_key_id": {"Ref": "ApiKeyResource"},
            "secret_key": {"Fn::GetAtt": [ "ApiKeyResource", "SecretAccessKey" ]},
            "refresh": [ {"resource": "SomeResource"} ],
            "stack": {Ref: 'AWS::Stack'},
            "region": {Ref: 'AWS::Region'}
        }
    }
}

If you would like to signal a wait condition at the end of post-configure.d, a generic name of 'completion-handle' can be used like so:

{
    "completion-handle": {"Ref": "CompletionHandleName"}
}