aboutsummaryrefslogtreecommitdiffstats
path: root/manifests/profile/pacemaker
AgeCommit message (Collapse)AuthorFilesLines
2016-08-11Removing WARNING: line has more than 140 characters in puppet-tripleo profilesCarlos Camacho1-1/+5
Some lint checks are returning: WARNING: line has more than 140 characters in puppet-tripleo profiles This patch will remove those warnings by adding \'s Change-Id: I19b56c93db82948fb0498a4c9851b522c81946f8
2016-08-08Fix parameters and headers inconsistency in the puppet manifests.Carlos Camacho48-229/+162
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-08-05Remove keystone PKI cert generationSteven Hardy1-3/+0
We don't currently offer any parameter interface to enable PKI certs, and these have all been deprecated by keystone, so remove them. Change-Id: I8232262b928c91dcde7bea2f23fa2a7c2660719e
2016-08-04Merge "Next generation HA architecture work"Jenkins2-17/+17
2016-08-03Remove unused parameter in saharaCarlos Camacho1-12/+1
Remove unused parameter in sahara Change-Id: I46c033b410ab850289b798ee93990b6fb10c80ea
2016-08-02Fixup nit in manila pacemaker profile, duplicate variablemarios1-1/+0
See discussion at https://review.openstack.org/#/c/342961/8 Change-Id: I571b65a5402c1028418476a573ebeb9450ed00c9
2016-08-01Next generation HA architecture workMichele Baldessari2-17/+17
This change moves the cinder-volume/cinder-scheduler constraints in the cinder-scheduler profile as these can't be applied by the cinder-volume service when cinder-scheduler isn't managed by Pacemaker. Blueprint: https://blueprints.launchpad.net/tripleo/+spec/ha-lightweight-architecture Change-Id: I5e7585c08675d8a4bd071523b94210d325d79b59 Implements: blueprint ha-lightweight-architecture Co-Author: cmsj@tenshu.net
2016-07-29Move constraints to their respective servicesMichele Baldessari2-0/+36
The openstack-core-then-httpd constraint needs to live in the apache pacemaker manifest and not in the main controller manifest file. The same goes for those specific vsm/cisco neutron resources. Change-Id: I2041d4d163f051427b62eec07b8345ad7006cc1d
2016-07-29Merge "Move nova constraints from controller manifest to each service"Jenkins3-0/+87
2016-07-28Merge "Remove global openstack-core resource"Jenkins1-11/+0
2016-07-28Merge "Create role for the fake openstack-core resource"Jenkins1-0/+59
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-27Remove global openstack-core resourceGiulio Fidente1-11/+0
The openstack-core resource is not needed by the NG Pacemaker architecture. It was moved into an isolated role by [1] so that it could optionally be enabled when wanting the older architecture. This submission removes the old openstack-core global resource. 1. I74a62973146c0261385ecf5fd3d06db51e079caa Change-Id: I16a786ce167c57848551c7245f4344c382c55b3d
2016-07-27Create role for the fake openstack-core resourceGiulio Fidente1-0/+59
Change-Id: I74a62973146c0261385ecf5fd3d06db51e079caa
2016-07-27profile/base/nova: declare nova class and configure cache correctly.Emilien Macchi1-1/+8
Nova {} workaround is not working correctly, we need to merge this patch so we can move out ::nova from THT completely. Also we need to use nova::cache to configure memcached parameters. Co-Authorized-By: Giulio Fidente <gfidente@redhat.com> Co-Authorized-By: Sven Anderson <sven@redhat.com> Co-Authorized-By: Emilien Macchi <emilien@redhat.com> Depends-On: I52d5badb9960124bb8fcb54983db2853c4185e77 Depends-On: I3e400a5f64b85f0d374fc02cc5e4080d19d0f2e4 Depends-On: Iee5f8015cbf40ca0e9a435a7de919ebdb74cf93f Change-Id: Ie4e72e765f6a8ade48d4b2b766f067872554d1a2
2016-07-25Merge "Add base constraint so gnocchi metricd is tied to core-clone"Jenkins1-0/+9
2016-07-22Merge "use parameter to lookup the step instead of hiera again"Jenkins1-3/+3
2016-07-22Merge "Remove unused redis_vip parameter"Jenkins1-4/+0
2016-07-22use parameter to lookup the step instead of hiera againEmilien Macchi1-3/+3
In some profiles, we were looking up the $step by using Hiera again, while we already do it in the parameter definition. When using this class outside THT, it will fail but with this patch, we could use just set the $step parameter and the rest of the manifest will work. Change-Id: I7082f47204fb4e529b164e4c4f1032e7bdd88f02
2016-07-21Merge "Deploy Keystone and Gnocchi API with new Apache profile"Jenkins2-0/+2
2016-07-21Merge "Include gnocchi config on non-bootstrap nodes"Jenkins1-2/+4
2016-07-21Deploy Keystone and Gnocchi API with new Apache profileEmilien Macchi2-0/+2
Deploy Keystone and Gnocchi API with the new Apache/Pacemaker profile. Change-Id: Id28c618133e53e28dfac7e3e9cf9f5f5a6b2421a
2016-07-21Remove unused redis_vip parameterGiulio Fidente1-4/+0
Change-Id: I6ba962c682dc2ab8c6ee5238e0c176d9ae05d696
2016-07-20Include gnocchi config on non-bootstrap nodesBen Nemec1-2/+4
Change I67a15dc83a754fb6f5fe25c64ae9e7d29c58fcec removed the gnocchi configuration completely from non-bootstrap nodes. This changes it so the configuration is included on all nodes, but the db sync is only included on bootstrap. Change-Id: If402becc900c175f5b3bb95c3413276e5a04b4f7 Closes-Bug: 1604708
2016-07-20Implement Apache pacemaker profileEmilien Macchi2-0/+51
Deploy Apache with Pacemaker in a new profile. Change-Id: I9ae6cee2bfb0f8974d41d700454cfde2df06c2d1
2016-07-20Add base constraint so gnocchi metricd is tied to core-clonePradeep Kilambi1-0/+9
Currently if we manually restart the cluster saometimes gnocchi statsd doesnt comeup as galera is not up yet. This should tie the metrics to core and follow the order. Closes-bug: #1604860 Change-Id: I5ec29622938336410b91785ca49b410bcdd30cdd
2016-07-20Merge "Make ::tripleo::profile::base classes work with multiple nodes"Jenkins12-76/+19
2016-07-20Merge "make sure we start nova-compute after nova-conductor"Jenkins1-0/+5
2016-07-19Only sync the gnocchi db on the pacemaker masterJames Slagle1-6/+1
The gnocchi db sync is being run from multiple controllers causing errors in CI. See the bug for more details. Change-Id: I67a15dc83a754fb6f5fe25c64ae9e7d29c58fcec Closes-Bug: #1604624
2016-07-18Make ::tripleo::profile::base classes work with multiple nodesMichele Baldessari12-76/+19
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-15Merge "Add MySQL profiles"Jenkins1-0/+184
2016-07-13Add MySQL profilesEmilien Macchi1-0/+184
Add MySQL profiles, for non-ha and ha scenarios. Change-Id: I7ddae28a6affd55c5bffc15d72226a18c708850e Closes-Bug: #1601853
2016-07-12Move gnocchi clustercheck to step 2Carlos Camacho1-4/+7
As not having guarantee of being installed on same node, the dbsync will be on step 3 and the clustercheck on 2. Change-Id: Id728aae79442c45ab48fe0914c065f1807e8890d
2016-07-09Merge "Split Sahara pacemaker roles into separate services"Jenkins3-33/+102
2016-07-08Merge "Fix Ceilometer profiles"Jenkins2-41/+5
2016-07-08Use include for base neutron profileDan Prince1-3/+1
Simplify the base neutron profile so that we always include the neutron and neutron::config classes at step 3. In doing so we can now simplify the pacemaker version to use a simple include which will avoid duplicate class errors. Change-Id: I95b9188607ab6c599ad4cde6faa1deb081618f3e
2016-07-08Split Sahara pacemaker roles into separate servicesBrad P. Crochet3-33/+102
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: Id61eb15b1e2366f5b73c6e7d47941651e40651b1 Partial-Bug: #1592284
2016-07-06Fix Ceilometer profilesPradeep Kilambi2-41/+5
* Configure ceilometer to default mongodb backend. * remove useless sync_db parameter in pacemaker class. * Remove duplicated resource for ceilometer central agent service with pcmk. * Remove pacemaker delay resource dependency, the resource does not exist anymore. Change-Id: Ie337bfe770c5b22158dc307eb36e39c2b93b95a9
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-06Merge "Add gnocchi profiles"Jenkins4-0/+230
2016-07-06Merge "nova: do not manage nova-compute with pacemaker"Jenkins6-9/+35
2016-07-05Merge "Split Heat pacemaker roles into separate services"Jenkins5-86/+203
2016-07-05Add gnocchi profilesPradeep Kilambi4-0/+230
Implements: blueprint refactor-puppet-manifests Co-Authored-By: Carlos Camacho <ccamacho@redhat.com> Co-Authored-By: Juan Antonio Osorio Robles <jaosorior@redhat.com> Change-Id: I38f218da118c45f3af1938eb17298017f4c70e24
2016-07-04nova: do not manage nova-compute with pacemakerEmilien Macchi6-9/+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-07-02Set bootstrap_nodeid to undef by defaultEmilien Macchi11-22/+22
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-07-01Merge "Set manage_roles for all steps in Keystone/Pacemaker"Jenkins1-7/+1
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-29Set manage_roles for all steps in Keystone/PacemakerGiulio Fidente1-7/+1
We the base::keystone profile is trying to create users and roles before step 5, this change will set the a value for manage_roles from the pacemaker profile for all steps. Change-Id: I7aca8d6418988160641b29f9396a0fbe33b64e51
2016-06-29Remove base/neutron/ml2.ppEmilien Macchi1-38/+0
Not used anymore. Change-Id: Id3f943132fce235a5a4888da30332b8fc2434a78 Depends-On: I6436c5c36ac0081a720cb8a737a573b1246127a1