3c6ec654b4
Heat now supports release name aliases, so we can replace the inconsistent mix of date related versions with one consistent version that aligns with the supported version of heat for this t-h-t branch. This should also help new users who sometimes copy/paste old templates and discover intrinsic functions in the t-h-t docs don't work because their template version is too old. Change-Id: Ib415e7290fea27447460baa280291492df197e54
40 lines
1.1 KiB
YAML
40 lines
1.1 KiB
YAML
heat_template_version: ocata
|
|
|
|
description: >
|
|
Example extra config for post-deployment, this re-runs every update
|
|
|
|
# Note extra parameters can be defined, then passed data via the
|
|
# environment parameter_defaults, without modifying the parent template
|
|
parameters:
|
|
servers:
|
|
type: json
|
|
# This is provided via parameter_defaults from tripleoclient
|
|
# it changes to a new timestamp every update, so we can use it to
|
|
# trigger the deployment to run even though it and the config are
|
|
# otherwise unchanged
|
|
DeployIdentifier:
|
|
type: string
|
|
|
|
resources:
|
|
|
|
ExtraConfig:
|
|
type: OS::Heat::SoftwareConfig
|
|
properties:
|
|
group: script
|
|
inputs:
|
|
- name: deploy_identifier
|
|
config: |
|
|
#!/bin/sh
|
|
echo "extra_update $deploy_identifier" >> /root/extra_update
|
|
|
|
ExtraDeployments:
|
|
type: OS::Heat::SoftwareDeployments
|
|
properties:
|
|
name: ExtraDeployments
|
|
servers: {get_param: servers}
|
|
config: {get_resource: ExtraConfig}
|
|
# Do this on CREATE/UPDATE (which is actually the default)
|
|
actions: ['CREATE', 'UPDATE']
|
|
input_values:
|
|
deploy_identifier: {get_param: DeployIdentifier}
|