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

Re: [Xen-devel] SLA Monitoring of XEN DomU's

To: echo@xxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, "Xen-Devel (E-mail)" <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] SLA Monitoring of XEN DomU's
From: Ahmad Hassan <ahmad.hassan@xxxxxxxxx>
Date: Mon, 4 Jan 2010 15:11:40 +0000
Cc:
Delivery-date: Mon, 04 Jan 2010 07:12:20 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=S4AJiuI4+NDXwVs+jHq7v857VtMlS4430v7hcBL0s6Y=; b=hshOVcP9phTNswujMhqFA3T/x1WplRLp0p1RNFGS+/b252oAWW5wGJMUgZLVpxy76c O0lHcc2Xw1oQ+2HpkVhZLQmczgV3WUHm7kzxZmI6aNRxPHyurwRony8fH24NMt1iAt78 p+AXXOOSW+elXa/YNkRXPhlCTKJpvwbdzs7nk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=gSHlY0sox9UNkTH3TC6cxhNiHl+9kufOgmnyXwJuCCxaDyZ91n5O5+LZ8IHotG4xjh Og2zjuXkAuhIlXI0ahGWXjeC2K2ixh2SELeEjzaHbvV+D8o4omf/+0xhpMDyDNLSouYE FcQKZUuDBzUdkiI0/wEpdyWjPw+oPyWPRyWMY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1262616866.3408.90.camel@tpost-desktop>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <d47704fc1001040619h4f6442e8g92e449686e357258@xxxxxxxxxxxxxx> <1262616866.3408.90.camel@tpost-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks for the replies. So I can use either use SNMP monitoring using CACTI or http://www.pmacct.net for Network traffic monitoring of DomU's.

What about CPU availability guarantees for DomU's?

By SLA guarantees, I mean to say that Whether I can proof and show to the owner of DomU's that you are getting the exact bandwidth and CPU you asked for.


Best Regards, Hassan
http://cern.ch/ahmadh/portfolio

Erasmus Student
The University of Reading, UK
Aristotle University of Thessaloniki, Greece
The University Of Carlos III, Madrid Spain



2010/1/4 Tim Post <echo@xxxxxxxxxxxx>
On Mon, 2010-01-04 at 14:19 +0000, Ahmad Hassan wrote:
> Dear All,
>
> We have set up a XEN testbed on AMD64 based cluster nodes. I would
> like to know the possible ways to monitor the activities of DomU's
> from Dom0. Is there any transparent way to monitor cpu usage and
> network traffic of DomU's at Dom0 level in order to ensure that SLA
> gurantees to each DomU.
>
> You help is much appreciated.
>
> Thanks.
>
> Regards, Hassan

Network traffic is easily monitored by making sure that you assign
static vifnames to guests. I.e. if your guest is named "vps-123", then
your network config might look like this:

vif = ['bridge = br0, mac = xx:xx:xx:..., vifname = vps-123.0',
      'bridge = br1, mac = xx:xx:xx:..., vifname = vps-123.1' ]

... where vps-123.0 is the device to monitor (on dom-0) for eth0 in that
guest, vps-123.1 the one to monitor for eth1, etc .. etc.

After that, snmp takes care of logging if using something like cacti.

It becomes a little complicated if you tend to migrate guests from node
to node, but not unmanageable.

I'm not quite sure what kind of SLA you are backing with this. I can
produce graphs that tell people they have 100% of all 16 cores in a node
rather easily. Since its impossible for the customer to independently
verify, its hardly usable in a SLA claim. Unless I missed something?

Cheers,
--Tim

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel