[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] best practices in using shared storage for XENVirtualMachines and auto-failover?


  • To: <admin@xxxxxxxxxxx>, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Jeff Sturm <jeff.sturm@xxxxxxxxxx>
  • Date: Thu, 14 Oct 2010 09:45:15 -0400
  • Cc:
  • Delivery-date: Thu, 14 Oct 2010 06:46:50 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Actrk2w1CwheS1NLQtGSNpCj2+4xaQACLMYgAAJkwZA=
  • Thread-topic: [Xen-users] best practices in using shared storage for XENVirtualMachines and auto-failover?

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of admin@xxxxxxxxxxx
> Sent: Thursday, October 14, 2010 8:37 AM
> To: 'xen-users'
> Subject: RE: [Xen-users] best practices in using shared storage for
XENVirtualMachines
> and auto-failover?
> 
> It is easier to use NFS than iSCSI for shared storage target.  If you
use iSCSI, you will
> need to use a cluster aware file system to avoid data corruption.  If
your storage
> target can do both, just use NFS.

You don't need a clustered filesystem.  You don't need a shared
filesystem at all.  Just partition your shared block storage (with a
clustered logical volume manager if needed) and use a logical volume for
each domU image.

-Jeff



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.