summaryrefslogtreecommitdiffstats
path: root/manifests/profile/pacemaker/neutron/server.pp
AgeCommit message (Collapse)AuthorFilesLines
2016-08-08Fix parameters and headers inconsistency in the puppet manifests.Carlos Camacho1-1/+0
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-02Set bootstrap_nodeid to undef by defaultEmilien Macchi1-2/+2
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-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-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-09Make neutron server/ml2 profiles match t-h-tDan Prince1-8/+14
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 Fidente1-2/+0
These can be controlled via the specific Pacemaker role template. Depends-On: I91a4267f0fc230f63df3333747d28463c7ae55fe Change-Id: I8ef7bb94e048b998712b3534ceb51a7d10d016e9
2016-05-05Add neutron profilesMichael Chapman1-0/+58
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