On Wed, Jul 20, 2011 at 03:20:30PM -0400, Jason Baron wrote: > However, I think we need to discuss how we envision cgroup configuration > working longer term. The current consumers out of the box, that I'm aware of > are libvirt and systemd. Currently, these consumers manage cgroups as they see > fit. However, since they are managing shared resources, I think there probably > is an argument to be made that its useful, to have some sort of global view > of things, to understand how resources are being allocated, and thus a global > way of configuring cgroups (as opposed to each new consumer doing its own > thing). One thing I should mention is that it is an explicit design goal of libvirt, that the concept of "cgroups" is not exposed to users of the libvirt API. This is because the libvirt goal is to provide an API / XML format that is independent of the specific implementation that a hypervisor uses. Cgroups is an implementation detail of the libvirt KVM & LXC drivers. The libvirt VMWare, Hyper-V, VirtualBox drivers use completely different mechanisms to provide resource controls. Thus the guest resource controls are expressed with a common vocabularly, which is then internally translated to changes in cgroups or some other mechanism as appropriate for the driver. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
