[
https://issues.apache.org/jira/browse/MESOS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056909#comment-14056909
]
Benjamin Hindman commented on MESOS-1527:
-----------------------------------------
Here are two commits on the path towards running multiple containerizers
simultaneously.
https://github.com/mesos/mesos/commit/8db82562f63b564b83816f46712fb3b9f1755eb0
This first commit updates 'Containerizer::launch' to return a 'bool', which
distinguishes whether or not that containerizer could launch the container.
Returning 'true' implies it launched the container, returning 'false' implies
it could not.
https://github.com/mesos/mesos/commit/c318df59e24153b2a917dec67d8c2340fc1830d2
This second commit introduces a Containerizer implementation that is made up of
multiple containerizers, determined on the command line by seting the
--containerizers=foo,bar,baz flag. At runtime all Containerizer's will be
created and each will be called (in the order specified in the --containerizers
flag) to launch the container until one returns 'true' from
Containerizer::launch (see commit above). So, for example, one could do:
--containerizers=external,mesos which will attempt to launch with the external
containerizer first followed by the Mesos containerizer. The plan is to be able
to do something like: --containerizers=docker,mesos which will try the
DockerContainerizer followed by the MesosContainerizer.
> 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)
