44ef2a3ec1
The new master branch should point now to rocky. So, HOT templates should specify that they might contain features for rocky release [1] Also, this submission updates the yaml validation to use only latest heat_version alias. There are cases in which we will need to set the version for specific templates i.e. mixed versions, so there is added a variable to assign specific templates to specific heat_version aliases, avoiding the introductions of error by bulk replacing the the old version in new releases. [1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b
44 lines
1.2 KiB
YAML
44 lines
1.2 KiB
YAML
heat_template_version: rocky
|
|
description: 'Post-Puppet Config for Pacemaker deployments'
|
|
|
|
parameters:
|
|
servers:
|
|
type: json
|
|
input_values:
|
|
type: json
|
|
description: input values for the software deployments
|
|
|
|
resources:
|
|
|
|
{%- for role in roles %}
|
|
{%- if 'controller' in role.tags %}
|
|
{{role.name}}PostPuppetMaintenanceModeConfig:
|
|
type: OS::Heat::SoftwareConfig
|
|
properties:
|
|
group: script
|
|
config: |
|
|
#!/bin/bash
|
|
pacemaker_status=$(systemctl is-active pacemaker)
|
|
|
|
if [ "$pacemaker_status" = "active" ]; then
|
|
pcs property set maintenance-mode=false
|
|
fi
|
|
|
|
{{role.name}}PostPuppetMaintenanceModeDeployment:
|
|
type: OS::Heat::SoftwareDeployments
|
|
properties:
|
|
name: {{role.name}}PostPuppetMaintenanceModeDeployment
|
|
servers: {get_param: [servers, {{role.name}}]}
|
|
config: {get_resource: {{role.name}}PostPuppetMaintenanceModeConfig}
|
|
input_values: {get_param: input_values}
|
|
|
|
{{role.name}}PostPuppetRestart:
|
|
type: OS::TripleO::Tasks::{{role.name}}PostPuppetRestart
|
|
depends_on: {{role.name}}PostPuppetMaintenanceModeDeployment
|
|
properties:
|
|
servers: {get_param: [servers, {{role.name}}]}
|
|
input_values: {get_param: input_values}
|
|
{%- endif %}
|
|
{%- endfor %}
|
|
|