hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6447) Provide container sandbox policies for groups
Date Tue, 24 Apr 2018 20:50:08 GMT

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

Hudson commented on YARN-6447:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
YARN-6447. Provide container sandbox policies for groups (gphillips via (xyao: rev e77468840928b236aef71d387923676af3c42956)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/runtime/TestJavaSandboxLinuxContainerRuntime.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/runtime/JavaSandboxLinuxContainerRuntime.java

> Provide container sandbox policies for groups 
> ----------------------------------------------
>                 Key: YARN-6447
>                 URL: https://issues.apache.org/jira/browse/YARN-6447
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, yarn
>    Affects Versions: 3.0.0-alpha4
>            Reporter: Greg Phillips
>            Assignee: Greg Phillips
>            Priority: Minor
>             Fix For: 3.0.0-alpha4
>         Attachments: YARN-6447.001.patch, YARN-6447.002.patch, YARN-6447.003.patch
> Currently the container sandbox feature ([YARN-5280|https://issues.apache.org/jira/browse/YARN-5280])
allows YARN administrators to use one Java Security Manager policy file to limit the permissions
granted to YARN containers.  It would be useful to allow for different policy files to be
used based on groups.
> For example, an administrator may want to ensure standard users who write applications
for the MapReduce or Tez frameworks are not allowed to open arbitrary network connections
within their data processing code.  Users who are designing the ETL pipelines however may
need to open sockets to extract data from external sources.  By assigning these sets of users
to different groups and setting specific policies for each group you can assert fine grained
control over the permissions granted to each Java based container across a YARN cluster.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message