3770deda06
In previous releases, when not using network isolation, we used to create two different VIPs for the ControlVirtualIP and the PublicVirtualIP both on the ctlplane network. Later we moved into a configuration with a single VIP instead so we need a compatibility yaml for those updating from old versions which preserves both the IPs; one of the two is deleted otherwise. Also updates README.md with a short description of the use case. Change-Id: Iae08b938a255bf563d3df2fdc0748944a9868f8e
2 lines
104 B
YAML
2 lines
104 B
YAML
resource_registry:
|
|
OS::TripleO::Network::Ports::ExternalVipPort: ../../network/ports/ctlplane_vip.yaml |