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
This directory contains Heat environment file snippets which can be used to ensure smooth updates of the Overcloud.
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'.