Sometimes in certain environments we need to set specific cluster
properties to tune the control plane to that specific situation.
Tested with:
tripleo::profile::base::pacemaker::cluster_properties:
test:
property: shutdown-escalation
value: 6m
tries: 5
test2:
property: priority-fencing-delay
value: 10
tries: 5
test3:
property: startup-fencing
value: false
tries: 5
And obtained the correctly set properties:
[root@controller-0 hieradata]# pcs property
Cluster Properties:
...
priority-fencing-delay: 10
shutdown-escalation: 6m
startup-fencing: false
Change-Id: Iebd1ae24a69fb0bdc5f7f7c75a1a79e9c608ba96
(cherry picked from commit 056ace0c8c)
(cherry picked from commit ccb419ceb5)