Simplify/fix config enabled conditions for upgrades
authorSteven Hardy <shardy@redhat.com>
Mon, 30 Jan 2017 10:17:53 +0000 (10:17 +0000)
committerSteven Hardy <shardy@redhat.com>
Fri, 3 Feb 2017 11:43:47 +0000 (11:43 +0000)
commitefa4c0ffd2000c0b2f14679caaf781e28150f248
tree0ed4475eb13139f87c55c266b980d5fcadd9fa2c
parent87af02d67336ff26c47f67c40df23dad9e66b7fd
Simplify/fix config enabled conditions for upgrades

We should enable each kind of upgrade per role, not per step
so rework the conditions, and also only apply it to the deployment
(to save the round-trip to the nodes applying an empty config)
but don't disable the *Config resources as the overhead of these
is small, and we reference the Step1 config in the outputs, even
if it's empty.

Change-Id: Iee2f1fb5b1d8b0b6001c6ab0f2a4ef2858cef281
Partially-Implements: blueprint overcloud-upgrades-per-service
puppet/major_upgrade_steps.j2.yaml