Pass enabled and manage_service to Neutron/L3 when Pacemaker
authorGiulio Fidente <gfidente@redhat.com>
Wed, 18 May 2016 17:06:46 +0000 (19:06 +0200)
committerGiulio Fidente <gfidente@redhat.com>
Wed, 18 May 2016 17:06:46 +0000 (19:06 +0200)
We can drive enabled and manage_service from the Pacemaker specific
templates so change I8ef7bb94e048b998712b3534ceb51a7d10d016e9
removed that logic from the TripleO specific manifests. This change
adds them into the Pacemaker template for the Neutron/L3 agent.

Change-Id: I1146a8bae4938577e9927d1ce74009e066cb58dd

puppet/services/pacemaker/neutron-l3.yaml

index 84bff80..cbe2ddb 100644 (file)
@@ -29,5 +29,7 @@ outputs:
         map_merge:
           - get_attr: [NeutronL3Base, role_data, config_settings]
           - tripleo::profile::pacemaker::neutron::enable_l3: True
+            neutron::agents::l3::enabled: false
+            neutron::agents::l3::manage_service: false
       step_config: |
         include ::tripleo::profile::pacemaker::neutron::l3