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] XCP bandwidth management

To: Peter Phaal <peter.phaal@xxxxxxxxx>
Subject: Re: [Xen-users] XCP bandwidth management
From: Alexandre Bezroutchko <abb@xxxxxxxxx>
Date: Sun, 05 Jun 2011 21:24:35 +0200
Cc: "msgbox450@xxxxxxxxx" <msgbox450@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 05 Jun 2011 12:25:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTikLbgZV4zoCbPu3nm55wSMvYDj7pw@xxxxxxxxxxxxxx>
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: <4dd95da0.0427650a.7e16.4699SMTPIN_ADDED@xxxxxxxxxxxxx> <4DD97482.80400@xxxxxxxxx> <BANLkTing8s=OErpx_bT13Eyu5BS-jDFB-g@xxxxxxxxxxxxxx> <4DDA4BA5.8040408@xxxxxxxxx> <BANLkTikLbgZV4zoCbPu3nm55wSMvYDj7pw@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
Perhaps you have misunderstood what I have said. I was suggesting to install sFlow _collector_ in domU, not agents.

Thanks for the references to sFlow resource management. I'm looking forward to see this approach to become usable in practice.

Regards,
Alex

On 06/05/2011 08:30 PM, Peter Phaal wrote:
On Mon, May 23, 2011 at 4:57 AM, Alexandre Bezroutchko<abb@xxxxxxxxx>  wrote:
Another aspect of problem #3 is how to transfer the policy from sFlow domU
to dom0. I would do it by publishing desired policy on sFlow domU. It can be
a simple as putting a plain text file on HTTP server, or maybe having LDAP
server on sFlow domU, if it is justified. Then a cron job in dom0 would poll
the desired policy from sFlow domU and reconfigure vswitch accordingly.
Alternatively, one can push the config from sFlow domU into dom0 over native
vSwitch API, but I feel it is less preferable from security point of view. I
would prefer to keep my dom0 shut, even from trusted systems I own.
The sFlow instrumentation is in dom0 (it's part of the the Open
vSwitch). Traffic to every virtual machine is visible from dom0 so
there is no need to install sFlow agents in the virtual machines. The
quota controller should be on the management network so it can receive
sFlow from dom0 and implement vSwitch configuration changes in dom0.
To maintain security, entire system should be part of the control
plane and avoid direct interactions with the domUs that are being
managed.

It might also be interesting to look at managing domU CPU quotas as
well as bandwidth quotas:
http://blog.sflow.com/2011/06/resource-allocation.html

sFlow can be installed in the domUs, but this is only necessary if you
are operating in a public cloud where you don't have access to dom0:
http://blog.sflow.com/2010/12/visibility-in-cloud.html
http://blog.sflow.com/2011/01/rackspace-cloudservers.html

As a cloud customer the controls would be a bit different, you might
use the data to decide how many VMs to run etc.

Cheers,
Peter


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

<Prev in Thread] Current Thread [Next in Thread>