Add update yaml backward compatibe with PublicVirtualIP on ctlplane

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
This commit is contained in:
Giulio Fidente 2015-12-14 23:38:57 +01:00
parent 3e8010dc85
commit 3770deda06
2 changed files with 5 additions and 0 deletions

View File

@ -7,3 +7,6 @@ Contents
**update-from-keystone-admin-internal-api.yaml**
To be used if the Keystone Admin API was originally deployed on the
Internal API network.
**update-from-publicvip-on-ctlplane.yaml**
To be used if the PublicVirtualIP resource was deployed as an additional VIP on the 'ctlplane'.

View File

@ -0,0 +1,2 @@
resource_registry:
OS::TripleO::Network::Ports::ExternalVipPort: ../../network/ports/ctlplane_vip.yaml