Age | Commit message (Collapse) | Author | Files | Lines |
|
As we are staring to manually check overcloud services
the first step is to check that the puppet profiles
are all aligned.
Changes applied:
No logic added or removed in this submission.
Removed unused parameters.
Align header comments structure.
All profiles parameters sorted following:
"Mandatory params first sorted alphabetically
then optional params sorted alphabetically."
Note: Following submissions will check pacemaker,
cinder, mistral and redis services in the base profiles
as some of them has the $pacemaker_master parameter
defaulted to true.
Change-Id: I2f91c3f6baa33f74b5625789eec83233179a9655
|
|
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
|
|
When nova-compute and nova-conductor are collocated, we need to make
sure nova-conductor starts before nova-compute otherwise nova-compute
will just fail to start.
Change-Id: Icc3ed768af2a08e2db78d9c9278d309a62d26850
|
|
In the case where all services are installed on the same node
(All-In-One), we don't want Pacemaker to manage nova-compute. This patch
makes the Nova service more specific for overriding start/stop/restart
actions, to be applied only for services that usually run on
controllers.
Change-Id: I81a86331cff4e7988e035ada82834a45a6bb99c1
|
|
Create nova-conductor profile, part of composable services.
Implements: blueprint refactor-puppet-manifests
Change-Id: Iaaf3a3c2528d9747e41f360a1fe55f95ed37b2d1
|