aboutsummaryrefslogtreecommitdiffstats
path: root/manifests/profile/pacemaker/neutron
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 Camacho10-39/+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-18Make ::tripleo::profile::base classes work with multiple nodesMichele Baldessari4-40/+12
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-02Set bootstrap_nodeid to undef by defaultEmilien Macchi10-20/+20
bootstrap_nodeid is a parameter looked-up with Hiera but only set on controllers. With the transition to composable roles, we don't need to set this parameter on compute nodes, so let's just default this value by undef so we can deploy Neutron classes on compute nodes. Change-Id: I94034f696c163969a7489d9cb0a20423210d3b84
2016-06-30Merge "Nova API and Neutron server should run database creation in step 3"Jenkins1-2/+1
2016-06-30Nova API and Neutron server should run database creation in step 3Giulio Fidente1-2/+1
We perform the Galera setup in step 2 so there is no guarantee that the database will be available in that same step [1]. We used to implement a dependency in puppet using the 'galera-ready' resource (clustercheck) but this is not possible with roles because we also don't have any guarantee about clustercheck being installed on the same node. Because of the above all services must create/sync their databases in a later step. This patch fixes Nova API and Neutron Server, the other services use step 3 already. 1. https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst Change-Id: I22750ffb64afbe40b5560a6a0d0dabc5b8927d32
2016-06-29Remove base/neutron/ml2.ppEmilien Macchi1-38/+0
Not used anymore. Change-Id: Id3f943132fce235a5a4888da30332b8fc2434a78 Depends-On: I6436c5c36ac0081a720cb8a737a573b1246127a1
2016-06-22Move neutron ml2 plugins in plugins dirEmilien Macchi2-1/+39
Move neutron ml2 plugins in plugins directory and make it compatible with current THT. The old class will be removed soon. Change-Id: I35332df5800083f3373f5c37411534d11e9b4401
2016-06-21Add Neutron opencontrail plugin profilesDan Prince1-0/+33
Change-Id: Ie5ac07e6dd447216f17481ea4acf3bc204926bc8
2016-06-21Merge "Add pacemaker nuage profile."Jenkins1-0/+33
2016-06-15Merge "add plumgrid neutron profile"Jenkins1-0/+33
2016-06-10Pacemaker: only create DB on pacemaker masterDan Prince1-2/+2
This fixes a bug introduced in 72fb6727951af2cf5b16e686b3a36f5f3a7c71c7 where non-master nodes would try to create the database (and potentially fail due to a race). Change-Id: Ic0c7b05618b69caca0d4019b5153163f2405bbe5
2016-06-09add plumgrid neutron profileQasim Sarfraz1-0/+33
Change-Id: I8536782d433f97a9b619e54a1eb1ea0edb8fdaf0 Implements: blueprint refactor-puppet-manifests
2016-06-09Add pacemaker nuage profile.Dan Prince1-0/+33
The pacemaker version of nuage has its DB sync at a different step so we need a separate profile to ensure plugin.ini exists. Change-Id: Ia4a297008b259a8e238bd1ad511e82f4e5ab6d63
2016-06-09Make neutron server/ml2 profiles match t-h-tDan Prince2-10/+27
This patch brings the neutron profiles and the associated steps in line with what already happens in t-h-t. Specifically: -we want to create the db $step >= 2 and $sync_db -we want to make sure plugin.ini exists before the neutron dbsync -we want to make sure the db sync runs before neutron::server starts when using pacemaker -split the neutron server profiles. They are quite different across pacemaker and base. Change-Id: I52815f45a04bf3e39940b9cb116261730580a3e2
2016-06-05Drop duplicate neutron pacemaker constraintDan Prince1-14/+1
Drop a duplicate keystone-to-neutron-server-constraint constraint for the neutron server profile. Change-Id: I928f9f9f3cf665ac80696f66e1d64ceb02129b8e
2016-05-09Remove manage_service and enabled from TripleO manifestsGiulio Fidente5-19/+4
These can be controlled via the specific Pacemaker role template. Depends-On: I91a4267f0fc230f63df3333747d28463c7ae55fe Change-Id: I8ef7bb94e048b998712b3534ceb51a7d10d016e9
2016-05-05Add neutron profilesMichael Chapman7-0/+396
Implements: blueprint refactor-puppet-manifests Add neutron profiles for both pacemaker and non-ha. HA profiles are designed such that they include the base profiles, disabling features as needed, while the base profile can be used independently. Co-Authored-By: Dan Prince <dprince@redhat.com> Change-Id: Ida781badbcd63bbcb481a2170638aefe262b717b