Add support for autofencing to Pacemaker Remote.
We now pass configuration for autofencing to Pacemaker Remote nodes. Change-Id: Ibb9c65a83cc909528024c538cf3bcc96390c555e Depends-On: I87c60bd56feac6dedc00a3c458b805aa9b71d9ce Closes-Bug: #1686115
This commit is contained in:
parent
5781c925f4
commit
05953542a6
@ -34,6 +34,42 @@ parameters:
|
||||
MonitoringSubscriptionPacemakerRemote:
|
||||
default: 'overcloud-pacemaker_remote'
|
||||
type: string
|
||||
EnableFencing:
|
||||
default: false
|
||||
description: Whether to enable fencing in Pacemaker or not.
|
||||
type: boolean
|
||||
FencingConfig:
|
||||
default: {}
|
||||
description: |
|
||||
Pacemaker fencing configuration. The JSON should have
|
||||
the following structure:
|
||||
{
|
||||
"devices": [
|
||||
{
|
||||
"agent": "AGENT_NAME",
|
||||
"host_mac": "HOST_MAC_ADDRESS",
|
||||
"params": {"PARAM_NAME": "PARAM_VALUE"}
|
||||
}
|
||||
]
|
||||
}
|
||||
For instance:
|
||||
{
|
||||
"devices": [
|
||||
{
|
||||
"agent": "fence_xvm",
|
||||
"host_mac": "52:54:00:aa:bb:cc",
|
||||
"params": {
|
||||
"multicast_address": "225.0.0.12",
|
||||
"port": "baremetal_0",
|
||||
"manage_fw": true,
|
||||
"manage_key_file": true,
|
||||
"key_file": "/etc/fence_xvm.key",
|
||||
"key_file_password": "abcdef"
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
type: json
|
||||
PacemakerRemoteLoggingSource:
|
||||
type: json
|
||||
default:
|
||||
@ -60,6 +96,8 @@ outputs:
|
||||
proto: 'tcp'
|
||||
dport:
|
||||
- 3121
|
||||
tripleo::fencing::config: {get_param: FencingConfig}
|
||||
enable_fencing: {get_param: EnableFencing}
|
||||
tripleo::profile::base::pacemaker_remote::remote_authkey: {get_param: PacemakerRemoteAuthkey}
|
||||
step_config: |
|
||||
include ::tripleo::profile::base::pacemaker_remote
|
||||
|
Loading…
x
Reference in New Issue
Block a user