WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] best practices in using shared storage forXENVirtualMach

To: Freddie Cash <fjwcash@xxxxxxxxx>, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] best practices in using shared storage forXENVirtualMachines and auto-failover?
From: Jeff Sturm <jeff.sturm@xxxxxxxxxx>
Date: Thu, 14 Oct 2010 11:59:34 -0400
Cc:
Delivery-date: Thu, 14 Oct 2010 09:02:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikU6qRJvJEjK8K7O3cm6t7gY_tjV8dqyq+32Cwm@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinDO4=ruP+bPcsdc6_hhJpmDZSBs_Es8hTqi81e@xxxxxxxxxxxxxx><DD177853709B410F8CBF1161674AED50@maindesk><64D0546C5EBBD147B75DE133D798665F06A12481@xxxxxxxxxxxxxxxxx> <AANLkTikU6qRJvJEjK8K7O3cm6t7gY_tjV8dqyq+32Cwm@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActrtefFcG+m6l4DRxuScc9R/zNL5QAAX4Kg
Thread-topic: [Xen-users] best practices in using shared storage forXENVirtualMachines and auto-failover?
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Freddie Cash
> Sent: Thursday, October 14, 2010 11:38 AM
> To: xen-users
> Subject: Re: [Xen-users] best practices in using shared storage 
> forXENVirtualMachines
> and auto-failover?
> 
> > 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.
> 
> Would you run the iSCSI initiator in the host and attach the block device to 
> the guest?
> Or would you run the iSCSI initiator in the guest?

I like to do the former.  That makes the guest easier--you don't have to figure 
out things like modifying initrd to do boot-from-SAN.

> How does the migration from one host machine to another work with iSCSI?

No different than migration with any other shared storage.  Just make sure each 
dom0 has a working initiator, and is logged into the appropriate targets.  If 
your SAN has ACLs, you'll need to allow access from every possible dom0.

-Jeff

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