path: root/overcloud.j2.yaml
diff options
authorJames Slagle <jslagle@redhat.com>2017-04-26 11:04:42 -0400
committerJames Slagle <jslagle@redhat.com>2017-06-15 14:56:20 -0400
commita59142162c8acf189e5682b9ad1a6fef7a2dbc29 (patch)
tree424d2e809fee25a9cc09ec8a660d599d64198203 /overcloud.j2.yaml
parent562ee3a9a74a06d080847193b017cbe9e59d7077 (diff)
Add VipMap output
Add VipMap output to the top level stack output. VipMap is a mapping from each network to the VIP address on that network. Also includes the Redis VIP. This output facilitates deploying split-stack so you can feed the VIP addresses from VipMap as inputs into the services stack. implements blueprint split-stack-default Change-Id: I245920994613c9bd10801c25fa545267aa49b239
Diffstat (limited to 'overcloud.j2.yaml')
1 files changed, 6 insertions, 0 deletions
diff --git a/overcloud.j2.yaml b/overcloud.j2.yaml
index 3244b25..c8b3458 100644
--- a/overcloud.j2.yaml
+++ b/overcloud.j2.yaml
@@ -806,3 +806,9 @@ outputs:
{% for role in roles %}
{{role.name}}: {get_attr: [{{role.name}}, attributes, os_collect_config]}
{% endfor %}
+ VipMap:
+ description: Mapping of each network to VIP addresses. Also includes the Redis VIP.
+ value:
+ map_merge:
+ - {get_attr: [VipMap, net_ip_map]}
+ - redis: {get_attr: [RedisVirtualIP, ip_address]}