Add Sahara services to ControllerServices list
authorSteven Hardy <shardy@redhat.com>
Thu, 30 Jun 2016 16:50:28 +0000 (17:50 +0100)
committerCarlos Camacho <ccamacho@redhat.com>
Sat, 6 Aug 2016 08:45:31 +0000 (10:45 +0200)
commit0327fc2bbb1be9972d99e2e83d54d07410ad01d9
tree1752ba09ea4e4b699206abac7bbe32e289c9ebb8
parent77cca14bd760f091a1e481bd44e96f8882fb99cc
Add Sahara services to ControllerServices list

https://review.openstack.org/#/c/318840/ decomposed the Sahara services
but they weren't added to the ControllerServices list, thus are now disabled.

Since we shipped mitaka with sahara enabled by default, we should probably add
them so the behavior is consistent when folks upgrade.

This also fixes a couple of issues we missed when landing the initial service
templates (partly because CI didn't test them).

In order for each service to operate independently when used with Pacemaker,
the roles needed to be separated. This commit also does this.

Depends-On: Id61eb15b1e2366f5b73c6e7d47941651e40651b1
Change-Id: I0846b328e9d938275e373d58f0b99219b19b326c
Closes-Bug: #1592284
Co-Authored-By: Brad P. Crochet <brad@redhat.com>
environments/puppet-pacemaker.yaml
overcloud.yaml
puppet/controller.yaml
puppet/services/pacemaker/sahara-api.yaml
puppet/services/pacemaker/sahara-engine.yaml
puppet/services/sahara-api.yaml
puppet/services/sahara-base.yaml
puppet/services/sahara-engine.yaml