[Pacemaker] Corosync over DHCP IP

[Viacheslav Biriukov]

Yes, you are right.
In our case we got this bug with dnsmasq (
http://markmail.org/message/7kjf4hljszpydsrx#query:+page:1+mid:7kjf4hljszpydsrx+state:results
).
Still investigating.



2013/2/11 Dennis Jacobfeuerborn <dennisml at conversis.de>

> On 02/11/2013 11:30 AM, Andrew Beekhof wrote:
> > On Mon, Feb 11, 2013 at 9:24 PM, Viacheslav Biriukov
> > <v.v.biriukov at gmail.com> wrote:
> >> It is VM in the OpenStack. So we can't use static IP.
> >> Right now investigating why interface become down.
> >
> > Even if you solve that, dynamic IP addresses are fundamentally
> > incompatible with cluster software.
> > You're effectively trying to create a cluster out of nodes which
> > change their name every time they boot.
>
> DHCP doesn't necessarily mean a dynamic IP. In cloud environments the DHCP
> Server usually has a record in the leases database that associates a MAC
> address with an IP address so that the host will always get the same IP
> assigned.
>
> Regards,
>   Dennis
>
> _______________________________________________
> 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
>



-- 
Viacheslav Biriukov
BR
http://biriukov.me
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130211/84280ec2/attachment-0003.html>