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] Xen-API Preview Tree

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] Xen-API Preview Tree
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 10 Oct 2006 14:18:14 +0100
Cc: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 10 Oct 2006 06:18:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061009224535.GA7376@xxxxxxxxxxxxxxxxxxxxxx>
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: <20061008210013.GA21597@xxxxxxxxxxxxxxxxxxxxxx> <20061009174737.GA17524@xxxxxxxxxx> <20061009224535.GA7376@xxxxxxxxxxxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Mon, Oct 09, 2006 at 11:45:35PM +0100, Ewan Mellor wrote:
> On Mon, Oct 09, 2006 at 06:47:37PM +0100, Daniel P. Berrange wrote:
> 
> > With the lifecycle patches, 'xm list' and 'GET /xend/domains' will now
> > include inactive domains as well as active domains. eg
> > 
> >   # xm list
> >   Name                              ID Mem(MiB) VCPUs State  Time(s)
> >   Domain-0                           0      594     2 r-----    22.2
> >   guest3                            -1      400     1 ------    14.7
> > 
> > This can cause a slight compatability problem because there has previously
> > been the tacit assumption that "ID" is a unique way to refer to a domain
> > running on a box. With all inactive domains now returning '-1' this is no
> > longer valid. So I think that returning inactive domains by default for
> > commands line 'xm list' or the raw  'GET /xend/domains' may well cause
> > compatability problems for existing users of this command / API. 
> 
> Note that the domain ID is a unique identifier for the domain, but _not_ a
> unique identifier for a VM.  If a VM is migrating to localhost, for example,
> then a given VM may have two different domain IDs.

Ah yes, good point.

> That said, I certainly agree that the change in semantics of the old protocol
> is inappropriate, and I'll put that on the list to be fixed.  Your
> proposal for a flag to xm list sounds fine to me also (though I'm
> tempted to word it as "state=Running" rather than "scope=active", to
> reuse the existing VM state mechanisms).  Regardless of the details, the
> basic idea is sound, and we'll put that in certainly.

Yeah, 'state' sounds like a better parameter name to me.

> > Finally, I'd also like to see the 'xend_config_version' field for 'xm info'
> > incremented from '2' to '3' to allow clients to easily detect that the XenD
> > they're talking to has this new capability for configs.
> 
> Definitely.

Thanks!

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

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