[Pacemaker] Pacemaker cluster with different operating systems

[Osman Findik]

Hi Lars,
We think that the third node will be in standby, so only corosync and pacemaker processes will execute and no resource will be executed on this node by the cluster.
We also plan to use existing application servers as third node and they will continue to run their dedicated processes. Is this a bad idea? Why do you think that it isn't allowed to do anything else?

For other approaches, I only know boothd. And what I know is it is suitable for geo-redundancy purposes. I will look for fence_sanlock.

Thanks,


-----Original Message-----
From: Lars Marowsky-Bree [mailto:lmb at suse.com] 
Sent: 07 Mart 2013 Perşembe 11:12
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Pacemaker cluster with different operating systems

On 2013-03-07T05:09:25, Osman Findik <Osman.Findik at telenity.com> wrote:

> Hi all,
> We are using pacemaker with RHEL 6.2 successfully to manage pair of 
> MySQL databases. Pacemaker is coming from Red Hat High Availability Add-on. Its version is 1.1.6 Our need is to add an observer to this cluster but our existing servers are all RHEL 5.x servers. We could not locate same version of pacemaker in clusterlabs repo.

So, basically, you want a 3rd node for quorum only? I find that a kludge, since the third node needs to be maintained and configured and managed etc and isn't really allowed to do anything.

Have you investigated other approaches as a tie-breaker? external/sbd (or, in the RHEL work, fence_sanlock)? boothd?


Regards,
    Lars

--
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


_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org