[
https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu updated MESOS-7302:
-----------------------------
Description: 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. (was: 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.)
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
