openstack
/
tripleo-image-elements
Code Issues Proposed changes

Return derived config id when signalling deployments 

Currently signalling via 99-refresh-completed only uses the legacy
curl data payload (e.g that for CFN compatible WaitConditions),
but now we're using it exclusively for signalling SoftwareDeployment
resources, which support a different payload, including deploy_stdout
which is accessible via a resource attribute.

Returning a payload for deploy_stdout containing the derived config ID
is potentially useful as it changes whenever the SoftwareConfig or any
inputs change, thus can be used as a unique identifier for dependent
resources which need to be re-triggered when some config is reapplied,
for example puppet manifests with a dependency on hieradata applied
via a SoftwareDeployment.

get_attr: [ControllerDeployment, deploy_stdout]

Partial-Bug: #1463092
Change-Id: Ic62b6303795f70f3b9ace46731a21d1c0e7fe6c7
This commit is contained in:
Steven Hardy 2015-06-10 18:51:10 +01:00
parent 00102e4d93
commit e6b9609473
1 changed files with 33 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
elements/os-refresh-config/os-refresh-config/post-configure.d/99-refresh-completed
View File

@ -24,6 +24,19 @@ call_curl() {
fi
}
call_curl_deployment() {
local method=$1
local url=$2
local stdout=$3
local output=$(mktemp)
status=$(curl -s -w %{http_code} -X $method -H 'Content-Type:' -o $output --data-binary "{\"deploy_stdout\": \"$stdout\", \"deploy_status_code\": \"0\"}" $url)
cat $output
rm $output
if [ "$status" != "200" ]; then
exit 1
fi
}
# Signals use POST, wait handles use PUT
if [ -n "$HANDLE" ]; then
call_curl PUT $HANDLE
@ -35,11 +48,25 @@ fi
# This extracts "deploy_signal_id" from any deployments of group "os-apply-config"
# deploy_signal_id is a pre-signed URL when CFN_SIGNAL is specified, it's not
# included if NO_SIGNAL is specified. Won't yet work with HEAT_SIGNAL.
DEPLOYMENT_HANDLES=$(os-apply-config --key deployments --type raw --key-default "" | \
jq -r "map(select(.group == \"os-apply-config\") | .inputs | \
map(select(.name == \"deploy_signal_id\"))) | .[][].value")
for url in ${DEPLOYMENT_HANDLES}
# We also include the id, which provides a means to identify when a config
# being deployed has changed. DEPLOYMENTS is a list of concatenated ID+URL.
#
# The jq is really hard to read, so here's the process line by line:
# 1. Extract all deployments data via os-apply-config
# 2. Select all which have a config group of "os-apply-config"
# 3. Filter further for only deployments with a deploy_signal_id input
# thus avoiding NO_SIGNAL deployments
# 4. Extract and join the "id" key and the input value for deploy_signal_id
# 5. Print the elements of the resulting list to enable for loop iteration
DEPLOYMENTS=$(os-apply-config --key deployments --type raw --key-default "" |
jq -r "map(select(.group == \"os-apply-config\") |
select(.inputs[].name == \"deploy_signal_id\") |
.id + (.inputs | map(select(.name == \"deploy_signal_id\")) | .[].value)) |
.[]")
for dep in ${DEPLOYMENTS}
do
echo "Signalling deploy_signal_handle=$url"
call_curl POST $url
DEPLOY_ID=$(echo $dep | sed "s/http.*$//")
DEPLOY_URL=$(echo $dep | sed "s/^.*http/http/")
echo "Signalling os-apply-config deployment $DEPLOY_ID $DEPLOY_URL"
call_curl_deployment POST $DEPLOY_URL "os-apply-config deployment $DEPLOY_ID completed"
done