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

[Xen-users] Opinion on best way to use network storage

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: VPS Lime <vpslime@xxxxxxxxx>
  • Date: Thu, 11 Nov 2010 22:28:46 -0500
  • Delivery-date: Thu, 11 Nov 2010 19:30:05 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=F+9Gr1/4C/1SzzoeCStUJH3HPVQAlhRSFQbmoLrFxP76cPvxZAb68ak0WK+veOp4Cz ciAw1VDTUlbbgRZwrccicBIPA1ISgE0L9GAIUBiHNsX63CWhkFC8AvsniofWFyieGdm9 VcPO5FrdTHf4qWEQvpsTuJQ7h9GAenO2XpiWc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I need the community's opinion on the best way to use my storage SAN to host xen images.  The SAN itself is running iSCSI and NFS.  My goal is to keep all my xen images on the SAN device, and to be able to easily move images from one host to another as needed while minimizing storage requirements and maximizing performance. 

What I see are my options:

1) Export a directory through NFS.  Create image files on the NFS mount and have each zen guest use the image off the NFS mount.  This has the benefit of all images being visible to all hosts (on the NFS mount), but I'm not sure about the performance.
2) Create an image on the SAN server for each XEN host and export it to the XEN servers through iSCSI.  The XEN server will see it as a VolumeGroup.  Create Logical Volumes in the VolumeGroup for each XEN guest.  Has the advantage of using LVM for the guest instead of an image file (which is rumored to be faster).  Disadvantage is individual images are not easily moved to other hosts
3) Create a image on the SAN server for each XEN guest and export it through iSCSI.  Attach XEN guests directly to the iSCSI image.  Has the advantage of being portable to other hosts, maybe more efficient?  

Thanks in advance

Xen-users mailing list



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