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
49 lines
1.2 KiB
YAML
49 lines
1.2 KiB
YAML
heat_template_version: ocata
|
|
description: 'Upgrade for via ansible by applying a step related tag'
|
|
|
|
parameters:
|
|
UpgradeStepConfig:
|
|
type: json
|
|
description: Config (ansible yaml) that will be used to step through the deployment.
|
|
default: ''
|
|
|
|
step:
|
|
type: string
|
|
description: Step number of the upgrade
|
|
|
|
resources:
|
|
|
|
AnsibleConfig:
|
|
type: OS::Heat::Value
|
|
properties:
|
|
value:
|
|
str_replace:
|
|
template: CONFIG
|
|
params:
|
|
CONFIG:
|
|
- hosts: localhost
|
|
connection: local
|
|
tasks: {get_param: UpgradeStepConfig}
|
|
|
|
AnsibleUpgradeConfigImpl:
|
|
type: OS::Heat::SoftwareConfig
|
|
properties:
|
|
group: ansible
|
|
options:
|
|
tags:
|
|
str_replace:
|
|
template: "stepSTEP"
|
|
params:
|
|
STEP: {get_param: step}
|
|
inputs:
|
|
- name: role
|
|
config: {get_attr: [AnsibleConfig, value]}
|
|
|
|
outputs:
|
|
OS::stack_id:
|
|
description: The software config which runs ansible with tags
|
|
value: {get_resource: AnsibleUpgradeConfigImpl}
|
|
upgrade_config:
|
|
description: The configuration file used for upgrade
|
|
value: {get_attr: [AnsibleConfig, value]}
|