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] Xen Management API draft

To: "Jim Fehlig" <jfehlig@xxxxxxxxxx>, "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
Subject: RE: [Xen-API] Xen Management API draft
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sat, 24 Jun 2006 09:24:40 +0100
Cc: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 24 Jun 2006 15:42:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaXH5VEm8o1nQ0qSa6wceayly6ChQARzOYg
Thread-topic: [Xen-API] Xen Management API draft
> Is it realistic to use XML-RPC for tasks such as resource monitoring?
> Seems like there should be an optional, lower-latency, lighter-weight
> mechanism to retrieve things such as host_cpu.utilisation,
> VBD.IO_bandwidth/incoming_kbs, etc.  

The whole stats reporting interface certainly needs more thought.

However, I think it definitely should still use the xml-rpc interface,
we just need to 'cook' the raw data into something more directly useful
within xend so that there's no need to do high-rate polling on the API.
This might involve using something like rrdtool to generate averages
over different time scales etc.


xen-api mailing list