Run upgrade steps before post-deploy config
authorSteven Hardy <shardy@redhat.com>
Fri, 2 Dec 2016 13:58:24 +0000 (13:58 +0000)
committerSteven Hardy <shardy@redhat.com>
Mon, 19 Dec 2016 11:04:47 +0000 (11:04 +0000)
commit58c6988751c6d6b55cfc22aa87bc4f45b6509c2b
treedbb5051fad4067b53d4b63fc76225f8cd0e69e75
parentb8a4e40cf2281036d4fb1f8db48ce16625b2edac
Run upgrade steps before post-deploy config

For some upgrade scenarios, e.g all-in-one deployments, it may
be possible to run the upgrade steps, then apply puppet in one
stack update, so reverse the order here.  For normal deployments
the upgrade steps are mapped to OS::Heat::None so this will have
no effect.

Partially-Implements: blueprint overcloud-upgrades-per-service
Change-Id: I3c78751349a6ac2bc5dff82f67bffe13750ac21c
environments/major-upgrade-all-in-one.yaml [new file with mode: 0644]
overcloud.j2.yaml