aboutsummaryrefslogtreecommitdiffstats
path: root/environments/external-loadbalancer-vip.yaml
diff options
context:
space:
mode:
authorDan Prince <dprince@redhat.com>2015-09-10 09:30:01 -0400
committerGiulio Fidente <gfidente@redhat.com>2015-11-24 11:02:34 +0100
commitbb0d66b8008dfc9c6b9febb9a98e28a94d8262b7 (patch)
tree283f7afccd9c7afb2e9fdec104b2ebd4f3459f61 /environments/external-loadbalancer-vip.yaml
parent705a6401a6db2fe9f78ee5f6584026179e64c7ae (diff)
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 <gfidente@redhat.com> Change-Id: Ifad32e18f12b9997e3f89e4afe3ebc4c30e14a86
Diffstat (limited to 'environments/external-loadbalancer-vip.yaml')
-rw-r--r--environments/external-loadbalancer-vip.yaml13
1 files changed, 13 insertions, 0 deletions
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: