2017-03-01 13:57:13 +00:00
|
|
|
# certain initialization steps (run in a container) will occur
|
2017-03-29 14:43:45 -06:00
|
|
|
# on the role marked as primary controller or the first role listed
|
2017-11-20 14:48:03 +00:00
|
|
|
{%- if enabled_roles is not defined or enabled_roles == [] -%}
|
2017-09-11 14:39:06 +01:00
|
|
|
# On upgrade certain roles can be disabled for operator driven upgrades
|
|
|
|
# See major_upgrade_steps.j2.yaml and post-upgrade.j2.yaml
|
|
|
|
{%- set enabled_roles = roles -%}
|
|
|
|
{%- endif -%}
|
|
|
|
{%- set primary_role = [enabled_roles[0]] -%}
|
|
|
|
{%- for role in enabled_roles -%}
|
2017-03-29 14:43:45 -06:00
|
|
|
{%- if 'primary' in role.tags and 'controller' in role.tags -%}
|
|
|
|
{%- set _ = primary_role.pop() -%}
|
|
|
|
{%- set _ = primary_role.append(role) -%}
|
|
|
|
{%- endif -%}
|
|
|
|
{%- endfor -%}
|
|
|
|
{%- set primary_role_name = primary_role[0].name -%}
|
|
|
|
# primary role is: {{primary_role_name}}
|
2017-04-11 11:44:46 +01:00
|
|
|
{% set deploy_steps_max = 6 -%}
|
2017-07-21 11:43:25 +01:00
|
|
|
{% set update_steps_max = 6 -%}
|
2018-03-12 17:02:36 +01:00
|
|
|
{% set pre_upgrade_rolling_steps_max = 1 -%}
|
2017-08-04 14:55:48 +03:00
|
|
|
{% set upgrade_steps_max = 6 -%}
|
2018-01-17 12:28:55 +05:30
|
|
|
{% set post_upgrade_steps_max = 4 -%}
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
{% set fast_forward_upgrade_steps_max = 9 -%}
|
|
|
|
{% set fast_forward_upgrade_prep_steps_max = 3 -%}
|
2018-01-23 22:43:49 +05:30
|
|
|
{% set post_update_steps_max = 4 -%}
|
2017-04-11 11:44:46 +01:00
|
|
|
|
2018-03-05 19:28:35 +01:00
|
|
|
heat_template_version: rocky
|
2017-03-01 13:57:13 +00:00
|
|
|
|
|
|
|
description: >
|
|
|
|
Post-deploy configuration steps via puppet for all roles,
|
|
|
|
as defined in ../roles_data.yaml
|
|
|
|
|
|
|
|
parameters:
|
|
|
|
servers:
|
|
|
|
type: json
|
|
|
|
description: Mapping of Role name e.g Controller to a list of servers
|
2017-05-06 02:19:47 +02:00
|
|
|
stack_name:
|
|
|
|
type: string
|
|
|
|
description: Name of the topmost stack
|
2017-03-01 13:57:13 +00:00
|
|
|
role_data:
|
|
|
|
type: json
|
|
|
|
description: Mapping of Role name e.g Controller to the per-role data
|
|
|
|
DeployIdentifier:
|
|
|
|
default: ''
|
|
|
|
type: string
|
|
|
|
description: >
|
|
|
|
Setting this to a unique value will re-run any deployment tasks which
|
|
|
|
perform configuration on a Heat stack-update.
|
2018-05-07 15:54:11 -06:00
|
|
|
deployment_source_hosts:
|
|
|
|
default: 'undercloud'
|
|
|
|
type: string
|
|
|
|
description: Host or hostgroup that runs the deployment
|
|
|
|
deployment_target_hosts:
|
|
|
|
default: 'overcloud'
|
|
|
|
type: string
|
|
|
|
description: Host or hostgroup that consists of the target systems for the deployment
|
2017-03-01 13:57:13 +00:00
|
|
|
EndpointMap:
|
|
|
|
default: {}
|
|
|
|
description: Mapping of service endpoint -> protocol. Typically set
|
|
|
|
via parameter_defaults in the resource registry.
|
|
|
|
type: json
|
Fix ConfigDebug for puppet host runs
Before pike we used to be able to add -e environments/config-debug.yaml
and that would give us debug logs for puppet. With the move to ansible
running puppet we lost this feature.
Let's make sure that the old ConfigDebug variable still works with
the ansible playbook-based deploy steps. With this patch and ConfigDebug
set to true, we correctly get the puppet debug logs:
TASK [debug] *******************************************************************
ok: [localhost] => {
"(outputs.stderr|default('')).split('\n')|union(outputs.stdout_lines|default([]))": [
"Warning: Undefined variable 'deploy_config_name'; ",
" (file & line not available)",
"Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README. at [\"/etc/puppet/modules/ntp/manifests/init.pp\", 54]:[\"/etc/puppet/modules/tripleo/manifests/profile/base/time/ntp.pp\", 29]",
" (at /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')",
"Debug: Runtime environment: puppet_version=4.8.2, ruby_version=2.0.0, run_mode=user, default_encoding=UTF-8",
"Debug: Loading external facts from /etc/puppet/modules/openstacklib/facts.d",
"Debug: Loading external facts from /var/lib/puppet/facts.d",
....
Change-Id: Ia726fb8ca4a6f7bbbd7a1284d76ff42df6825d01
Closes-Bug: #1722752
2017-10-11 12:47:01 +02:00
|
|
|
ConfigDebug:
|
|
|
|
default: false
|
|
|
|
description: Whether to run config management (e.g. Puppet) in debug mode.
|
|
|
|
type: boolean
|
2018-03-06 13:43:07 -05:00
|
|
|
EnablePuppet:
|
|
|
|
default: true
|
|
|
|
description: Whether to run the puppet (baremetal) deployment tasks.
|
|
|
|
type: boolean
|
2017-06-26 09:53:31 -04:00
|
|
|
DockerPuppetDebug:
|
|
|
|
type: string
|
|
|
|
default: ''
|
|
|
|
description: Set to True to enable debug logging with docker-puppet.py
|
2017-08-25 23:01:24 -04:00
|
|
|
DockerPuppetProcessCount:
|
|
|
|
type: number
|
2018-07-05 14:01:10 +03:00
|
|
|
default: 6
|
2017-08-25 23:01:24 -04:00
|
|
|
description: Number of concurrent processes to use when running docker-puppet to generate config files.
|
2017-05-24 18:45:59 +02:00
|
|
|
ctlplane_service_ips:
|
|
|
|
type: json
|
2018-01-12 17:04:12 -05:00
|
|
|
blacklisted_ip_addresses:
|
|
|
|
description: List of IP addresses belong to blacklisted servers
|
|
|
|
type: comma_delimited_list
|
|
|
|
default: []
|
2018-01-12 17:17:14 -05:00
|
|
|
blacklisted_hostnames:
|
|
|
|
description: List of hostnames belong to blacklisted servers
|
|
|
|
type: comma_delimited_list
|
|
|
|
default: []
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
FastForwardUpgradeReleases:
|
|
|
|
type: comma_delimited_list
|
2018-02-24 22:40:28 +01:00
|
|
|
default: ['ocata', 'pike', 'queens']
|
|
|
|
description: List of releases to fast forward through during upgrade. Last release in list is used for post steps.
|
2018-01-12 15:52:26 -05:00
|
|
|
ssh_known_hosts_hostnames:
|
|
|
|
description: Mapping of hostname to ssh known hosts entry
|
|
|
|
type: json
|
2017-03-01 13:57:13 +00:00
|
|
|
|
2017-05-06 02:19:47 +02:00
|
|
|
conditions:
|
|
|
|
{% for step in range(1, deploy_steps_max) %}
|
|
|
|
WorkflowTasks_Step{{step}}_Enabled:
|
|
|
|
or:
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for role in enabled_roles %}
|
2017-05-06 02:19:47 +02:00
|
|
|
- not:
|
|
|
|
equals:
|
2017-09-12 22:29:13 +02:00
|
|
|
- get_param: [role_data, {{role.name}}, workflow_tasks, step{{step}}]
|
2017-05-06 02:19:47 +02:00
|
|
|
- ''
|
|
|
|
- False
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
2017-05-06 02:19:47 +02:00
|
|
|
{% endfor %}
|
|
|
|
|
2017-03-01 13:57:13 +00:00
|
|
|
resources:
|
|
|
|
|
2017-05-03 17:12:55 +01:00
|
|
|
RoleConfig:
|
2017-03-01 13:57:13 +00:00
|
|
|
type: OS::Heat::SoftwareConfig
|
|
|
|
properties:
|
2017-05-03 17:12:55 +01:00
|
|
|
group: ansible
|
|
|
|
options:
|
|
|
|
modulepath: /usr/share/ansible-modules
|
2017-03-01 13:57:13 +00:00
|
|
|
inputs:
|
2017-05-03 17:12:55 +01:00
|
|
|
- name: step
|
2018-05-14 11:15:09 -07:00
|
|
|
- name: tripleo_role_name
|
2017-05-03 17:12:55 +01:00
|
|
|
- name: update_identifier
|
|
|
|
- name: bootstrap_server_id
|
Fix ConfigDebug for puppet host runs
Before pike we used to be able to add -e environments/config-debug.yaml
and that would give us debug logs for puppet. With the move to ansible
running puppet we lost this feature.
Let's make sure that the old ConfigDebug variable still works with
the ansible playbook-based deploy steps. With this patch and ConfigDebug
set to true, we correctly get the puppet debug logs:
TASK [debug] *******************************************************************
ok: [localhost] => {
"(outputs.stderr|default('')).split('\n')|union(outputs.stdout_lines|default([]))": [
"Warning: Undefined variable 'deploy_config_name'; ",
" (file & line not available)",
"Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README. at [\"/etc/puppet/modules/ntp/manifests/init.pp\", 54]:[\"/etc/puppet/modules/tripleo/manifests/profile/base/time/ntp.pp\", 29]",
" (at /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')",
"Debug: Runtime environment: puppet_version=4.8.2, ruby_version=2.0.0, run_mode=user, default_encoding=UTF-8",
"Debug: Loading external facts from /etc/puppet/modules/openstacklib/facts.d",
"Debug: Loading external facts from /var/lib/puppet/facts.d",
....
Change-Id: Ia726fb8ca4a6f7bbbd7a1284d76ff42df6825d01
Closes-Bug: #1722752
2017-10-11 12:47:01 +02:00
|
|
|
- name: enable_debug
|
2018-03-06 13:43:07 -05:00
|
|
|
- name: enable_puppet
|
2017-06-26 09:53:31 -04:00
|
|
|
- name: docker_puppet_debug
|
2017-08-25 23:01:24 -04:00
|
|
|
- name: docker_puppet_process_count
|
2017-12-04 13:55:10 +00:00
|
|
|
- name: role_data_step_config
|
|
|
|
- name: role_data_puppet_config
|
|
|
|
type: Json
|
|
|
|
- name: role_data_docker_config_scripts
|
|
|
|
type: Json
|
|
|
|
- name: role_data_docker_puppet_tasks
|
|
|
|
type: Json
|
|
|
|
- name: role_data_docker_config
|
|
|
|
type: Json
|
|
|
|
- name: role_data_kolla_config
|
|
|
|
type: Json
|
|
|
|
|
2017-07-20 15:04:10 +01:00
|
|
|
config:
|
|
|
|
str_replace:
|
|
|
|
template: |
|
|
|
|
- hosts: localhost
|
|
|
|
connection: local
|
|
|
|
tasks:
|
|
|
|
_TASKS
|
|
|
|
params:
|
|
|
|
_TASKS: {get_file: deploy-steps-tasks.yaml}
|
2017-03-01 13:57:13 +00:00
|
|
|
|
2017-10-06 11:41:59 +02:00
|
|
|
ExternalDeployTasks:
|
|
|
|
type: OS::Heat::Value
|
|
|
|
properties:
|
|
|
|
type: comma_delimited_list
|
|
|
|
value:
|
|
|
|
yaql:
|
|
|
|
# processing from per-role unique tasks into globally unique tasks
|
|
|
|
expression: coalesce($.data, []).flatten().distinct()
|
|
|
|
data:
|
|
|
|
{%- for role in enabled_roles %}
|
|
|
|
- get_param: [role_data, {{role.name}}, external_deploy_tasks]
|
|
|
|
{%- endfor %}
|
|
|
|
|
2017-11-22 17:45:19 +00:00
|
|
|
ExternalPostDeployTasks:
|
|
|
|
type: OS::Heat::Value
|
|
|
|
properties:
|
|
|
|
type: comma_delimited_list
|
|
|
|
value:
|
|
|
|
yaql:
|
|
|
|
# processing from per-role unique tasks into globally unique tasks
|
|
|
|
expression: coalesce($.data, []).flatten().distinct()
|
|
|
|
data:
|
|
|
|
{%- for role in enabled_roles %}
|
|
|
|
- get_param: [role_data, {{role.name}}, external_post_deploy_tasks]
|
|
|
|
{%- endfor %}
|
|
|
|
|
2017-05-06 02:19:47 +02:00
|
|
|
{%- for step in range(1, deploy_steps_max) %}
|
2017-09-12 22:29:13 +02:00
|
|
|
# BEGIN workflow_tasks handling
|
2017-05-06 02:19:47 +02:00
|
|
|
WorkflowTasks_Step{{step}}:
|
|
|
|
type: OS::Mistral::Workflow
|
|
|
|
condition: WorkflowTasks_Step{{step}}_Enabled
|
|
|
|
depends_on:
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- if step == 1 %}
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for dep in enabled_roles %}
|
2017-05-06 02:19:47 +02:00
|
|
|
- {{dep.name}}PreConfig
|
|
|
|
- {{dep.name}}ArtifactsDeploy
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
|
|
|
{%- else %}
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for dep in enabled_roles %}
|
2017-05-06 02:19:47 +02:00
|
|
|
- {{dep.name}}Deployment_Step{{step -1}}
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
|
|
|
{%- endif %}
|
2017-05-06 02:19:47 +02:00
|
|
|
properties:
|
2017-09-12 22:29:13 +02:00
|
|
|
name: {list_join: [".", ["tripleo", {get_param: stack_name}, "workflow_tasks", "step{{step}}"]]}
|
2017-05-06 02:19:47 +02:00
|
|
|
type: direct
|
2017-09-13 19:34:14 +02:00
|
|
|
tags:
|
|
|
|
- tripleo-heat-templates-managed
|
|
|
|
- {get_param: stack_name}
|
2017-05-06 02:19:47 +02:00
|
|
|
tasks:
|
|
|
|
yaql:
|
|
|
|
expression: $.data.where($ != '').select($.get('step{{step}}')).where($ != null).flatten()
|
|
|
|
data:
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for role in enabled_roles %}
|
2017-09-12 22:29:13 +02:00
|
|
|
- get_param: [role_data, {{role.name}}, workflow_tasks]
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
2017-05-06 02:19:47 +02:00
|
|
|
|
|
|
|
WorkflowTasks_Step{{step}}_Execution:
|
2018-04-16 18:29:52 +02:00
|
|
|
type: OS::TripleO::WorkflowSteps
|
2017-05-06 02:19:47 +02:00
|
|
|
condition: WorkflowTasks_Step{{step}}_Enabled
|
|
|
|
depends_on: WorkflowTasks_Step{{step}}
|
|
|
|
properties:
|
|
|
|
actions:
|
|
|
|
CREATE:
|
|
|
|
workflow: { get_resource: WorkflowTasks_Step{{step}} }
|
2017-05-24 18:45:59 +02:00
|
|
|
params:
|
|
|
|
env:
|
2018-05-25 13:01:18 +00:00
|
|
|
heat_stack_name: { get_param: stack_name }
|
2017-05-24 18:45:59 +02:00
|
|
|
service_ips: { get_param: ctlplane_service_ips }
|
2017-07-14 13:38:47 +02:00
|
|
|
role_merged_configs:
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- for r in roles %}
|
2017-07-14 13:38:47 +02:00
|
|
|
{{r.name}}: {get_param: [role_data, {{r.name}}, merged_config_settings]}
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
2018-01-12 17:04:12 -05:00
|
|
|
blacklisted_ip_addresses: {get_param: blacklisted_ip_addresses}
|
2018-01-12 17:17:14 -05:00
|
|
|
blacklisted_hostnames: {get_param: blacklisted_hostnames}
|
2017-07-20 13:44:57 +02:00
|
|
|
evaluate_env: false
|
2017-05-06 02:19:47 +02:00
|
|
|
UPDATE:
|
|
|
|
workflow: { get_resource: WorkflowTasks_Step{{step}} }
|
2017-05-24 18:45:59 +02:00
|
|
|
params:
|
|
|
|
env:
|
2018-05-25 13:01:18 +00:00
|
|
|
heat_stack_name: { get_param: stack_name }
|
2017-05-24 18:45:59 +02:00
|
|
|
service_ips: { get_param: ctlplane_service_ips }
|
2017-07-14 13:38:47 +02:00
|
|
|
role_merged_configs:
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- for r in roles %}
|
2017-07-14 13:38:47 +02:00
|
|
|
{{r.name}}: {get_param: [role_data, {{r.name}}, merged_config_settings]}
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
2018-01-12 17:04:12 -05:00
|
|
|
blacklisted_ip_addresses: {get_param: blacklisted_ip_addresses}
|
2018-01-12 17:17:14 -05:00
|
|
|
blacklisted_hostnames: {get_param: blacklisted_hostnames}
|
2017-07-20 13:44:57 +02:00
|
|
|
evaluate_env: false
|
2017-05-06 02:19:47 +02:00
|
|
|
always_update: true
|
2017-09-12 22:29:13 +02:00
|
|
|
# END workflow_tasks handling
|
2017-05-06 02:19:47 +02:00
|
|
|
{% endfor %}
|
|
|
|
|
2017-10-19 18:06:42 +01:00
|
|
|
BootstrapServerId:
|
|
|
|
type: OS::Heat::Value
|
|
|
|
properties:
|
|
|
|
value:
|
|
|
|
yaql:
|
|
|
|
expression: $.data.items().orderBy($[0]).first()[1]
|
|
|
|
data: {get_param: [servers, {{primary_role_name}}]}
|
|
|
|
|
2017-09-11 14:39:06 +01:00
|
|
|
# Artifacts config and HostPrepConfig is done on all roles, not only
|
|
|
|
# enabled_roles, because on upgrade we need to write the json files
|
|
|
|
# for the operator driven upgrade scripts (the ansible steps consume them)
|
2017-03-01 13:57:13 +00:00
|
|
|
{% for role in roles %}
|
2017-09-11 14:39:06 +01:00
|
|
|
# Prepare host tasks for {{role.name}}
|
2017-03-01 13:57:13 +00:00
|
|
|
{{role.name}}ArtifactsConfig:
|
|
|
|
type: ../puppet/deploy-artifacts.yaml
|
|
|
|
|
|
|
|
{{role.name}}ArtifactsDeploy:
|
|
|
|
type: OS::Heat::StructuredDeploymentGroup
|
|
|
|
properties:
|
2017-09-20 12:48:19 -04:00
|
|
|
name: {{role.name}}ArtifactsDeploy
|
2017-03-01 13:57:13 +00:00
|
|
|
servers: {get_param: [servers, {{role.name}}]}
|
|
|
|
config: {get_resource: {{role.name}}ArtifactsConfig}
|
|
|
|
|
2017-03-09 14:47:12 +01:00
|
|
|
{{role.name}}HostPrepConfig:
|
|
|
|
type: OS::Heat::SoftwareConfig
|
|
|
|
properties:
|
|
|
|
group: ansible
|
|
|
|
options:
|
|
|
|
modulepath: /usr/share/ansible-modules
|
2017-04-10 16:16:29 +01:00
|
|
|
config:
|
|
|
|
str_replace:
|
|
|
|
template: _PLAYBOOK
|
|
|
|
params:
|
|
|
|
_PLAYBOOK:
|
|
|
|
- hosts: localhost
|
|
|
|
connection: local
|
|
|
|
vars:
|
2017-07-13 13:40:48 +01:00
|
|
|
docker_puppet_script: {get_file: ../docker/docker-puppet.py}
|
2017-10-19 18:06:42 +01:00
|
|
|
bootstrap_server_id: {get_attr: [BootstrapServerId, value]}
|
2017-04-10 16:16:29 +01:00
|
|
|
tasks:
|
|
|
|
# Join host_prep_tasks with the other per-host configuration
|
2017-08-30 15:43:16 +02:00
|
|
|
list_concat:
|
|
|
|
- {get_param: [role_data, {{role.name}}, host_prep_tasks]}
|
|
|
|
-
|
2017-12-04 13:55:10 +00:00
|
|
|
# FIXME: can we move docker-puppet somewhere so it's installed via a package?
|
2017-08-30 15:43:16 +02:00
|
|
|
- name: Create /var/lib/docker-puppet
|
2017-10-20 11:00:18 +02:00
|
|
|
file: path=/var/lib/docker-puppet state=directory setype=svirt_sandbox_file_t selevel=s0 recurse=true
|
2017-08-30 15:43:16 +02:00
|
|
|
- name: Write docker-puppet.py
|
2017-09-20 12:48:19 -04:00
|
|
|
copy: content="{{ '{{' }}docker_puppet_script{{ '}}' }}" dest=/var/lib/docker-puppet/docker-puppet.py force=yes mode=0600
|
2017-03-09 14:47:12 +01:00
|
|
|
|
|
|
|
{{role.name}}HostPrepDeployment:
|
|
|
|
type: OS::Heat::SoftwareDeploymentGroup
|
|
|
|
properties:
|
2017-09-20 12:48:19 -04:00
|
|
|
name: {{role.name}}HostPrepDeployment
|
2017-03-09 14:47:12 +01:00
|
|
|
servers: {get_param: [servers, {{role.name}}]}
|
|
|
|
config: {get_resource: {{role.name}}HostPrepConfig}
|
2017-09-11 14:39:06 +01:00
|
|
|
{% endfor %}
|
2017-03-09 14:47:12 +01:00
|
|
|
|
2017-09-11 14:39:06 +01:00
|
|
|
# BEGIN CONFIG STEPS, only on enabled_roles
|
|
|
|
{%- for role in enabled_roles %}
|
2017-04-25 15:13:38 +00:00
|
|
|
{{role.name}}PreConfig:
|
|
|
|
type: OS::TripleO::Tasks::{{role.name}}PreConfig
|
2017-05-03 17:12:55 +01:00
|
|
|
depends_on: {{role.name}}HostPrepDeployment
|
2017-03-01 13:57:13 +00:00
|
|
|
properties:
|
2017-04-25 15:13:38 +00:00
|
|
|
servers: {get_param: [servers, {{role.name}}]}
|
2017-03-01 13:57:13 +00:00
|
|
|
input_values:
|
|
|
|
update_identifier: {get_param: DeployIdentifier}
|
|
|
|
|
2017-09-11 14:39:06 +01:00
|
|
|
# Deployment steps for {{role.name}}
|
|
|
|
# A single config is re-applied with an incrementing step number
|
2017-04-11 11:44:46 +01:00
|
|
|
{% for step in range(1, deploy_steps_max) %}
|
2017-03-01 13:57:13 +00:00
|
|
|
{{role.name}}Deployment_Step{{step}}:
|
2017-07-21 17:45:09 +01:00
|
|
|
type: OS::TripleO::DeploymentSteps
|
2017-03-01 13:57:13 +00:00
|
|
|
depends_on:
|
2017-05-06 02:19:47 +02:00
|
|
|
- WorkflowTasks_Step{{step}}_Execution
|
|
|
|
# TODO(gfidente): the following if/else condition
|
|
|
|
# replicates what is already defined for the
|
|
|
|
# WorkflowTasks_StepX resource and can be remove
|
|
|
|
# if https://bugs.launchpad.net/heat/+bug/1700569
|
|
|
|
# is fixed.
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- if step == 1 %}
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for dep in enabled_roles %}
|
2017-05-06 02:19:47 +02:00
|
|
|
- {{dep.name}}PreConfig
|
|
|
|
- {{dep.name}}ArtifactsDeploy
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
|
|
|
{%- else %}
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for dep in enabled_roles %}
|
2017-03-01 13:57:13 +00:00
|
|
|
- {{dep.name}}Deployment_Step{{step -1}}
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
|
|
|
{%- endif %}
|
2017-03-01 13:57:13 +00:00
|
|
|
properties:
|
|
|
|
name: {{role.name}}Deployment_Step{{step}}
|
|
|
|
servers: {get_param: [servers, {{role.name}}]}
|
2017-05-03 17:12:55 +01:00
|
|
|
config: {get_resource: RoleConfig}
|
2017-03-01 13:57:13 +00:00
|
|
|
input_values:
|
|
|
|
step: {{step}}
|
2018-05-14 11:15:09 -07:00
|
|
|
tripleo_role_name: {{role.name}}
|
2017-03-01 13:57:13 +00:00
|
|
|
update_identifier: {get_param: DeployIdentifier}
|
2017-10-19 18:06:42 +01:00
|
|
|
bootstrap_server_id: {get_attr: [BootstrapServerId, value]}
|
Fix ConfigDebug for puppet host runs
Before pike we used to be able to add -e environments/config-debug.yaml
and that would give us debug logs for puppet. With the move to ansible
running puppet we lost this feature.
Let's make sure that the old ConfigDebug variable still works with
the ansible playbook-based deploy steps. With this patch and ConfigDebug
set to true, we correctly get the puppet debug logs:
TASK [debug] *******************************************************************
ok: [localhost] => {
"(outputs.stderr|default('')).split('\n')|union(outputs.stdout_lines|default([]))": [
"Warning: Undefined variable 'deploy_config_name'; ",
" (file & line not available)",
"Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README. at [\"/etc/puppet/modules/ntp/manifests/init.pp\", 54]:[\"/etc/puppet/modules/tripleo/manifests/profile/base/time/ntp.pp\", 29]",
" (at /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')",
"Debug: Runtime environment: puppet_version=4.8.2, ruby_version=2.0.0, run_mode=user, default_encoding=UTF-8",
"Debug: Loading external facts from /etc/puppet/modules/openstacklib/facts.d",
"Debug: Loading external facts from /var/lib/puppet/facts.d",
....
Change-Id: Ia726fb8ca4a6f7bbbd7a1284d76ff42df6825d01
Closes-Bug: #1722752
2017-10-11 12:47:01 +02:00
|
|
|
enable_debug: {get_param: ConfigDebug}
|
2018-03-06 13:43:07 -05:00
|
|
|
enable_puppet: {get_param: EnablePuppet}
|
2017-06-26 09:53:31 -04:00
|
|
|
docker_puppet_debug: {get_param: DockerPuppetDebug}
|
2017-08-25 23:01:24 -04:00
|
|
|
docker_puppet_process_count: {get_param: DockerPuppetProcessCount}
|
2017-12-04 13:55:10 +00:00
|
|
|
role_data_step_config: {get_param: [role_data, {{role.name}}, step_config]}
|
|
|
|
role_data_puppet_config: {get_param: [role_data, {{role.name}}, puppet_config]}
|
|
|
|
role_data_docker_config_scripts: {get_param: [role_data, {{role.name}}, docker_config_scripts]}
|
|
|
|
role_data_docker_puppet_tasks: {get_param: [role_data, {{role.name}}, docker_puppet_tasks]}
|
|
|
|
role_data_docker_config: {get_param: [role_data, {{role.name}}, docker_config]}
|
|
|
|
role_data_kolla_config: {get_param: [role_data, {{role.name}}, kolla_config]}
|
|
|
|
deploy_steps_max: {{deploy_steps_max}}
|
|
|
|
|
2017-03-01 13:57:13 +00:00
|
|
|
{% endfor %}
|
2017-05-03 17:12:55 +01:00
|
|
|
# END CONFIG STEPS
|
2017-03-01 13:57:13 +00:00
|
|
|
|
2017-06-08 23:18:44 +02:00
|
|
|
# Note, this should be the last step to execute configuration changes.
|
|
|
|
# Ensure that all {{role.name}}ExtraConfigPost steps are executed
|
|
|
|
# after all the previous deployment steps.
|
|
|
|
{{role.name}}ExtraConfigPost:
|
2017-03-01 13:57:13 +00:00
|
|
|
depends_on:
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for dep in enabled_roles %}
|
2017-11-10 15:32:42 +01:00
|
|
|
- {{dep.name}}Deployment_Step{{deploy_steps_max - 1}}
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
2017-06-08 23:18:44 +02:00
|
|
|
type: OS::TripleO::NodeExtraConfigPost
|
2017-03-01 13:57:13 +00:00
|
|
|
properties:
|
2017-06-08 23:18:44 +02:00
|
|
|
servers: {get_param: [servers, {{role.name}}]}
|
2017-03-01 13:57:13 +00:00
|
|
|
|
2017-06-08 23:18:44 +02:00
|
|
|
# The {{role.name}}PostConfig steps are in charge of
|
|
|
|
# quiescing all services, i.e. in the Controller case,
|
|
|
|
# we should run a full service reload.
|
|
|
|
{{role.name}}PostConfig:
|
|
|
|
type: OS::TripleO::Tasks::{{role.name}}PostConfig
|
2017-03-01 13:57:13 +00:00
|
|
|
depends_on:
|
2017-09-11 14:39:06 +01:00
|
|
|
{%- for dep in enabled_roles %}
|
2017-06-08 23:18:44 +02:00
|
|
|
- {{dep.name}}ExtraConfigPost
|
2017-07-17 10:15:13 +02:00
|
|
|
{%- endfor %}
|
2017-03-01 13:57:13 +00:00
|
|
|
properties:
|
2017-06-08 23:18:44 +02:00
|
|
|
servers: {get_param: servers}
|
|
|
|
input_values:
|
|
|
|
update_identifier: {get_param: DeployIdentifier}
|
|
|
|
|
2017-03-01 13:57:13 +00:00
|
|
|
|
|
|
|
{% endfor %}
|
2017-07-20 17:11:44 +01:00
|
|
|
|
|
|
|
outputs:
|
|
|
|
RoleConfig:
|
|
|
|
description: Mapping of config data for all roles
|
|
|
|
value:
|
2017-12-04 13:55:10 +00:00
|
|
|
global_vars:
|
|
|
|
deploy_steps_max: {{deploy_steps_max}}
|
2018-01-12 15:52:26 -05:00
|
|
|
ssh_known_hosts: {get_param: ssh_known_hosts_hostnames}
|
2017-11-22 18:37:39 +00:00
|
|
|
common_deploy_steps_tasks: {get_file: deploy-steps-tasks.yaml}
|
2018-02-06 18:58:49 +01:00
|
|
|
docker_puppet_script: {get_file: ../docker/docker-puppet.py}
|
2017-09-20 12:48:19 -04:00
|
|
|
deploy_steps_playbook:
|
|
|
|
str_replace:
|
|
|
|
params:
|
2017-10-19 18:06:42 +01:00
|
|
|
BOOTSTRAP_SERVER_ID: {get_attr: [BootstrapServerId, value]}
|
2018-05-07 15:54:11 -06:00
|
|
|
DEPLOY_SOURCE_HOST: {get_param: deployment_source_hosts}
|
|
|
|
DEPLOY_TARGET_HOST: {get_param: deployment_target_hosts}
|
2017-09-20 12:48:19 -04:00
|
|
|
template: |
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: DEPLOY_SOURCE_HOST
|
|
|
|
name: Gather facts from undercloud
|
2017-11-07 07:31:25 -05:00
|
|
|
gather_facts: yes
|
|
|
|
become: false
|
2017-11-08 10:49:50 -05:00
|
|
|
tags:
|
|
|
|
- facts
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
name: Gather facts from overcloud
|
2017-10-20 13:43:38 +02:00
|
|
|
gather_facts: yes
|
2017-11-08 10:49:50 -05:00
|
|
|
tags:
|
|
|
|
- facts
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2017-12-04 13:55:10 +00:00
|
|
|
- hosts: all
|
|
|
|
name: Load global variables
|
|
|
|
gather_facts: no
|
|
|
|
tasks:
|
|
|
|
- include_vars: global_vars.yaml
|
2018-01-25 08:08:59 +02:00
|
|
|
tags:
|
|
|
|
- always
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
2018-01-12 15:52:26 -05:00
|
|
|
name: Common roles for TripleO servers
|
2017-12-04 11:49:05 -08:00
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
|
|
|
roles:
|
|
|
|
- tripleo-bootstrap
|
2018-01-12 15:52:26 -05:00
|
|
|
- tripleo-ssh-known-hosts
|
2017-12-04 11:49:05 -08:00
|
|
|
tags:
|
2018-01-12 15:52:26 -05:00
|
|
|
- common_roles
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
|
2018-04-04 09:57:49 -04:00
|
|
|
name: Overcloud deploy step tasks for step 0
|
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
|
|
|
vars:
|
|
|
|
bootstrap_server_id: BOOTSTRAP_SERVER_ID
|
|
|
|
step: 0
|
|
|
|
tasks:
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/deploy_steps_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2018-04-04 09:57:49 -04:00
|
|
|
{%- endfor %}
|
|
|
|
tags:
|
|
|
|
- overcloud
|
|
|
|
- deploy_steps
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
|
2017-09-20 12:48:19 -04:00
|
|
|
name: Server deployments
|
2017-10-20 13:43:38 +02:00
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
2017-09-20 12:48:19 -04:00
|
|
|
tasks:
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: {{role.name}}/deployments.yaml
|
2017-09-20 12:48:19 -04:00
|
|
|
vars:
|
|
|
|
force: false
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2017-10-17 17:33:14 +01:00
|
|
|
with_items: "{{ '{{' }} {{role.name}}_pre_deployments|default([]) {{ '}}' }}"
|
2017-09-20 12:48:19 -04:00
|
|
|
{%- endfor %}
|
2017-11-08 10:49:50 -05:00
|
|
|
tags:
|
|
|
|
- overcloud
|
|
|
|
- pre_deploy_steps
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
|
2017-11-08 10:49:50 -05:00
|
|
|
name: Host prep steps
|
2017-10-20 13:43:38 +02:00
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
2017-09-20 12:48:19 -04:00
|
|
|
vars:
|
|
|
|
bootstrap_server_id: BOOTSTRAP_SERVER_ID
|
|
|
|
tasks:
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/host_prep_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2017-09-20 12:48:19 -04:00
|
|
|
{%- endfor %}
|
2017-11-08 10:49:50 -05:00
|
|
|
tags:
|
|
|
|
- overcloud
|
|
|
|
- host_prep_steps
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2017-10-06 11:41:59 +02:00
|
|
|
{%- for step in range(1,deploy_steps_max) %}
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: DEPLOY_SOURCE_HOST
|
2017-11-08 10:35:39 -05:00
|
|
|
name: External deployment step {{step}}
|
2017-10-20 13:43:38 +02:00
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
2017-11-07 07:31:25 -05:00
|
|
|
become: false
|
2017-10-06 11:41:59 +02:00
|
|
|
vars:
|
|
|
|
step: '{{step}}'
|
|
|
|
tasks:
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: external_deploy_steps_tasks.yaml
|
2017-11-08 10:49:50 -05:00
|
|
|
tags:
|
|
|
|
- external
|
|
|
|
- external_deploy_steps
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
|
2017-11-22 18:37:39 +00:00
|
|
|
name: Overcloud deploy step tasks for {{step}}
|
2017-10-20 13:43:38 +02:00
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
2017-11-22 18:37:39 +00:00
|
|
|
# FIXME(shardy) - it would be nice to use strategy: free to
|
|
|
|
# allow the tasks per-step to run in parallel on each role,
|
|
|
|
# but that doesn't work with any_errors_fatal: yes
|
2017-10-06 11:41:59 +02:00
|
|
|
vars:
|
|
|
|
bootstrap_server_id: BOOTSTRAP_SERVER_ID
|
|
|
|
step: '{{step}}'
|
|
|
|
tasks:
|
2017-11-22 18:37:39 +00:00
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/deploy_steps_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2017-11-22 18:37:39 +00:00
|
|
|
{%- endfor %}
|
|
|
|
tags:
|
|
|
|
- overcloud
|
|
|
|
- deploy_steps
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
|
2017-11-22 18:37:39 +00:00
|
|
|
name: Overcloud common deploy step tasks {{step}}
|
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
|
|
|
vars:
|
|
|
|
bootstrap_server_id: BOOTSTRAP_SERVER_ID
|
|
|
|
step: '{{step}}'
|
|
|
|
tasks:
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: common_deploy_steps_tasks.yaml
|
2017-11-08 10:49:50 -05:00
|
|
|
tags:
|
|
|
|
- overcloud
|
|
|
|
- deploy_steps
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2017-10-06 11:41:59 +02:00
|
|
|
{%- endfor %}
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
|
2017-09-20 12:48:19 -04:00
|
|
|
name: Server Post Deployments
|
2017-10-20 13:43:38 +02:00
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
2017-09-20 12:48:19 -04:00
|
|
|
tasks:
|
2017-07-20 17:11:44 +01:00
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: {{role.name}}/deployments.yaml
|
2017-09-20 12:48:19 -04:00
|
|
|
vars:
|
|
|
|
force: false
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2017-10-17 17:33:14 +01:00
|
|
|
with_items: "{{ '{{' }} {{role.name}}_post_deployments|default([]) {{ '}}' }}"
|
2018-01-19 17:25:28 +01:00
|
|
|
{%- endfor %}
|
2017-11-08 10:49:50 -05:00
|
|
|
tags:
|
|
|
|
- overcloud
|
|
|
|
- post_deploy_steps
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2018-05-07 15:54:11 -06:00
|
|
|
- hosts: DEPLOY_SOURCE_HOST
|
2017-11-22 17:45:19 +00:00
|
|
|
name: External deployment Post Deploy tasks
|
|
|
|
gather_facts: no
|
|
|
|
any_errors_fatal: yes
|
|
|
|
become: false
|
|
|
|
tasks:
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: external_post_deploy_steps_tasks.yaml
|
2017-11-22 17:45:19 +00:00
|
|
|
tags:
|
|
|
|
- external
|
|
|
|
- external_deploy_steps
|
2018-01-30 19:41:35 -05:00
|
|
|
|
2017-10-06 11:41:59 +02:00
|
|
|
external_deploy_steps_tasks: {get_attr: [ExternalDeployTasks, value]}
|
2017-11-22 17:45:19 +00:00
|
|
|
external_post_deploy_steps_tasks: {get_attr: [ExternalPostDeployTasks, value]}
|
2017-07-21 11:43:25 +01:00
|
|
|
update_steps_tasks: |
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/update_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2017-07-21 11:43:25 +01:00
|
|
|
{%- endfor %}
|
2018-05-07 15:54:11 -06:00
|
|
|
update_steps_playbook:
|
|
|
|
str_replace:
|
|
|
|
params:
|
|
|
|
DEPLOY_SOURCE_HOST: {get_param: deployment_source_hosts}
|
|
|
|
DEPLOY_TARGET_HOST: {get_param: deployment_target_hosts}
|
|
|
|
template: |
|
|
|
|
- hosts: DEPLOY_SOURCE_HOST
|
|
|
|
name: Gather facts from undercloud
|
|
|
|
gather_facts: yes
|
|
|
|
become: false
|
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
name: Gather facts from overcloud
|
|
|
|
gather_facts: yes
|
|
|
|
- hosts: all
|
|
|
|
name: Load global variables
|
|
|
|
gather_facts: no
|
|
|
|
tasks:
|
|
|
|
- include_vars: global_vars.yaml
|
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
name: Run update
|
|
|
|
serial: 1
|
|
|
|
gather_facts: no
|
|
|
|
tasks:
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: update_steps_tasks.yaml
|
2018-05-07 15:54:11 -06:00
|
|
|
with_sequence: start=0 end={{update_steps_max-1}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
2018-06-11 14:06:40 +02:00
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/host_prep_tasks.yaml
|
2018-06-11 14:06:40 +02:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
|
|
|
{%- endfor %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: common_deploy_steps_tasks.yaml
|
2018-05-07 15:54:11 -06:00
|
|
|
with_sequence: start=1 end={{deploy_steps_max-1}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: post_update_steps_tasks.yaml
|
2018-06-25 10:39:56 +02:00
|
|
|
with_sequence: start=0 end={{post_update_steps_max-1}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
2018-03-12 17:02:36 +01:00
|
|
|
pre_upgrade_rolling_steps_tasks: |
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/pre_upgrade_rolling_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2018-03-12 17:02:36 +01:00
|
|
|
{%- endfor %}
|
2018-05-07 15:54:11 -06:00
|
|
|
pre_upgrade_rolling_steps_playbook:
|
|
|
|
str_replace:
|
|
|
|
params:
|
|
|
|
DEPLOY_SOURCE_HOST: {get_param: deployment_source_hosts}
|
|
|
|
DEPLOY_TARGET_HOST: {get_param: deployment_target_hosts}
|
|
|
|
template: |
|
|
|
|
- hosts: DEPLOY_SOURCE_HOST
|
|
|
|
name: Gather facts from undercloud
|
|
|
|
gather_facts: yes
|
|
|
|
become: false
|
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
name: Gather facts from overcloud
|
|
|
|
gather_facts: yes
|
|
|
|
- hosts: all
|
|
|
|
name: Load global variables
|
|
|
|
gather_facts: no
|
|
|
|
tasks:
|
|
|
|
- include_vars: global_vars.yaml
|
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
name: Run pre-upgrade rolling tasks
|
|
|
|
serial: 1
|
|
|
|
gather_facts: no
|
|
|
|
tasks:
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: pre_upgrade_rolling_steps_tasks.yaml
|
2018-05-07 15:54:11 -06:00
|
|
|
with_sequence: start=0 end={{pre_upgrade_rolling_steps_max-1}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
2017-08-04 14:55:48 +03:00
|
|
|
upgrade_steps_tasks: |
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/upgrade_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2017-08-04 14:55:48 +03:00
|
|
|
{%- endfor %}
|
2018-05-07 15:54:11 -06:00
|
|
|
upgrade_steps_playbook:
|
|
|
|
str_replace:
|
|
|
|
params:
|
|
|
|
DEPLOY_SOURCE_HOST: {get_param: deployment_source_hosts}
|
|
|
|
DEPLOY_TARGET_HOST: {get_param: deployment_target_hosts}
|
|
|
|
template: |
|
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
tasks:
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: upgrade_steps_tasks.yaml
|
2018-05-07 15:54:11 -06:00
|
|
|
with_sequence: start=0 end={{upgrade_steps_max-1}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
2017-10-11 15:55:06 +03:00
|
|
|
post_upgrade_steps_tasks: |
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/post_upgrade_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2017-10-11 15:55:06 +03:00
|
|
|
{%- endfor %}
|
2018-05-07 15:54:11 -06:00
|
|
|
post_upgrade_steps_playbook:
|
|
|
|
str_replace:
|
|
|
|
params:
|
|
|
|
DEPLOY_SOURCE_HOST: {get_param: deployment_source_hosts}
|
|
|
|
DEPLOY_TARGET_HOST: {get_param: deployment_target_hosts}
|
|
|
|
template: |
|
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
tasks:
|
2018-07-03 15:50:26 +05:30
|
|
|
- include_tasks: post_upgrade_steps_tasks.yaml
|
2018-05-07 15:54:11 -06:00
|
|
|
with_sequence: start=0 end={{post_upgrade_steps_max-1}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
fast_forward_upgrade_playbook:
|
2018-05-07 15:54:11 -06:00
|
|
|
str_replace:
|
|
|
|
params:
|
|
|
|
DEPLOY_SOURCE_HOST: {get_param: deployment_source_hosts}
|
|
|
|
DEPLOY_TARGET_HOST: {get_param: deployment_target_hosts}
|
|
|
|
template: |
|
|
|
|
- hosts: DEPLOY_TARGET_HOST
|
|
|
|
tasks:
|
|
|
|
- set_fact:
|
|
|
|
releases: {get_param: [FastForwardUpgradeReleases]}
|
2018-02-24 22:40:28 +01:00
|
|
|
{% raw %}
|
2018-05-07 15:54:11 -06:00
|
|
|
- set_fact:
|
|
|
|
ffu_releases: "{{ releases | difference( releases | last )}}"
|
|
|
|
- include_tasks: fast_forward_upgrade_release_tasks.yaml
|
|
|
|
loop_control:
|
|
|
|
loop_var: release
|
|
|
|
with_items: '{{ ffu_releases }}'
|
|
|
|
- set_fact:
|
|
|
|
release: "{{ releases | last }}"
|
|
|
|
ffu_packages_apply: True
|
2018-02-24 22:40:28 +01:00
|
|
|
{% endraw %}
|
2018-05-07 15:54:11 -06:00
|
|
|
- include_tasks: fast_forward_upgrade_post_role_tasks.yaml
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
fast_forward_upgrade_release_tasks: |
|
|
|
|
- include_tasks: fast_forward_upgrade_prep_tasks.yaml
|
|
|
|
- include_tasks: fast_forward_upgrade_bootstrap_tasks.yaml
|
|
|
|
fast_forward_upgrade_prep_tasks: |
|
2018-02-06 18:58:49 +01:00
|
|
|
{%- for role in roles %}
|
|
|
|
- shell: |
|
|
|
|
#!/bin/bash
|
|
|
|
if [ ! -f /root/.ffu_workaround ]; then
|
|
|
|
touch /root/.ffu_workaround
|
|
|
|
os-apply-config -m /var/lib/os-collect-config/{{role.deprecated_server_resource_name|default(role.name)}}Deployment.json
|
|
|
|
systemctl stop os-collect-config
|
|
|
|
rm -r /var/lib/os-collect-config/*
|
|
|
|
rm -f /usr/libexec/os-refresh-config/configure.d/40-hiera-datafiles
|
|
|
|
rm -f /usr/libexec/os-apply-config/templates/etc/puppet/hiera.yaml
|
|
|
|
rm -f /usr/libexec/os-refresh-config/configure.d/10-hiera-disable
|
|
|
|
fi
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2018-02-06 18:58:49 +01:00
|
|
|
name: Run Fast Forward Upgrade Prep Workarounds for {{role.name}}
|
|
|
|
{%- endfor %}
|
|
|
|
{% raw %}
|
|
|
|
- name: get bootstrap nodeid
|
|
|
|
tags: common
|
|
|
|
command: hiera -c /etc/puppet/hiera.yaml bootstrap_nodeid
|
|
|
|
register: bootstrap_node
|
2018-02-24 22:40:28 +01:00
|
|
|
- name: set is_bootstrap_node ffu_packages_bootstrap_only facts
|
2018-02-06 18:58:49 +01:00
|
|
|
tags: common
|
2018-02-24 22:40:28 +01:00
|
|
|
set_fact:
|
|
|
|
is_bootstrap_node={{bootstrap_node.stdout|lower == ansible_hostname|lower}}
|
|
|
|
ffu_packages_apply={{bootstrap_node.stdout|lower == ansible_hostname|lower}}
|
2018-02-06 18:58:49 +01:00
|
|
|
{% endraw %}
|
|
|
|
- name: Create /var/lib/docker-puppet
|
|
|
|
file: path=/var/lib/docker-puppet state=directory setype=svirt_sandbox_file_t selevel=s0 recurse=true
|
|
|
|
- name: Write docker-puppet.py
|
|
|
|
copy: src=docker_puppet_script.yaml dest=/var/lib/docker-puppet/docker-puppet.py force=yes mode=0600
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
- include_tasks: fast_forward_upgrade_prep_role_tasks.yaml
|
|
|
|
with_sequence: start=0 end={{fast_forward_upgrade_prep_steps_max}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
2018-02-24 22:40:28 +01:00
|
|
|
fast_forward_upgrade_post_role_tasks: |
|
|
|
|
{%- for role in roles %}
|
|
|
|
- include_tasks: {{role.name}}/fast_forward_post_upgrade_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2018-02-24 22:40:28 +01:00
|
|
|
{%- endfor %}
|
|
|
|
- name: Openstack Heat Agents package update
|
|
|
|
yum: name=openstack-heat-agents state=latest
|
|
|
|
- name: Update os-collect-config
|
|
|
|
yum: name=os-collect-config state=latest
|
|
|
|
- name: Start os-collect-config back up
|
|
|
|
service: name=os-collect-config state=started enabled=yes
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
fast_forward_upgrade_prep_role_tasks: |
|
|
|
|
{%- for role in roles %}
|
|
|
|
- include_tasks: {{role.name}}/fast_forward_upgrade_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
{%- endfor %}
|
|
|
|
fast_forward_upgrade_bootstrap_tasks: |
|
|
|
|
- include_tasks: fast_forward_upgrade_bootstrap_role_tasks.yaml
|
|
|
|
with_sequence: start={{fast_forward_upgrade_prep_steps_max+1}} end={{fast_forward_upgrade_steps_max}}
|
|
|
|
loop_control:
|
|
|
|
loop_var: step
|
|
|
|
fast_forward_upgrade_bootstrap_role_tasks: |
|
|
|
|
{%- for role in roles %}
|
|
|
|
- include_tasks: {{role.name}}/fast_forward_upgrade_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}' and ansible_hostname == {{role.name}}[0]
|
ffu: Add fast-forward upgrade outputs to RoleConfig
As outlined in the spec, fast-forward upgrades aim to take an
environment from an initial release of N to a release of N>=2, beyond
that of the traditionally supported N+1 upgrade path provided today by
many OpenStack projects.
For TripleO the first phase of this upgrade will be to move the
environment to the release prior to the target release. This will be
achieved by disabling all OpenStack control plane services and then
preforming the minimum number of steps required to upgrade each service
through each release until finally reaching the target release.
This change introduces the framework for this phase of the fast-forward
upgrades by adding playbooks and task files as outputs to RoleConfig.
- fast_forward_upgrade_playbook.yaml
This is the top level play and acts as the outer loop of the process,
iterating through the required releases as set by the
FastForwardUpgradeReleases parameter for the fast-forward section of the
upgrade. This currently defaults to Ocata and Pike for Queens.
Note that this play is run against the overcloud host group and it is
currently assumed that the inventory used to run this play is provided
by the tripleo-ansible-inventory command.
- fast_forward_upgrade_release_tasks.yaml
This output simply imports the top level prep and bootstrap task files.
- fast_forward_upgrade_prep_tasks.yaml
- fast_forward_upgrade_bootstrap_tasks.yaml
These outputs act as the inner loop for the fast-forward upgrade phase,
iterating over step values while importing their associated role tasks.
As prep tasks are carried out first for each release we loop over step
values starting at 0 and ending at the defined
fast_forward_upgrade_prep_steps_max, currently 3.
Following this we then complete the bootstrap tasks for each release,
looping over steps values starting at
fast_forward_upgrade_prep_steps_max + 1 , currently 4 and ending at
fast_forward_upgrade_steps_max,currently 9.
- fast_forward_upgrade_prep_role_tasks.yaml
- fast_forward_upgrade_bootstrap_role_tasks.yaml
These outputs then finally import the fast_forward_upgrade_tasks files
generated by the FastForwardUpgradeTasks YAQL query for each role. For
prep tasks these are always included when on an Ansible host of a given
role. This differs from bootstrap tasks that are only included for the
first host associated with a given role.
This will result in the following order of task imports with their
associated value of release and step:
fast_forward_upgrade_playbook
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=ocata
\_fast_forward_upgrade_prep_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=0
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=1
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=2
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=3
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=ocata
\_fast_forward_upgrade_bootstrap_role_tasks - release=ocata
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=4
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=5
\_$roleA/fast_forward_upgrade_tasks - release=ocata, step=N
\_$roleB/fast_forward_upgrade_tasks - release=ocata, step=N
\_fast_forward_upgrade_release_tasks
\_fast_forward_upgrade_prep_tasks - release=pike
\_fast_forward_upgrade_prep_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=0
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=1
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=2
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=3
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=3
\_fast_forward_upgrade_bootstrap_tasks - release=pike
\_fast_forward_upgrade_bootstrap_role_tasks - release=pike
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=4
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=5
\_$roleA/fast_forward_upgrade_tasks - release=pike, step=N
\_$roleB/fast_forward_upgrade_tasks - release=pike, step=N
bp fast-forward-upgrades
Change-Id: Ie2683fd7b81167abe724a7b9245bf85a0a87ad1d
2017-08-25 14:25:08 +01:00
|
|
|
{%- endfor %}
|
2018-01-23 22:43:49 +05:30
|
|
|
post_update_steps_tasks: |
|
|
|
|
{%- for role in roles %}
|
2018-07-03 15:50:26 +05:30
|
|
|
- import_tasks: {{role.name}}/post_update_tasks.yaml
|
2018-05-14 11:15:09 -07:00
|
|
|
when: tripleo_role_name == '{{role.name}}'
|
2018-01-23 22:43:49 +05:30
|
|
|
{%- endfor %}
|
2018-04-11 18:38:37 +05:30
|
|
|
boot_param_tasks: {get_file: ../extraconfig/pre_network/boot_param_tasks.yaml}
|