[
https://issues.apache.org/jira/browse/MESOS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844719#comment-13844719
]
Ian Downes commented on MESOS-727:
----------------------------------
Of course, I should have provided some details!
Some of the salient points:
* it looks very interesting and there are indeed many similarities in approach
* the programming model is different from Mesos which uses libprocess heavily
* It's marked as beta and in heavy development
* it's not production code but a rewrite from scratch
* currently only cpu and memory isolation supported
* only CL1 (lower level) is being implemented, not yet CL2 (policy layer)
So, although very interesting I thought it was at too early in development to
use and build upon. However, we've been working on refactoring the isolation
component to better support different isolation strategies so users can select
different isolation implementations. As lmctfy matures it should be supported,
probably as an external containerizer.
> Investigate Google's open source container stack for isolation
> --------------------------------------------------------------
>
> Key: MESOS-727
> URL: https://issues.apache.org/jira/browse/MESOS-727
> Project: Mesos
> Issue Type: Task
> Reporter: Ian Downes
> Assignee: Ian Downes
> Priority: Minor
> Labels: twitter
>
> Google recently open sourced some of their low level container stack:
> https://github.com/google/lmctfy
> Discussion on HackerNews:
> https://news.ycombinator.com/item?id=6486991
> There appears to be a lot of similarities in design to what we're working on
> for the new Isolator.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
