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-api

Re: [Xen-API] legacy vbds and new vdis

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-API] legacy vbds and new vdis
From: Tom Wilkie <tom.wilkie@xxxxxxxxx>
Date: Wed, 9 May 2007 10:53:13 +0100
Cc: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 09 May 2007 02:51:24 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=Ro21gFM3Pah29EJuIYq4TIpEJ4DozE6P3fn9851asGzUOSQpMRRFrpPyfGVOmnSC5DtTJj6pbR4NGT8tzlUEXSp1m+loelCcoRcZMCAUgGxy/mcHanBhU6ydPtrNFFNk/xG84MQWK7yEyC1ubHdIWEI42Z5/mz94SXFQex1G5z4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=tlI178F9rN6EAA5bh91dhog9oN+Og1UKKlONXWiJF3ZnmR4nG+N6EcQoDbeOOJDoqeOZD/fYApJYeARMC147JhYZR92uGd+VYxmbvtRBfKtycxyq+jNPlFYIMmTFb7B7MXZbU92NhTlmppDLDDgUCmYPC9cnrEFSszSxFctfDp8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46410F01.3070703@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <46410F01.3070703@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
If you use the new xm which creates stuff via the XenAPI, then a vdi is created. If you look at tools/python/xen/xm/xenapi_create.py theres code that basically already does this, but in xm.
If you want to put this into xend for the old api, then I think that  
would be fine, but we're going to deprecate and eventually remove the  
old SXP based interface.
Hope this helps

Tom

On 9 May 2007, at 01:00, Jim Fehlig wrote:

While moving the cim providers forward on new Xen API functionality I
come across a problem retrieving the uname information of a vbd. If vbd
is created via Xen API, a vdi had to be created first and is
subsequently retrievable via vdi field of vbd record. However, if a vm
is 'xm newed' or 'xm created' using a traditional conf file, vdis are
not created and hence not accessible via the vdi field of vbd. So there is no way to retrieve (via Xen API) the uname of device backing the vbd.
I'm considering a patch that creates a 'default' vdi for each vbd when
vms are created outside of Xen API, but not convinced this is the proper
solution.  Suggestions before creating such a patch?

Regards,
Jim

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api

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