aboutsummaryrefslogtreecommitdiffstats
path: root/manifests/profile/base/neutron.pp
AgeCommit message (Collapse)AuthorFilesLines
2016-07-18Make ::tripleo::profile::base classes work with multiple nodesMichele Baldessari1-2/+2
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-08Use include for base neutron profileDan Prince1-6/+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-06-07Include neutron in step 3Juan Antonio Osorio Robles1-2/+7
neutron::server requires the neutron's init.pp to be ran beforehand because init.pp installs the 'neutron' package. Else the relationship with neutron::policy will fail [1].So to address this, we move neutron's init.pp to be ran on step 3 if db_sync is enabled. [1] https://github.com/openstack/puppet-neutron/blob/master/manifests/server.pp#L498 Change-Id: I8eb497c2b483e11d1f640a7ba9fae5a9d5bcef4d
2016-05-05Add neutron profilesMichael Chapman1-0/+32
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