aa365ee117
We need to make sure that the hiera data are fresh before the update
step so that anyone using those data during those steps are seeing the
latest information from heat.
Factor out the hiera generation and include it in deployment and
update playbooks.
The double tasks definition in the deployment playbook seemed to be
redundant so It has been removed.
Change-Id: I6b6c676880ccc8cbed23af135e5865c222a8f1d0
Closes-Bug: #1861799
With some adjustment:
(cherry picked from commit 536230b323)
31 lines
679 B
YAML
31 lines
679 B
YAML
- name: Hiera configuration
|
|
when: not ansible_check_mode|bool
|
|
block:
|
|
- name: Hiera config
|
|
include_role:
|
|
name: tripleo-hieradata
|
|
- name: Hiera symlink
|
|
file:
|
|
src: /etc/puppet/hiera.yaml
|
|
dest: /etc/hiera.yaml
|
|
state: link
|
|
force: true
|
|
|
|
- name: Hieradata from vars
|
|
when: not ansible_check_mode|bool
|
|
include_role:
|
|
name: tripleo-hieradata
|
|
tasks_from: hieradata_vars.yaml
|
|
vars:
|
|
hieradata_templates_list:
|
|
- bootstrap_node
|
|
- all_nodes
|
|
- vip_data
|
|
- net_ip_map
|
|
- cloud_domain
|
|
- fqdn
|
|
- service_names
|
|
- service_configs
|
|
- extraconfig
|
|
- role_extraconfig
|