[Pacemaker] uname eq node-name

Andrew Beekhof andrew at beekhof.net
Tue Jun 11 18:26:50 EDT 2013


On 11/06/2013, at 2:33 AM, Andreas Mock <Andreas.Mock at web.de> wrote:

> Hi all,
> 
> I couldn't find a definitive source stating that
> a corosync/pacemaker/cman cluster must follow the
> rule: uname -n == node-name (== DNS-name of communication-IP)

In older versions this is true (an artefact of our heartbeat heritage).
However we have been chipping away at that in 1.1.9 and I am currently running corosync 2.x with pacemaker 1.1.10-rc4 and node-name != uname -n

> 
> Can someone give a hint for related documentation?
> 
> The question arises when you want to configure a
> cman based cluster (cluster.conf) having a uname -n
> equal to the DNS-name of the external ip address but
> whant to route the cluster communication over
> the internal IP-adresse (cluster interconnect).
> I couldn't find a solution that doesn't use the
> DNS-names of the internal ip-addresses as node-names.
> 
> Hints and rules welcome!
> 
> Best regards
> Andreas Mock
> 
> 
> 
> _______________________________________________
> 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





More information about the Pacemaker mailing list