You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2012/07/20 22:58:35 UTC
[jira] [Commented] (MESOS-207) A new isolation module on Linux that
uses Linux control groups (cgroups) directly.
[ https://issues.apache.org/jira/browse/MESOS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419563#comment-13419563 ]
Jie Yu commented on MESOS-207:
------------------------------
Here is the list of the reviews related to this new feature.
1) Basic APIs to control Linux control groups (cgroups).
https://reviews.apache.org/r/5394/
2) Add an API in process::io to do non-blocking read.
https://reviews.apache.org/r/5576/
3) Add event notification handler mechanism in cgroups (based on (1) and (2)).
https://reviews.apache.org/r/5395/
4) Add APIs to use the cgroups freezer subsystem.
https://reviews.apache.org/r/5401/
5) Add API to atomically kill all tasks in a cgroup (based on (4)).
https://reviews.apache.org/r/5402/
6) Add API to destroy a cgroup and all its sub-cgroups (based on (5)).
https://reviews.apache.org/r/5840/
7) Add cgroups isolation module in slave.
https://reviews.apache.org/r/5509/
> A new isolation module on Linux that uses Linux control groups (cgroups) directly.
> ----------------------------------------------------------------------------------
>
> Key: MESOS-207
> URL: https://issues.apache.org/jira/browse/MESOS-207
> Project: Mesos
> Issue Type: New Feature
> Components: isolation
> Environment: Linux 2.6.27 or later.
> Reporter: Jie Yu
> Labels: cgroups
> Original Estimate: 360h
> Remaining Estimate: 360h
>
> A new isolation module on Linux platforms that uses Linux control groups (cgroups) directly. This is intended to replace the LXC isolation module. The initial goal is to provide memory and cpu isolation. Future goals include disk i/o isolation, network isolation, and file system isolation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira