hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1964) Support Docker containers in YARN
Date Thu, 24 Apr 2014 21:51:26 GMT

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

Wangda Tan commented on YARN-1964:

[~djp], as you mentioned,
bq. The interesting thing is when resource scheduler try to schedule RR to nodes, it should
not only consider location of resource request but also the container types supported NM (assume
a heterogenous env in possible).
We can use YARN-796 descirbe container types supported by NM, that will not need change ApplicationMasterProtocol
for supporting different containers. More generically, I think we can add a configuration
(org.apache.hadoop.conf.Configuration) to container launch request, and it will be consumed
by CE.launchContainer call. Which IMO can get more extensibility for users add more container
specific parameters to launch container. Any thoughts?

> Support Docker containers in YARN
> ---------------------------------
>                 Key: YARN-1964
>                 URL: https://issues.apache.org/jira/browse/YARN-1964
>             Project: Hadoop YARN
>          Issue Type: New Feature
>    Affects Versions: 2.2.0
>            Reporter: Arun C Murthy
>            Assignee: Abin Shahab
>         Attachments: yarn-1964-branch-2.2.0-docker.patch
> Docker (https://www.docker.io/) is, increasingly, a very popular container technology.
> In context of YARN, the support for Docker will provide a very elegant solution to allow
applications to *package* their software into a Docker container (entire Linux file system
incl. custom versions of perl, python etc.) and use it as a blueprint to launch all their
YARN containers with requisite software environment. This provides both consistency (all YARN
containers will have the same software environment) and isolation (no interference with whatever
is installed on the physical machine).

This message was sent by Atlassian JIRA

View raw message