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] XCP - GFS - ISCSI

To: 'Pasi Kärkkäinen' <pasik@xxxxxx>
Subject: RE: [Xen-users] XCP - GFS - ISCSI
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Fri, 15 Jan 2010 11:04:03 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: Julian Chesterfield <Julian.Chesterfield@xxxxxxxxxxxxx>, 'menox menox' <menox.menox@xxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 15 Jan 2010 03:04:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100115081432.GG17978@xxxxxxxxxxx>
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: <67f1d7c11001140559q6a10c77q53785c1e415e233f@xxxxxxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD2143B8C19496@xxxxxxxxxxxxxxxxxxxxxxxxx> <20100115081432.GG17978@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqVutQVprf+kcCwQHSHdhTu5xOInwAFtO7Q
Thread-topic: [Xen-users] XCP - GFS - ISCSI
Hi Pasi,

[cc:d Julian who is responsible for storage in XCP]

> I haven't looked at the XCP code yet, but are there some special
> patches for
> LVM to make it work in a shared environment on multiple hosts?
> 
> I guess it's not CLVM, since you support snapshots.. so xapi is doing
> some coordination of management commands and making sure only one LVM
> command is issued at a time?

Julian could describe the detail better than me but my high-level understanding 
is:

* xapi nominates one host to be the 'SR master': all LVM metadata-changing 
commands are run here

* all hosts are allowed to map/unmap LVs so the LVM commands were patched to 
make absolutely sure they didn't attempt to change any metadata

* unless you request a special "raw" LV, vhd metadata is added to the LV: this 
is how we handle snapshots
 
> And after making changes to the LVM configuration xapi runs 'vgscan' on
> every host to pick up the changes?

I'll defer to Julian for this one :-)

Cheers,
Dave


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

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