openstack
/
tripleo-heat-templates
Code Issues Proposed changes
tripleo-heat-templates/environments/updates
History
marios 11079d69df Retain existing ComputeHostnameFormat when upgrading older envs 
As discussed at +bug/1569705 after an upgrade to liberty from an
older deployment, the hostname of the compute nodes is changed.

If we set the ComputeHostnameFormat in the upgrade-pacemaker-init
environment file parameter_defaults then we don't need to worry
about the new value being specified as default by the upgraded
overcloud.yaml since the parameter_defaults value is persisted
unless explicitly overridden with a new parameter_defaults value.

This is provided as a new environment file that needs to be
included in the first upgrade step when upgradinng from an
environment that has 'overcloud-compute-N' hostnames.

Change-Id: I2c12bd1abac65d7f13d8768f87c5ebda91164578
Related-Bug: 1569705
 		2016-04-14 18:35:37 +03:00
..
README.md Add update yaml backward compatibe with PublicVirtualIP on ctlplane 2015-12-15 12:59:22 +01:00
update-from-keystone-admin-internal-api.yaml Always use parameter_defaults in environment files 2016-04-11 14:15:39 -04:00
update-from-overcloud-compute-hostnames.yaml Retain existing ComputeHostnameFormat when upgrading older envs 2016-04-14 18:35:37 +03:00
update-from-publicvip-on-ctlplane.yaml Add update yaml backward compatibe with PublicVirtualIP on ctlplane 2015-12-15 12:59:22 +01:00

README.md

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'.