[Pacemaker] uname eq node-name

[Andreas Mock]

Hi Andrew,

can you tell me what the attribute  #uname is holding?
Is it the node-name or the 'uname -n' of the node?
(I justt read
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Pacemaker_
Explained/index.html#_which_resource_instance_is_promoted)

Is there an attribute like '#node'or '#nodename'?

Best regards
Andreas Mock



-----Ursprüngliche Nachricht-----
Von: Andrew Beekhof [mailto:andrew at beekhof.net] 
Gesendet: Mittwoch, 12. Juni 2013 06:45
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] uname eq node-name


On 12/06/2013, at 2:40 PM, "Andreas Mock" <andreas.mock at web.de> wrote:

> Hi Andrew,
> 
> thank you for that information. You know, often one answer is followed 
> by many other questions. The same here:
> 
> Is there a tool, where a script is able to determine the node name 
> based on the uname?
> For a script it is easy to find the nodename (uname -n) it is running 
> on. But what has to be done when the script needs to know the 
> node-name it is running on?

crm_node -n is a good place to start, but requires a running cluster.

> 
> Best regards
> Andreas Mock
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Andrew Beekhof [mailto:andrew at beekhof.net]
> Gesendet: Mittwoch, 12. Juni 2013 00:27
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pacemaker] uname eq node-name
> 
> 
> 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
> 
> 
> _______________________________________________
> 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
> 
> 
> _______________________________________________
> 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


_______________________________________________
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