[ 
https://issues.apache.org/jira/browse/YARN-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588954#comment-14588954
 ] 

Sidharta Seethana commented on YARN-1983:
-----------------------------------------

Hi [~chenchun]

[~ashahab] and I have been thinking on how best to take ‘container type’ 
support forward in a way that leverages existing functionality ( e.g 
security/resource isolation ) in a given executor (e.g LinuxContainerExecutor) 
and yet provide flexibility to let users pick different container types ( e.g 
Docker v/s non-Docker ). To this end, we came up with the notion of container 
runtimes that can be used within the same executor. Given this, I feel that we 
no longer need to go down the path of 'composite executors'. Please see the 
following for more information :

* YARN-3611 which describes Docker support in LinuxContainerExecutor
* Our presentation/demo at the recent hadoop summit at how this functionality 
can be used : https://prezi.com/2mxvb0n_q1rt/yarn-and-the-docker-ecosystem/

We have been working on patches to enable this functionality and we expect to 
submit these for review soon (within the next week).  

thanks,
-Sidharta 

> 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)

Reply via email to