[
https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057946#comment-16057946
]
Joseph Wu commented on MESOS-7302:
----------------------------------
For the MVP, containers launched via the (to be implemented) standalone
container API will be isolated like any other container. But the Master will
not know about them. So if you abuse the Operator API, it would be possible to
oversubscribe the Agent.
I'd need to add some additional plumbing from the Agent to the Master's
allocator in order to properly account for these resources (albeit racily, as
standalone containers are launched outside of the offer cycle).
> 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.4.14#64029)
