Enable per-role SchedulerHints
authorSteven Hardy <shardy@redhat.com>
Tue, 8 Dec 2015 10:28:08 +0000 (10:28 +0000)
committerSteven Hardy <shardy@redhat.com>
Tue, 8 Dec 2015 10:28:08 +0000 (10:28 +0000)
commit5d61012f86a2e036908a2f7441672e43cbd34790
tree9ab7396dffc3dfe48d4c4367c705ee01a32ced14
parent10b6bb97133eb36ef0185fd903b3f112cd70a5db
Enable per-role SchedulerHints

This adds a parameter for each role, where optional scheduler hints
may be passed to nova.  One potential use-case for this is using
the ComputeCapabilities to pin deployment to a specific node (not
just a specific role/profile mapping to a pool of nodes like we
have currently documented in the ahc-match docs).

This could work as follows:

1. Tag a specific node as "node:controller-0" in Ironic:

ironic node-update <id> replace properties/capabilities='node:controller-0,boot_option:local'

2. Create a heat environment file which uses %index%

parameters:
  ControllerSchedulerHints:
    'capabilities:node': 'controller-%index%'

Change-Id: I79251dde719b4bb5c3b0cce90d0c9d1581ae66f2
overcloud.yaml
puppet/ceph-storage.yaml
puppet/cinder-storage.yaml
puppet/compute.yaml
puppet/controller.yaml
puppet/swift-storage.yaml