diff options
| author |   marios <marios@redhat.com> | 2016-04-14 12:26:45 +0300 |
|---|---|---|
| committer | marios <marios@redhat.com> | 2016-04-14 18:35:37 +0300 |
| commit | 11079d69df8f7b212fee419c7489095feba9cfa2 (patch) | |
| tree | cf2faf6df164ac242e2e587ac48f57db6ed767c2 /extraconfig/post_deploy/example_run_on_update.yaml | |
| parent | abbc6b1a7ac0ce9e381fdf92297f0045806a16a0 (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
Diffstat (limited to 'extraconfig/post_deploy/example_run_on_update.yaml')
0 files changed, 0 insertions, 0 deletions