[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Is VM_guest_metrics implemented ?


  • To: Frederic Dang Tran <frederic.dangtran@xxxxxxxxxxxxxxxxxx>
  • From: Tom Wilkie <tom.wilkie@xxxxxxxxx>
  • Date: Mon, 28 May 2007 19:59:20 +0100
  • Cc: xen-api@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 28 May 2007 11:57:21 -0700
  • 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=CnqDh8mHlCfwDMl0sfjYDQDewMhc5ZPqGfLSaQE2oWMmBFfGFNnRyHSMoMmyGB09VBkowjVKSO1xwxW+N6sJTBoiHct7IpbLHZFrDt75s5iV/P+T/PgzI8yE9JOkiCgh3AHw5yH0drUXQVQvaOSIQJ/ZK/4ELcP60TXEWlvrVO8=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Is the VM_guest_metrics class, as described in the Xen Management API V1.0, implemented ?

No I'm afraid its not. To implement it properly would require a agent in each domU to reliably extract details like IP address.

Unless I'm wrong any attempt to invoke a VM_guest_metrics RPC returns [MESSAGE_METHOD_UNKNOWN] and I cannot find any related code in XendAPI.py. Would it be possible to know the subset of the Xen API V1.0 which is supported in the Xen 3.1 release ?

The intention was for the entire API to be implemented, but we didn't make it. All other classes should be fully implemented, but I'm sure theres the odd exception.

Cheers

Tom


Thanks









_______________________________________________
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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.