Add net_vip_map_external to be used for an external balancer
authorDan Prince <dprince@redhat.com>
Thu, 10 Sep 2015 13:30:01 +0000 (09:30 -0400)
committerGiulio Fidente <gfidente@redhat.com>
Tue, 24 Nov 2015 10:02:34 +0000 (11:02 +0100)
commitbb0d66b8008dfc9c6b9febb9a98e28a94d8262b7
tree283f7afccd9c7afb2e9fdec104b2ebd4f3459f61
parent705a6401a6db2fe9f78ee5f6584026179e64c7ae
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
12 files changed:
environments/external-loadbalancer-vip.yaml [new file with mode: 0644]
network/ports/ctlplane_vip.yaml
network/ports/external.yaml
network/ports/internal_api.yaml
network/ports/net_vip_map_external.yaml [new file with mode: 0644]
network/ports/storage.yaml
network/ports/storage_mgmt.yaml
network/ports/tenant.yaml
network/ports/vip.yaml
overcloud-resource-registry-puppet.yaml
overcloud-resource-registry.yaml
overcloud-without-mergepy.yaml