History

Steve Baker dfbb0549fe Prepare os-*-config for CI Specify pip install --pre so that local git built packages will be installed if available. It should be possible to always specify --pre since public repos do not have snapshot release packages for these tools Change-Id: Id2e539ba72ac2ef8d39a3ab694991e9b8bf724d7		2014-06-25 16:02:28 +12:00
..
install.d	Prepare os-*-config for CI	2014-06-25 16:02:28 +12:00
os-refresh-config	Error out when complete waitcondition fails	2014-05-16 16:09:17 +12: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"}
}