From bb0d66b8008dfc9c6b9febb9a98e28a94d8262b7 Mon Sep 17 00:00:00 2001 From: Dan Prince Date: Thu, 10 Sep 2015 09:30:01 -0400 Subject: Add net_vip_map_external to be used for an external balancer Changes VipMap into a new NetVipMap resource which defaults to being the same as the 'old' VipMap. An environment file can be used to map NetVipMap instead to the net_vip_map_external.yaml which allows for passing in explicit Virtual IP addresses. It also ensures that references to the Virtual IPs are gathered from the VipMap resource and allows for an empty ControlPlaneIP parameter in the neutron port templates where it can be. Co-Authored-By: Giulio Fidente Change-Id: Ifad32e18f12b9997e3f89e4afe3ebc4c30e14a86 --- environments/external-loadbalancer-vip.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 environments/external-loadbalancer-vip.yaml (limited to 'environments') diff --git a/environments/external-loadbalancer-vip.yaml b/environments/external-loadbalancer-vip.yaml new file mode 100644 index 00000000..0866806c --- /dev/null +++ b/environments/external-loadbalancer-vip.yaml @@ -0,0 +1,13 @@ +resource_registry: + OS::TripleO::Network::Ports::NetVipMap: ../network/ports/net_vip_map_external.yaml + +parameter_defaults: + # When using an external loadbalancer set the following in parameter_defaults + # to control your VIPs (currently one per network) + # NOTE: we will eventually move to one VIP per service + # + # ControlNetworkVip: + # ExternalNetworkVip: + # InternalApiNetworkVip: + # StorageNetworkVip: + # StorageMgmtNetworkVip: -- cgit 1.2.3-korg