[
https://issues.apache.org/jira/browse/YARN-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307247#comment-14307247
]
Chun Chen commented on YARN-1983:
---------------------------------
Thanks for the comments, [~vinodkv] [~chris.douglas].
Do you mean we can simply use NM_DOCKER_CONTAINER_EXECUTOR_IMAGE_NAME env to
identify container types? IMHO, users can implement a custom
${yarn.nodemanager.container-executor.class} for their own scenarios currently,
what if they want to use both LinuxCE and their owner CE at runtime? I think
NM_DOCKER_CONTAINER_EXECUTOR_IMAGE_NAME is not enough to distinguish these
different container types.
Besides, based on my proposal, if users don't want to use DockerCE, they don't
need to change any configuration.
I think my current patch is intrusive indeed but more general, right?
> Support heterogeneous container types at runtime on YARN
> --------------------------------------------------------
>
> Key: YARN-1983
> URL: https://issues.apache.org/jira/browse/YARN-1983
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Junping Du
> Attachments: YARN-1983.2.patch, YARN-1983.patch
>
>
> Different container types (default, LXC, docker, VM box, etc.) have different
> semantics on isolation of security, namespace/env, performance, etc.
> Per discussions in YARN-1964, we have some good thoughts on supporting
> different types of containers running on YARN and specified by application at
> runtime which largely enhance YARN's flexibility to meet heterogenous app's
> requirement on isolation at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
