Move per-role *SchedulerHints parameters into role templates
authorSteven Hardy <shardy@redhat.com>
Tue, 26 Jul 2016 07:03:28 +0000 (08:03 +0100)
committerSteven Hardy <shardy@redhat.com>
Wed, 27 Jul 2016 16:04:59 +0000 (17:04 +0100)
commit466274e28712d913528742be3293266743062a45
tree46d99b6891783f3ded53a7978333075f2032c88f
parent918b668bf4fe4a32cce9440bc123b663acc7c5a9
Move per-role *SchedulerHints parameters into role templates

To enable custom roles, move these into the role templates where
they can be passed via parameter defaults.  Because the Compute
role uses an inconsistent NovaCompute naming, these parameters
cannot be generated in overcloud.yaml, so moving them enables
backwards compatibility to be maintained when we move to a
fully jinja generated overcloud (e.g including the role
ResourceGroup resources)

Change-Id: I3f9b2275f2b1daeb8b83f09548a089dadcfe9eee
Partially-Implements: blueprint custom-roles
overcloud.yaml
puppet/ceph-storage.yaml
puppet/cinder-storage.yaml
puppet/compute.yaml
puppet/controller.yaml
puppet/swift-storage.yaml