[Pacemaker] override node name when using cman

[Andrew Beekhof]

On Wed, Aug 29, 2012 at 11:59 PM, Patrick H. <pacemaker at feystorm.net> wrote:
> Sent: Wed Aug 29 2012 08:00:53 GMT-0400 (EDT)
> From: Andrew Beekhof <andrew at beekhof.net>
> To: The Pacemaker cluster resource manager <pacemaker at oss.clusterlabs.org>
> Subject: Re: [Pacemaker] override node name when using cman
>
>> On Wed, Aug 29, 2012 at 4:56 AM, Patrick Hemmer<pacemaker at feystorm.net>
>> wrote:
>>>
>>> It looks like when using pacemaker with cman, pacemaker gets the name of
>>> the
>>> node from the<clusternode>  'name' attribute. Is there any way to
>>> override
>>> this?
>>
>> Basically no.  Nodes need to be addressable by whatever name is supplied.
>
> Can this be put in as a feature request? It doesn't make sense to call a
> node by the name of it's interface. Also cman is more than happy to let you
> put IPs in the <clusternode> and <altname> 'name' attribute (making things
> less ambiguous is always a good thing). But Having to identify the node (in
> crm shell) by the IP address of one of it's interfaces is just not right.

Wait. What now?
We don't require (or want) people to use IP addresses as node names.

The requirement is that the 'name' attribute needs to match the output
of 'uname -n'.
Although I just posted a lengthy email about a plan to remove the
'uname -n' requirement in most cases.

>
>>
>>> If the node has multiple interfaces, I may want corosync to use an
>>> interface
>>> other than the node's main interface as the main interface for
>>> communication
>>> (like if I had a crossover cable between nodes). If I use the IP of the
>>> second interface then pacemaker uses that IP as the node name. If I give
>>> the
>>> second interface a name, it still ends up using that name instead of the
>>> node's real name (`uname -n`).
>>>
>>> _______________________________________________
>>> 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