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-users] Dom U bandwidth monitoring - pmacct, bandwidthd?

To: "matt@xxxxxxxxxxxxxxxxxx" <matt@xxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Dom U bandwidth monitoring - pmacct, bandwidthd?
From: "Robbie A. Garrett" <RGarrett@xxxxxxxxxxxxxx>
Date: Fri, 12 Feb 2010 12:27:45 -0500
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 12 Feb 2010 09:28:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5aa2646afc8a5c87a9a704f90fa0df52.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <8344e7c272fa0554d38d0981d74bd478.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f1002120811n64732b78vb04d934301d039cc@xxxxxxxxxxxxxx>, <21a1800c1002120815u3f90fe78v9bd11160c5fcaa62@xxxxxxxxxxxxxx> <29D1DB7C-D596-4535-A091-B1582694464E@mimectl>, <5aa2646afc8a5c87a9a704f90fa0df52.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqsB32VTzyS//ExSiC4W4uOU2RO9AAAFVkUAAA3Zpw=
Thread-topic: [Xen-users] Dom U bandwidth monitoring - pmacct, bandwidthd?
How would the switch know that traffic is for DomU or internet?
 
this would have to be on a presence router / switch and track by ip address which I think is a bad idea.
What I would suggest is that you allow there vm's to be able to use there own private network to move the data from one vm to another.  A lot of houses do it like this so they can let the customers who setup there vm's in a cluster have there cluster traffic bandwidth free.
 

From: Matthew Law [matt@xxxxxxxxxxxxxxxxxx]
Sent: Friday, February 12, 2010 12:20 PM
To: Robbie A. Garrett
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Dom U bandwidth monitoring - pmacct, bandwidthd?


On Fri, February 12, 2010 4:48 pm, Robbie A. Garrett wrote:
> My Company developed a method via mrtg.  Each vm has a vif name that means
> something within our tracking system.
>
> an example of this would be user32.  On the Xen server, they have a vm
> called user32 and within the config file of the VM, there vif name is
> user32.  We set there MRTG files to pull data based on 'network card name'
> (in this case user32), and use rrd tool to store the information.   This
> makes it very easy to pull all historical data from vm's.  When ever a vm
> moves, so does it's .rrd file  thus keeping all bandwidth traffic
> together.
>
> This may not solve your issue or question...  but I would try barking up
> the mrtg tree to collect bandwidth totals.

I have unique vif names for each domU already (its against a unique ID in
a database table which maps back to the customer).  Only problem with
taking stats from the dom0 is that I wouldn't like to penalise people for
transferring data between their domUs on different hosts.  We get charged
for uplinked data transfer only.  Its starting to look like I might have
to do this at the switches...

Thanks,

Matt.

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