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] Fwd: Getting VM stats

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-API] Fwd: Getting VM stats
From: jdsw <jdsw2002@xxxxxxxxx>
Date: Tue, 19 Dec 2006 11:08:42 -0800 (PST)
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 19 Dec 2006 11:08:32 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=MGI+Rc81HXKw/c445hfDzDk0/IgBNK17JeI/JK9F9FOXDRbmWwrV3T6VAM8VaD/6Z520B7qR+deX9PIfNvmPxqoOES/rzlAxhDyAmqUSx9UB1VNQPWRAafzAN7l7cOQv8MlXkWRgblYb/h64j53ANao6onTGmVqzOBVHPrPNWv0=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061219180443.GK7929@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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
I understand that mechanism for collecting data might be different and specific. But the transport and API to get that information can be standardised. For example, a way to push some structured data on xenbus and make it accessible  through Xend api.

Also, I am not sure, if the email that I fwd got other questions about, how to get certain basic metrics through Xend instead of using combination of Xend API, Memory Maps, parsing files for VBD and n/w information.
/Jd

"Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:
On Tue, Dec 19, 2006 at 09:54:10AM -0800, jdsw wrote:
> Do you guys have any suggestion ?
> (I did not get satisfactory answers to each of the questions on dev forum)
>
> In addition is there a plan for a streamlined access to things happening
> in Domu information through Dom0. For example: Top process information in a
> DomU available through Dom0 ?

The Xen-API work is really about management of Dom0 and DomU VMs as opaque
entities viewed from Dom0. Collecting OS specific details about work going on
inside the DomU (eg processes running, detailed breakdown of CPU & memory
usage) is best handled by a dedicated monitoring API. It has very different
requirements of that of Xen-API, in particular from a performance / overhead
POV. There are a wide variety of existing OS monitoring tools which can be
deployed inside DomUs, Big-Sister, Nagios, Ganglia, to name but three such
tools.

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

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

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