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

[Xen-users] LVM snapshots to provide HA iSCSI storage

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] LVM snapshots to provide HA iSCSI storage
From: "Angel L. Mateo" <amateo@xxxxx>
Date: Tue, 09 Feb 2010 14:43:24 +0100
Delivery-date: Tue, 09 Feb 2010 05:43:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

        This is not a properly Xen problem, but I guess somebody has set out
this same configuration, so I think you could help me. So sorry if you
this is an offtopic message.

        We are planning to migrate our locally storaged VM (in LVM volumes) to
a central storage, so we could you live migration and to provide HA
mechanisms to our VM. For the central storage, we are planning to use
iSCSI with LVM over it.

        The problem with this configuration is that if your iSCSI server (the
target) fails, then all your VMs fail, and this a problem for us.

        So what we have thought is to use LVM to mirror our volumes. The idea
is that the disk for a VM is in a iSCSI LVM volume:

* When we start a VM, then we create a mirror using the the iSCSI LVM
and another volume in a local disk, then the VM uses this mirror.
* If the iSCSI server goes down, there is no problem, because we have
the local volume (when it goes up again, the mirror will synchronize the
contents).
* When we stop the VM, then we destroy the mirror and store the iSCSI
volume.
* When the migration, we destroy the mirror in the dom0 and create it in
the other dom0.

        Running this scripts is not a problem, because we are going to use
opennebule, where we can personalize the actions taking place in these
situations.

        Is this posible? Does anybody use this idea (or similar)? Could anybody
point me to some documentation?

-- 
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información       _o)
y las Comunicaciones Aplicadas (ATICA)      / \\
http://www.um.es/atica                    _(___V
Tfo: 868887590
Fax: 868888337


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

<Prev in Thread] Current Thread [Next in Thread>