Re: [Xen-users] XCP bandwidth management

[Alexandre Bezroutchko <abb@xxxxxxxxx>]

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