From beb0633894fbf5e9323b05c9f065cd07877b8de9 Mon Sep 17 00:00:00 2001 From: JUN JIE NAN Date: Thu, 28 Nov 2013 09:44:04 +0800 Subject: [PATCH] Correct os-refresh-config README.md typo and format Replace `run-parts' with `dib-run-parts' since os-refresh-config is using it. Correct markdown code block format. Change-Id: If0184b80d0f35bc30f9799135bd4f659889bcbbd --- elements/os-refresh-config/README.md | 42 ++++++++++++++-------------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/elements/os-refresh-config/README.md b/elements/os-refresh-config/README.md index 232771112..907066da2 100644 --- a/elements/os-refresh-config/README.md +++ b/elements/os-refresh-config/README.md @@ -1,6 +1,7 @@ -Install os-refresh-config. +Install os-refresh-config +========================= -os-refresh-config uses run-parts to run scripts in a pre-defined set +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 @@ -8,33 +9,32 @@ 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 -``` + + /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'} + { + "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"} - } + { + "completion-handle": {"Ref": "CompletionHandleName"} + }