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

["Avinash Sridharan (JIRA)" <ji...@apache.org>]

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

Avinash Sridharan commented on MESOS-7302:
------------------------------------------

[~jieyu]
How would the standalone containers report task updates to the agent? They would still need to have the default/command executor semantics to monitor the container right?

Just a thought, in order to launch stand alone containers why can we make the agent act as a first class framework that can launch containers directly on the agent?

> 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
>
> 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)