Move nova constraints from controller manifest to each service
authorMichele Baldessari <michele@acksyn.org>
Tue, 26 Jul 2016 12:21:49 +0000 (14:21 +0200)
committerMichele Baldessari <michele@acksyn.org>
Wed, 27 Jul 2016 20:49:40 +0000 (22:49 +0200)
commita93d22f45a24a16b253f6842a087d850763926eb
tree18eec3eda07679ff84cef592d15bc8e7004de2a2
parent7a4ac41ec499867a38a9078eea356b9912fbf3c0
Move nova constraints from controller manifest to each service

Currently we are still creating all the pacemaker constraints for nova
in the main overcloud_controller_pacemaker.pp manifest file.

Let's move those to each role where they belong. Note that given
that a constraint depends on two separate pacemaker resources it is
a bit arbitrary in which file they end up being (the one of the first
resource or the second one).

Change-Id: I96a3a313d15fac820b020feae0568437c2cbade3
manifests/profile/pacemaker/nova/api.pp
manifests/profile/pacemaker/nova/conductor.pp
manifests/profile/pacemaker/nova/consoleauth.pp