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] High availability and live migration with just LVMand ha

To: Jeff Sturm <jeff.sturm@xxxxxxxxxx>
Subject: Re: [Xen-users] High availability and live migration with just LVMand hardware fencing
From: Bart Coninckx <bart.coninckx@xxxxxxxxxx>
Date: Wed, 19 May 2010 16:08:01 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 19 May 2010 07:08:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <64D0546C5EBBD147B75DE133D798665F055D927C@xxxxxxxxxxxxxxxxx>
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: <201005191146.18169.bart.coninckx@xxxxxxxxxx> <201005191459.34059.bart.coninckx@xxxxxxxxxx> <64D0546C5EBBD147B75DE133D798665F055D927C@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.12.4 (Linux/2.6.31.12-0.2-desktop; KDE/4.3.5; x86_64; ; )
On Wednesday 19 May 2010 15:43:19 Jeff Sturm wrote:
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> > bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Bart Coninckx
> > Sent: Wednesday, May 19, 2010 9:00 AM
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-users] High availability and live migration with
> 
> just LVMand hardware
> 
> > fencing
> >
> > Did some further research in the meantime and so far the best reason I
> 
> can
> 
> > find for using cLVM, is the making changes to the volume groups: with
> 
> cLVM
> 
> > they seem to be "published" to all Xen hosts at once, while with LVM
> 
> one needs
> 
> > to reconnect to the volume group (probably causing weird things to the
> > guests).
> 
> We've done it with and without CLVM.  It's not a requirement, but it
> works, and can compensate for storage devices that make it cumbersome to
> manage the number of LUNs needed for your deployment.
> 
> Advantanges of CLVM:
> 
> - Fully clustered, uses robust fencing, no single point of failure
> - Integration with device mapper allows for intuitive logical volume
> names
> - Works identically atop any network block storage (iSCSI etc.)
> - Supports mirroring of block devices in recent releases
> - Synchronizes volume group changes across cluster
> 
> Disadvantages:
> 
> - No support for volume snapshots (maybe someday--last I tried it didn't
> work)
> - Not available or convenient to use with all OS distributions
> - Requires cluster infrastructure--difficult to use with system
> partitions (e.g. /, /var)
> - No thin provisioning
> 
> For my money I prefer the LUN management that ships with certain SAN
> products (such as Dell's Equallogic arrays) over CLVM.  As we consider
> moving away from a RHEL-supported dom0 kernel towards something like XCP
> or XenServer, it'll become a necessity.
> 
> -Jeff
> 

Jeff,

a well put conclusion. 
Your second disadvantage particularly is relevant to me, since I need to use 
the commercially supported SLES10SP3, which has no cLVM available in it. 

Also the first one is a, to say the least, disappointing. Having the 
possibility of snapshotting is most valuable in the context of 
updating/rollback. 

By the way: would it be correct to state that cLVM is only an advantage when 
dealing with more than one volume group (being the result of having more than 
one LUN)?


thx!

B.

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

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