On Sunday 30 Jun 2013 01:01:18 Linda Walsh wrote:
You should probably read this mail about upcoming kernel and systemd changes with respect to cgroups, suffice it to say that there's going to be some significant changes so you may not want to rely too heavily on cgroup API's that might change in the not too distant future.
---- Um... *ouch*?
http://lists.freedesktop.org/archives/systemd-devel/2013-June/011521.html
--- I don't get it. I use the cgroups in /sys/fs/cgroup/.
Currently my only usage is in the net_prio group to set default network priorities for a group or type of service (naming services, timekeeping, mail...etc).
The only interface I'm aware of has been the one in /sys.
They said something about there only being one hierarchy and it being owned by systemd. That sounds like it would interfere with setting anything up like I have already setup. What does it mean to own a hierarchy??
Are they removing the cgroup interface in /sys?
I don't think so, just making the default/root hierarchy managed by systemd. By the description it sounds like there will be just a few less knobs to worry about and no opportunity to accidentally clobber cgroup settings. Personally I find the following the most interesting part of the whole email: "More specifically: libcgroup is out of the game with this. libvirt/openshift/lxc/.. can continue to do what they do for now, however they should be updated sooner rather than later to do things the systemd way, i.e. rely on systemd VM/container registration and user cgroup management." I think if I was deploying KVM and containers on an upstart system I'd probably be a little bit apprehensive right now. Cheers the noo, Graham -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org