![Dan Prince](/assets/img/avatar_default.png)
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
14 lines
443 B
YAML
14 lines
443 B
YAML
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:
|