aboutsummaryrefslogtreecommitdiffstats
path: root/manifests/profile/pacemaker/nova
AgeCommit message (Collapse)AuthorFilesLines
2016-10-03Fix the timeout for pacemaker systemd resourcesMichele Baldessari5-0/+5
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 Camacho5-27/+25
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-07-27Move nova constraints from controller manifest to each serviceMichele Baldessari3-0/+87
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
2016-07-20Merge "Make ::tripleo::profile::base classes work with multiple nodes"Jenkins1-3/+1
2016-07-18Make ::tripleo::profile::base classes work with multiple nodesMichele Baldessari1-3/+1
In the Next Generation HA architecture a number of active/active services will be run via systemd. In order for this to work we need to make sure that the sync_db operation only takes place on the bootstrap node, just like it is done today for the pacemaker profiles. We do this by removing sync_db as a parameter and instead set it to true or false depending if the hostname matches the bootstrap_node as it is done today in the pacemaker role. Note that we call hiera('bootstrap_nodeid', undef) because if a profile is included on a non controller node that variable will be undefined. The following testing was done: - HA puppet-pacemaker.yaml scenario with three computes - NonHA with one controller - NonHA with three controllers Fixes-Bug: 1600149 Co-Author: cmsj@tenshu.net Change-Id: I04a7b9e3c18627ea512000a34357acb7f27d6e0e Implements: blueprint ha-lightweight-architecture
2016-07-06make sure we start nova-compute after nova-conductorEmilien Macchi1-0/+5
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
2016-07-04nova: do not manage nova-compute with pacemakerEmilien Macchi5-0/+35
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
2016-06-14Implement Nova vncproxy profileEmilien Macchi1-0/+45
Change-Id: I5bc2a77b5832706bd9167cf40e5a7e0f95d7b346 Implements: blueprint refactor-puppet-manifests
2016-06-14Implement Nova Consoleauth profileEmilien Macchi1-0/+45
Change-Id: I955b4fc07dc07d8adc32411848e3e131d77a5123 Implements: blueprint refactor-puppet-manifests
2016-06-14Implement Nova Scheduler profileEmilien Macchi1-0/+45
Change-Id: I5e1c90e3c6dc556f872ced73744c5c74caaa3635 Implements: blueprint refactor-puppet-manifests
2016-06-14Implement Nova API profileEmilien Macchi1-0/+48
Change-Id: I1dde63a5a7d1624494a7157a9679f88f4cb780e0 Implements: blueprint refactor-puppet-manifests
2016-06-04Implement Nova conductor profileEmilien Macchi1-0/+45
Create nova-conductor profile, part of composable services. Implements: blueprint refactor-puppet-manifests Change-Id: Iaaf3a3c2528d9747e41f360a1fe55f95ed37b2d1