Re: [Xen-users] 2 node - failover cluster

[Jean Baptiste FAVRE <xen-users@xxxxxxxxxxx>]

Hello,
Peter only has 2 nodes to make redundant each other.
This way, DRBD is maybe the best choice: it avoids the need of a
centralized storage and still allows live migration (and therefore
failover) of VMs.

The primary/primary mode works very well.
PV VMs storage can be defined using "disk = [ 'drbd:resource,xvda,w' ]"
(see http://www.drbd.org/docs/about/) which makes Xen in charge of
changing DRBD mode if need. But, be aware this only works for
paravirtualized VMs, not HVM ones.

The only thing is that it will not replace a pure share storage. But
basically, a SAN or NAS won't either, except (maybe) using a cluster FS
over DRBD.

Regards,
JB

On 28/04/2010 17:21, Caleb Call wrote:
> I think you may need to go back to the drawing board with your idea.
>  You say no NAS/SAN but you want shared storage???  NAS/SAN (i.e. shared
> storage) is a key part of live migration/failover in any virtualized
> (not just Xen) environment.
> 
> On Wed, Apr 28, 2010 at 1:41 AM, Peter Braun <xenware@xxxxxxxxx
> <mailto:xenware@xxxxxxxxx>> wrote:
> 
>     Hi,
> 
>     we would like to implement 2 node failover cluster running mix of
>     Win/Linux machines with automatic failover function.
> 
> 
>     Specs:
> 
>     2 identical servers with same hdd space and enough memory.
>     No NAS/SAN.
>     Windows 2008 and linux will be running in VM.
> 
> 
>     Requirements:
>     - shared storage mirrored betwen 2 hw nodes.
>     - PV drivers for windows 2008 must be available
>     - live migration of VM between nodes must be possible
>     - when one node crash, its VM should be automaticaly restarted on
>     other node
>     - support for VLAN
> 
>     What do you recommend?
>     Xen 4.0 (Windows PV drivers included?)
>     DRBD or glusterfs
>     how to manage VM (restart on other node in case of hw failure)
> 
>     Thanks for your opinion
> 
>     Peter Braun
> 
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
>     http://lists.xensource.com/xen-users
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users