1 heat_template_version: pike
4 Pacemaker remote service configured with Puppet
9 description: Dictionary packing service data
13 description: Mapping of service_name -> network name. Typically set
14 via parameter_defaults in the resource registry. This
15 mapping overrides those in ServiceNetMapDefaults.
22 description: Role name on which the service is applied
26 description: Parameters specific to the role
30 description: Mapping of service endpoint -> protocol. Typically set
31 via parameter_defaults in the resource registry.
33 PacemakerRemoteAuthkey:
35 description: The authkey for the pacemaker remote service.
38 MonitoringSubscriptionPacemakerRemote:
39 default: 'overcloud-pacemaker_remote'
43 description: Whether to enable fencing in Pacemaker or not.
48 Pacemaker fencing configuration. The JSON should have
49 the following structure:
53 "agent": "AGENT_NAME",
54 "host_mac": "HOST_MAC_ADDRESS",
55 "params": {"PARAM_NAME": "PARAM_VALUE"}
64 "host_mac": "52:54:00:aa:bb:cc",
66 "multicast_address": "225.0.0.12",
67 "port": "baremetal_0",
69 "manage_key_file": true,
70 "key_file": "/etc/fence_xvm.key",
71 "key_file_password": "abcdef"
77 PacemakerRemoteLoggingSource:
80 tag: system.pacemaker_remote
81 path: /var/log/pacemaker.log
83 /^(?<time>[^ ]*\s*[^ ]* [^ ]*)
90 description: Role data for the Pacemaker remote role.
92 service_name: pacemaker_remote
93 monitoring_subscription: {get_param: MonitoringSubscriptionPacemakerRemote}
96 logging_source: {get_param: PacemakerRemoteLoggingSource}
98 tripleo.pacemaker_remote.firewall_rules:
99 '130 pacemaker_remote tcp':
103 tripleo::fencing::config: {get_param: FencingConfig}
104 enable_fencing: {get_param: EnableFencing}
105 tripleo::profile::base::pacemaker_remote::remote_authkey: {get_param: PacemakerRemoteAuthkey}
107 include ::tripleo::profile::base::pacemaker_remote