aboutsummaryrefslogtreecommitdiffstats
path: root/manifests/profile/pacemaker/heat/api_cloudwatch.pp
AgeCommit message (Collapse)AuthorFilesLines
2016-10-03Fix the timeout for pacemaker systemd resourcesMichele Baldessari1-0/+1
Back in the Mitaka cycle via the change If6b43982c958f63bc78ad997400bf1279c23df7e we made sure that the default start and stop timeouts for pacemaker systemd resources is 200s (>= twice the default 90s DefaultTimeoutStopSec in systemd). We did this change by setting puppet resource defaults for the Pacemaker::Resource::Service class: Pacemaker::Resource::Service { op_params => 'start timeout=200s stop timeout=200s', } The problem is that after the composable services rework, this does not work anymore and the pacemaker systemd resources that still exist do not have these timeouts set. We want to move away from resource defaults for this because its results are dependent on the inclusion order which in tripleo is not guaranteed any longer (https://docs.puppet.com/puppet/latest/reference/lang_scope.html#scope-lookup-rules) The only services affected in Newton are: cinder-volume, cinder-backup, manila-share, haproxy. I preferred fixing all the pacemaker resources because it seems the cleanest and most logical commit. Change-Id: If89a95706514e536a7a2949871a0002c79b6046e Closes-Bug: #1629366
2016-08-08Fix parameters and headers inconsistency in the puppet manifests.Carlos Camacho1-3/+2
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
2016-06-22Split Heat pacemaker roles into separate servicesBrad P. Crochet1-0/+51
In order for each service to operate independently when used with Pacemaker, the roles needed to be separated. This also drops all pacemaker constraints, as they do not make much sense in the composable realm. Change-Id: I3fa76562c13191884a53848ad5adcbc9f5a24f61