[
https://issues.apache.org/jira/browse/MESOS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060318#comment-14060318
]
Benjamin Hindman commented on MESOS-1527:
-----------------------------------------
The --isolation flag is still useful for the MesosContainerizer as it is used
to distinguish the kinds of isolators that should get created. For example:
$ mesos-slave --master=ip:port --containerizers=docker,mesos
--isolation=cgroups/cpu,cgroups/mem
This creates two containerizers, a DockerContainerizer and MesosContainerizer
and the MesosContainerizer uses the cgroups CPU isolator and cgroups memory
isolator. Without the --isolation flag, the MesosContainerizer does not use
cgroups by default.
It is true that --isolation=external worked in the past and no longer works now
and I agree that it would be better to put that through a deprecation cycle so
I created MESOS-1580 for someone to take on (albeit, on top of the feature
branch until we merge it with master).
> Choose containerizer at runtime
> -------------------------------
>
> Key: MESOS-1527
> URL: https://issues.apache.org/jira/browse/MESOS-1527
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Jay Buffington
>
> Currently you have to choose the containerizer at mesos-slave start time via
> the --isolation option. I'd like to be able to specify the containerizer in
> the request to launch the job. This could be specified by a new "Provider"
> field in the ContainerInfo proto buf.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
