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

[Reid Wahl]

If you have a hardware **watchdog timer**, then sbd is a good option. With
shared storage, you can also implement fence_sbd.

KVM virtual machines also offer an emulated hardware watchdog. I'm not sure
whether that would fit your criteria or not -- it depends on whether you're
only excluding a management interface like an iLO/IMM, or whether you're
also excluding a watchdog timer.

If you can't use sbd or conventional power fencing (e.g., fence_ipmilan),
then you may be able to use fence_scsi or fence_mpath since you have shared
storage.

What hardware or virtualization platform are you running on, and is there a
particular reason you don't want to associate fencing with a hardware
device?

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.
>
> Help is greatly appreciated.
>
> Thanks,
>
> *Phil Stedman*
> Db2 High Availability Development and Support
> Email: pmstedma at us.ibm.com
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/developers
>
> ClusterLabs home: https://www.clusterlabs.org/
>


-- 
Regards,

Reid Wahl, RHCA
Software Maintenance Engineer, Red Hat
CEE - Platform Support Delivery - ClusterHA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/developers/attachments/20200729/2c5d949b/attachment-0002.htm>