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/
Home Products Support Community News


RE: [Xen-API] RE: Questions about the api

To: Julian Chesterfield <Julian.Chesterfield@xxxxxxxxxxxxx>
Subject: RE: [Xen-API] RE: Questions about the api
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Thu, 21 Oct 2010 20:19:41 +0100
Accept-language: en-US
Acceptlanguage: en-US
Cc: 'Tomoiaga Cristian' <cristi@xxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 21 Oct 2010 12:19:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CC07881.8010808@xxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <4C16BD5DB91CF44292D2145E0D5237351CF3AA1180@baseex> <81A73678E76EA642801C8F2E4823AD219331853AC5@xxxxxxxxxxxxxxxxxxxxxxxxx> <4CC07881.8010808@xxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActxRaCzufoHZp4lTvuoBy8ZvrN+BAADnAlQ
Thread-topic: [Xen-API] RE: Questions about the api
Julian wrote:
> I've thought for a while that it
> would be beneficial to store more metadata persistently within the SR
> itself, to make it more portable and to overcome synchronisation issues
> like this. This was the original intention for the MGT volume in LVHD.

It would be great to store stuff like VDI name_labels and VM metadata snapshots 
for DR. We should definitely do some more thinking about this.

Dave wrote (about the snapshot VDI fields)
> > We should consider allowing the backend to read/write these fields.
> > There's already precedent for that kind of thing: the backend can call
> > VDI.set_virtual_size but it looks read/only to everyone else.
> >
> I would be strongly in favour of this also.

Great. I think once we've branched for the next release we could make this 
happen in XCP unstable.


xen-api mailing list