summaryrefslogtreecommitdiffstats
path: root/environments/major-upgrade-pacemaker-init.yaml
AgeCommit message (Collapse)AuthorFilesLines
2016-09-22No-op Puppet for upgrades/migrations according to composable rolesJiri Stransky1-5/+1
Our previous no-ops stopped working because the Puppet run resources moved under a different entry in resource registry. This is now fixed to follow the latest way. Change-Id: Ia5598385ddca185bfbf10e2d3babb53f6f77d1ac Closes-Bug: #1626452
2016-07-01Stop no-opping PackageUpdate on upgradeJiri Stransky1-1/+0
After we fixed bug #1567384 and bug #1567385, we no longer need to no-op the PakageUpdate resource on upgrades. I removed the no-op in change Ie14ddbff15e7ed21aaa3fcdacf36e0040f912382 from major-upgrade-pacemaker-converge.yaml but didn't recall we had the no-op in major-upgrade-pacemaker{,-init}.yaml too. Change-Id: I24b913c790eae79e3b207729e0b22378075fb282
2016-05-31Adjust UpgradeLevelNovaCompute rpc messaging pin to mitakamarios1-1/+1
For upgrades to current master newton, we should pin nova compute rpc to the previous/current version, mitaka. Implements: blueprint overcloud-upgrades-workflow-mitaka-to-newton Change-Id: I89c3a8c50e83e682f83aa0d9eb222313676277e6
2016-03-09Upgrades: initialization command/snippetJiri Stransky1-0/+11
This allows to run a command or a script snippet on all overcloud nodes at the beginning of the upgrade. The intended use is to switch to a new set of repositories on the overcloud. This is done differently in different contexts (e.g. upstream vs. downstream), but generally it should be simple enough to not warrant creation of switchable "UpgradeInit" resource in the resource registry, and a string command/snippet parameter should suffice. Change-Id: I72271170d3f53a5179b3212ec9bae9a6204e29e6