summaryrefslogtreecommitdiffstats
path: root/puppet/controller-puppet.yaml
diff options
context:
space:
mode:
authorGiulio Fidente <gfidente@redhat.com>2015-06-12 16:17:19 +0200
committerDan Sneddon <dsneddon@redhat.com>2015-06-13 17:36:29 -0700
commitd4518312486d9e5ad1399f59c04d972abfed4d82 (patch)
tree776641da00c5fbdcd76132f15a19e098195b8420 /puppet/controller-puppet.yaml
parenta6706da768ece0d3eb850fc7739fa677f48513bf (diff)
Remove Redis VirtualIP from params and build it from Neutron::Port
The redis_vip should come from a Neutron Port as its cidr depends on the Neutron Network configuration. This change adds 2 new files and modifies 1 in the network/ports directory: - noop.yaml - Passes through the ctlplane Controller IP (modified) - ctlplane_vip.yaml - Creates a new VIP on the control plane - vip.yaml - Creates a VIP on the named network (for isolated nets) Also, changes to overcloud-without-mergepy.yaml create the Redis Virtual IP. The standard resource registry was modified to use noop.yaml for the new Redis VIP. The Puppet resource registry was modified to use ctlplane_vip.yaml by default, but can be made to use vip.yaml when network isolation is used by using an environment file. vip.yaml will place the VIP according to the ServiceNetMap, which can also be overridden. We use this new VIP port definition to assign a VIP to Redis, but follow-up patches will assign VIPs to the rest of the services in a similar fashion. Co-Authored-By: Dan Sneddon <dsneddon@redhat.com> Change-Id: I2cb44ea7a057c4064d0e1999702623618ee3390c
Diffstat (limited to 'puppet/controller-puppet.yaml')
0 files changed, 0 insertions, 0 deletions