[Pacemaker] CoroSync's UDPu transport for public IP addresses?

[Jan Friesse]

Dmitry,


> No, I meant that if you pass a domain name in ring0_addr, there are no
> errors in logs, corosync even seems to find nodes (based on its logs), And
> crm_node -l shows them, but in practice nothing really works. A verbose
> error message would be very helpful in such case.

This sounds weird. Are you sure that DNS names really maps to correct IP 
address? In logs there should be something like "adding new UDPU member 
{IP_ADDRESS}".

Regards,
   Honza

>
> On Tuesday, December 30, 2014, Daniel Dehennin <daniel.dehennin at baby-gnu.org>
> wrote:
>
>> Dmitry Koterov <dmitry.koterov at gmail.com <javascript:;>> writes:
>>
>>> Oh, seems I've found the solution! At least two mistakes was in my
>>> corosync.conf (BTW logs did not say about any errors, so my conclusion is
>>> based on my experiments only).
>>>
>>> 1. nodelist.node MUST contain only IP addresses. No hostnames! They
>> simply
>>> do not work, "crm status" shows no nodes. And no warnings are in logs
>>> regarding this.
>>
>> You can add name like this:
>>
>>      nodelist {
>>        node {
>>          ring0_addr: <public-ip-address-of-the-first-machine>
>>          name: node1
>>        }
>>        node {
>>          ring0_addr: <public-ip-address-of-the-second-machine>
>>          name: node2
>>        }
>>      }
>>
>> I used it on Ubuntu Trusty with udpu.
>>
>> Regards.
>>
>> --
>> Daniel Dehennin
>> Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
>> Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
>>
>
>
>
> _______________________________________________
> 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
>