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

diff --git a/environments/updates/README.md b/environments/updates/README.md
index 8c03411..426d732 100644 (file)
--- a/environments/updates/README.md
+++ b/environments/updates/README.md
@@ -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'.

diff --git a/environments/updates/update-from-publicvip-on-ctlplane.yaml b/environments/updates/update-from-publicvip-on-ctlplane.yaml
new file mode 100644 (file)
index 0000000..c62428b
--- /dev/null
+++ b/environments/updates/update-from-publicvip-on-ctlplane.yaml
@@ -0,0 +1,2 @@
+resource_registry:
+  OS::TripleO::Network::Ports::ExternalVipPort: ../../network/ports/ctlplane_vip.yaml
\ No newline at end of file