[jira] [Comment Edited] (MESOS-7302) Support launching standalone containers.

["Adam B (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968959#comment-15968959 ] 

Adam B edited comment on MESOS-7302 at 4/14/17 12:27 PM:
---------------------------------------------------------

[~kaysoky], are you planning to do any work on this in the next sprint? If so, please find/create the JIRA(s) under this Epic, estimate them, and add them to the sprint.


was (Author: adam-mesos):
[~kaysoky], are you planning to do any work in in the next sprint? If so, please find/create the JIRA(s) under this Epic, estimate them, and add them to the sprint.

> Support launching standalone containers.
> ----------------------------------------
>
>                 Key: MESOS-7302
>                 URL: https://issues.apache.org/jira/browse/MESOS-7302
>             Project: Mesos
>          Issue Type: Epic
>          Components: containerization
>            Reporter: Jie Yu
>            Assignee: Joseph Wu
>              Labels: mesosphere
>
> Containerizer should support launching containers (both top level and nested) that are not tied to a particular Mesos task or executor. This is for the case where the agent wants to launch some system containers (e.g., for CSI plugin) that will be managed by Mesos.
> More specifically, the Containerizer interfaces should be refactored so that they do not depend on TaskInfo or ExecutorInfo. Currently, the `launch` interface depends on them. Instead, we should consistently use ContainerInfo and CommandInfo in Containerizer and isolators.
> This is also one necessary step towards running MesosContainerizer in standalone mode.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)