From d4518312486d9e5ad1399f59c04d972abfed4d82 Mon Sep 17 00:00:00 2001 From: Giulio Fidente Date: Fri, 12 Jun 2015 16:17:19 +0200 Subject: 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 Change-Id: I2cb44ea7a057c4064d0e1999702623618ee3390c --- overcloud-resource-registry.yaml | 3 +++ 1 file changed, 3 insertions(+) (limited to 'overcloud-resource-registry.yaml') diff --git a/overcloud-resource-registry.yaml b/overcloud-resource-registry.yaml index 7be199da..78607b51 100644 --- a/overcloud-resource-registry.yaml +++ b/overcloud-resource-registry.yaml @@ -61,3 +61,6 @@ resource_registry: OS::TripleO::BlockStorage::Ports::InternalApiPort: network/ports/noop.yaml OS::TripleO::BlockStorage::Ports::StoragePort: network/ports/noop.yaml OS::TripleO::BlockStorage::Ports::StorageMgmtPort: network/ports/noop.yaml + + # Port assignments for service virtual IPs for the controller role + OS::TripleO::Controller::Ports::RedisVipPort: network/ports/noop.yaml -- cgit 1.2.3-korg