From Fedora Project Wiki

< Features
Revision as of 09:47, 19 February 2009 by Varekova (talk | contribs) (→‎Scope)

ControlGroups

Summary

Control Groups consists of two parts:

  1. an upstream kernel feature that allows system resources to be partitioned/divided up amongst different processes, or a group of processes.
  2. user-space tools which handle kernel control groups mechanism. We want to improve them where necessary and feasible and/or to create new ones e.g. to create or modify cgroups configuration or display control groups data (using libcgroups package).

Owner

  • Linda Wang
    • email: lwang@redhat.com
  • Nils Philippsen
    • email: nphilipp@redhat.com
  • Ivana Varekova
    • email: varekova@redhat.com
  • Jan Šafránek
    • email: jsafrane@redhat.com

Current status

  * Overall CGROUP infrastructure [completed, in Fedora 10]
  * Sub-CGROUP features:
    * CPUSET [completed, in Fedora 10]
    * CPUACCT [completed, in Fedora 10]
    * MEMCTL [completed, in Fedora 10]
    * DEVICE [completed, in Fedora 10]
    * NETWORKING [new, targeted for Fedora 11]
    • tools part
  * man-pages
  * code review
  * spec-file cleanup
  * make file cleanup
  * ps option for cgroups
  * new tools
  • Last updated: 2009-02-19
  • Percentage of completion: 65%

Detailed Description

Kernel Part

Control Groups provide a mechanism for aggregating/partitioning sets of tasks, and all their future children, into hierarchical groups with specialized behaviour.

Definitions:

A *cgroup* associates a set of tasks with a set of parameters for one or more subsystems.

A *subsystem* is a module that makes use of the task grouping facilities provided by cgroups to treat groups of tasks in particular ways. A subsystem is typically a "resource controller" that schedules a resource or applies per-cgroup limits, but it may be anything that wants to act on a group of processes, e.g. a virtualization subsystem.

A *hierarchy* is a set of cgroups arranged in a tree, such that every task in the system is in exactly one of the cgroups in the hierarchy, and a set of subsystems; each subsystem has system-specific state attached to each cgroup in the hierarchy. Each hierarchy has an instance of the cgroup virtual filesystem associated with it.

At any one time there may be multiple active hierachies of task cgroups. Each hierarchy is a partition of all tasks in the system.

User level code may create and destroy cgroups by name in an instance of the cgroup virtual file system, specify and query to which cgroup a task is assigned, and list the task pids assigned to a cgroup. Those creations and assignments only affect the hierarchy associated with that instance of the cgroup file system.

On their own, the only use for cgroups is for simple job tracking. The intention is that other subsystems hook into the generic cgroup support to provide new attributes for cgroups, such as accounting/limiting the resources which processes in a cgroup can access. For example, cpusets (see Documentation/cpusets.txt) allows you to associate a set of CPUs and a set of memory nodes with the tasks in each cgroup.

User space tools

Libcgroups makes that functionality available to programmers and contains two tools, cgexec and cgclassify, to start processes in a control group or move existing processes from one control group to another. In Fedora libcgroups package is already incorporated, but the overall quality is very poor. There is almost no documentation, no man pages, no configuration file samples, there should be done code review and created other necessary tools and improve installations:

The goal for Fedora 11 is to improve this package where necessary, i.e.:

  • bugfixing
  • add/fix documentation and man-pages
  • add examples
  • fix error handling
  • rework logging
  • create displaying tool (to see, in which control group is given process)
  • prepare a way, how to start a service daemon in given context group

The long term goal is to create new tools to e.g. create or modify persistent cgroups configuration and display control groups data. At the beginning the focus will be on command line tools, but we'll keep in mind that in the long term we'll likely want to have graphical tools. These would offer similar functionality and we should try to make sure that any non-UI code written is usable from both kinds of frontends.

Benefit to Fedora

The implementation of of "control groups" schema and its improvement should enable users to partitioned/divided resources up amongst different processes, or a group of processes. Libcgroups should helps them to create persistent configuration of partitioning devices and handle cgroups from user point of view. This project should help the user to make the best of control groups kernel feature.


Scope

Kernel Part

There are several sub-features under control group:

  • CGROUPS (grouping infrastructure mechanism)
 CGROUPS=y
  • CPUSET (cpuset controller, in F10)
 CPUSET=y
  • CPUACCT (cpu account controller, in F10)
 CGROUP_CPUACCT=y
  • SCHED (schedule controller, in F10)
 CGROUP_SCHED=y
  • MEMCTL (memory controller, in F10)
 RESOURCE_COUNTERS=y
 CGROUP_MEM_CONT=y
 (CGROUP_MEM_RES_CTLR???)
  • DEVICE
 CGROUP_DEVICE=y
  • NETCTL (network controller, New)
 NET_CLS_CGROUP=y

tools part

Required extended testing and fixing of libcgroups package and in time when libcgroups will be stable enough try to add start to write another parts - based on existing ones.

How To Test

For now it is necessary to have a kernel with cgroups support (Documentation/cgroups/cgroups.txt) and the libcgroup package. The user/tester must know, what cgroups are and what they are good for, the best is to read aforementioned kernel doc. 

1. yum install libcgroup


  • Creating cgroups:
  1. Configure /etc/cgconfig.conf file - there should be nice example and man page packaged.
  2. Start/stop cgconfig service and test whether the created groups are as expected.


  • Moving task to groups:
  1. Prepare some cgroups, i.e. prepare /etc/cgconfig.conf and start cgconfig service.
  2. Start/stop new proces using cgexec and check that it's in appropriate cgroup.
  3. Prepare cgrules.conf file - there should be some sample and man page available.
  4. Test cgrulesengd daemon (it should automatically move processes as written in cgrules.conf).
  5. Configure cgroup pam module and test that works if a user logs in (again, driven by cgrules.conf).

User Experience

Currently, the libcgroups package has several bugs, these will have to be fixed at first. When that is out of the way, configuration (or even monitoring) tools would reduce the barrier of entry to using control groups on Linux significantly.

Dependencies

  • Depends on kernel > 2.6.24 and libcgroups (current version is 0.32.2) which both are in Fedora since F-9.

Contingency Plan

Currently, nothing depends on libcgroup or the tools which would use it. If things go really wrong, we can always go back to the last working version of libcgroup.

Documentation

Release Notes

libcgroups is a tool which helps to manipulate, control and administrate control groups and the associated controllers. Using this tool it is possible to aggregate/partition set of tasks and their future children into hierarchical groups with specialized access to resources.

The tool consists of two parts -

  • The first one enables user to create persistent cgroups configuration using a configuration file and a service which creates configured groups on startup.
  • The second part enables user to define to which group belong the given process/given processes. This divison is based on uid or gid of processes. The user can start a service which will put the processes to the right subsystem, or there is a tool to move the process to the right subsystem or to create the process in it.

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/ControlGroups&oldid=79793"