Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 25 Apr 2014 21:27:18 +0000 (UTC)
From: "Abin Shahab (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12710452.1398381560498.184167.1398461238114@arcas>
In-Reply-To: <JIRA.12710452.1398381560498@arcas>
References: <JIRA.12710452.1398381560498@arcas>
Subject: [jira] [Commented] (YARN-1983) Support heterogeneous container
 types at runtime on YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Abin Shahab commented on YARN-1983:
-----------------------------------

Right, there maybe other, better alternatives. What kinds of extensibility are we supporting here? What kind of containers will YARN be able to support? What kind of configurations would these need?

>From the answers to these questions we can start talking about the abstractions needed to let Yarn launch all kinds of containers.

> 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
>
> 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.2#6252)