summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormarios <marios@redhat.com>2016-04-14 12:26:45 +0300
committermarios <marios@redhat.com>2016-04-14 18:35:37 +0300
commit11079d69df8f7b212fee419c7489095feba9cfa2 (patch)
treecf2faf6df164ac242e2e587ac48f57db6ed767c2
parentabbc6b1a7ac0ce9e381fdf92297f0045806a16a0 (diff)
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
-rw-r--r--environments/updates/update-from-overcloud-compute-hostnames.yaml2
1 files changed, 2 insertions, 0 deletions
diff --git a/environments/updates/update-from-overcloud-compute-hostnames.yaml b/environments/updates/update-from-overcloud-compute-hostnames.yaml
new file mode 100644
index 00000000..f628f0de
--- /dev/null
+++ b/environments/updates/update-from-overcloud-compute-hostnames.yaml
@@ -0,0 +1,2 @@
+parameter_defaults:
+ ComputeHostnameFormat: '%stackname%-compute-%index%'