[ClusterLabs] Coming in Pacemaker 2.1.2: new fencing configuration options

[Ken Gaillot]

Hi all,

We're looking ahead to the next Pacemaker release already. Even though
we had a recent release for a regression fix, I want to get back to the
goal of having a release before the holidays.

The new release will have a couple of enhancements to fencing
configuration options.

The existing pcmk_delay_base option lets you set a delay before a fence
action will be attempted. This is often used on one device in a 2-node
cluster to help avoid a "death match".

Previously, if you wanted different delays for different nodes, you had
to configure separate fencing resources, even if they used the same
device.

Now, pcmk_delay_base can take a map similar to pcmk_host_map. For
example, to use no delay on node1 and a 5-second delay on node2, you
can configure a single fencing resource with
pcmk_delay_base="node1:0s;node2:5s".

Separately, the pcmk_host_map option now supports backslash-escaped
characters (such as spaces) in the mapped name. For example, you could
set pcmk_host_map="node1:Plug\ 1;node2:Plug\ 2" if the device expects
"Plug 1" and "Plug 2" as the names.
-- 
Ken Gaillot <kgaillot at redhat.com>