[ClusterLabs Developers] How to implement fencing agent with no associated hardware device with Pacemaker?

Andrei Borzenkov arvidjaar at gmail.com
Fri Jul 31 02:02:50 EDT 2020

30.07.2020 22:17, Philippe M Stedman пишет:
> Thanks Gerry.
> Hi Reid,
> The shared storage solution we are using has clustering capabilities of its
> own built into it and is able to remotely fence off the lost node, all we
> need to do is run the command to expel/fence the lost node as part of our
> own custom fencing agent on the surviving node.
> FYI, the shared storage solution I am referring to here is IBM Spectrum
> Scale.


>   On Wed, Jul 29, 2020 at 8:34 PM Philippe M Stedman <pmstedma at us.ibm.com>
>   wrote:
>     Hi ClusterLabs developers,
>     I am looking into how to develop a fencing agent for Pacemaker that is
>     not associated to any underlying hardware device. In our case we have
>     two servers (we will expand to more in the future) which have access to
>     shared storage. When one of the two nodes fails, we expect the
>     surviving node to invoke our user-defined fencing agent and run a
>     series of commands which will "expel" the lost host from accessing
>     shared storage.
>     Do you have any advice on how to go about implementing such a solution?
>     All the examples I can find online revolve around using some sort of
>     underlying hardware device to implement fencing.

In this case your fencing *is* associated with specific underlying
hardware device. Just start with any of existing fencing or stonith
agents and fill in commands to your underlying hardware to fence off
node. You probably will need some sort of mapping from node name to
whatever is required by your hardware to identify it.

More information about the Developers mailing list