On 02/12/2013 02:38 AM, Andrew Beekhof wrote: > On Tue, Feb 12, 2013 at 3:09 AM, Dennis Jacobfeuerborn > <denni...@conversis.de> wrote: >> On 02/11/2013 11:30 AM, Andrew Beekhof wrote: >>> On Mon, Feb 11, 2013 at 9:24 PM, Viacheslav Biriukov >>> <v.v.biriu...@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 most (if not all) openstack deployments, it does. > Even better, the static IPs you can assign belong to the physical > hosts and don't show up inside the guests - so corosync can't bind to > them.
You are probably talking about the floating IPs. The primary IPs (usually in the 10.0.0.0/8 range) of the interfaces however should work fine for this. There's no magic involved. Regards, Dennis _______________________________________________ Pacemaker mailing list: Pacemaker@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
