[
https://issues.apache.org/jira/browse/MESOS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059155#comment-14059155
]
Jay Buffington commented on MESOS-1527:
---------------------------------------
I think the move from calling the command line flag --containerizers rather
than --isolation is good, but since --isolation was released in 0.19 we should
consider going through a deprecation cycle with it. It looks like --isolation
is no longer needed, so it could just be used as an alias for --containerizers
for a couple of releases.
Actually, --containerizers is really just "enabled" containerizers. This
makes sense for the existing three: mesos, external and docker. If you want to
use docker or external you're going to have to change system configuration
(start docker or the external containerizer), so right now explicit is better
than implicit.
> 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)
