[Pacemaker] Simpler solution than custom OCF scripts ?

Lars Marowsky-Bree lmb at suse.com
Wed Apr 4 10:25:33 EDT 2012

On 2012-04-04T15:12:49, Julien Cornuwel <cornuwel at gmail.com> wrote:

> Hi,
> I'm quite new to Corosync/Pacemaker but I managed to get my cluster to work:
> I have 2 nodes on CentOS5.8 (therefore Pacemaker 1.0.12 and Corosync
> 1.2.7) running samba-winbind-radius.
> The cluster is running fine, but it only knows about one resource, the
> failover IP address.
> Now, I would like to go further and make the cluster aware of the
> state of the above-mentionned services. Reading the documentation, I
> understand that I should write OCF scripts for each of the resources
> (winbind and radius) that really check that the service is delivered,
> not just that the daemon is running. Then declare all these resources
> and their affinities on the cluster.

You can just use the LSB init script if one is provided.

> Or even the quick-and-dirtiest: run my script with cron and stop the
> corosync daemon if I detect a problem ^^

My first thought to this was "WTF?". ;-)


Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

More information about the Pacemaker mailing list