summaryrefslogtreecommitdiffstats
path: root/manifests/profile/pacemaker/keystone.pp
AgeCommit message (Collapse)AuthorFilesLines
2016-07-18Make ::tripleo::profile::base classes work with multiple nodesMichele Baldessari1-7/+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-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-18keystone: fix a race condition in bootstrapEmilien Macchi1-4/+3
Before, we had bootstrap_master set to 'undef' by default that was used to whether or not run keystone bootstrap exec during deployment. Setting the value to undef was a mistake, because enable_bootstrap in puppet-keystone is set to true by default, so bootstrap was running on all controllers at step 4 for HA scenario, while we want it to run on a single controller (pacemaker_master) at step 4, like we do for db-sync. This patch: * removes bootstrap_master. * re-use sync_db to whether or not run keystone bootstrap. so it will only run on a single node when database is ready and db-sync done (orchestration dones by anchors in puppet-keystone). Change-Id: I1042862f7c346d1c358b908c33eae0f33afd5e9f
2016-05-18Merge "Remove manage_service and enabled from TripleO manifests"Jenkins1-2/+0
2016-05-10keystone: drop usage of step 6Emilien Macchi1-1/+3
* Manage roles & endpoints at step 5 * Set correct orchestration for Pacemaker resources within a single step. Change-Id: I079e65f535af069312b602e8ff58be80ab2f2226
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-04Noop start/stop/restart action for Glance and Keystone in the rolesGiulio Fidente1-0/+7
Change-Id: I1d95746cb990292462106c191987147eba30ee61
2016-05-03Move databases creation and sync with the roleGiulio Fidente1-9/+8
This change moves the database creation and sync with the role profile, so that it's only executed when the role is enabled and by the role itself. It also calls the non-pacemaker profiles out of the 'step' conditional because the non-pacemaker profiles know how to deal with 'step' already. Change-Id: I6c752cb53090e7ef8e0319bade462f2453ed7660 Related-Bug: 1572952
2016-03-22Add keystone and db sync profilesMichael Chapman1-0/+88
Implements: blueprint refactor-puppet-manifests Add keystone profiles for both pacemaker and non-ha. Add db sync profiles for 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. Change-Id: I2faf5a78db802549053ec41678bf83bf28108189