1 heat_template_version: pike
4 Pacemaker remote service configured with Puppet
9 description: Mapping of service_name -> network name. Typically set
10 via parameter_defaults in the resource registry. This
11 mapping overrides those in ServiceNetMapDefaults.
18 description: Role name on which the service is applied
22 description: Parameters specific to the role
26 description: Mapping of service endpoint -> protocol. Typically set
27 via parameter_defaults in the resource registry.
29 PacemakerRemoteAuthkey:
31 description: The authkey for the pacemaker remote service.
34 MonitoringSubscriptionPacemakerRemote:
35 default: 'overcloud-pacemaker_remote'
39 description: Whether to enable fencing in Pacemaker or not.
44 Pacemaker fencing configuration. The JSON should have
45 the following structure:
49 "agent": "AGENT_NAME",
50 "host_mac": "HOST_MAC_ADDRESS",
51 "params": {"PARAM_NAME": "PARAM_VALUE"}
60 "host_mac": "52:54:00:aa:bb:cc",
62 "multicast_address": "225.0.0.12",
63 "port": "baremetal_0",
65 "manage_key_file": true,
66 "key_file": "/etc/fence_xvm.key",
67 "key_file_password": "abcdef"
73 PacemakerRemoteLoggingSource:
76 tag: system.pacemaker_remote
77 path: /var/log/pacemaker.log
79 /^(?<time>[^ ]*\s*[^ ]* [^ ]*)
86 description: Role data for the Pacemaker remote role.
88 service_name: pacemaker_remote
89 monitoring_subscription: {get_param: MonitoringSubscriptionPacemakerRemote}
92 logging_source: {get_param: PacemakerRemoteLoggingSource}
94 tripleo.pacemaker_remote.firewall_rules:
95 '130 pacemaker_remote tcp':
99 tripleo::fencing::config: {get_param: FencingConfig}
100 enable_fencing: {get_param: EnableFencing}
101 tripleo::profile::base::pacemaker_remote::remote_authkey: {get_param: PacemakerRemoteAuthkey}
103 include ::tripleo::profile::base::pacemaker_remote