Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <987859490.1261367418693.JavaMail.jira@brutus>
Date: Mon, 21 Dec 2009 03:50:18 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6444) Support additional security group
 option in hadoop-ec2 script
In-Reply-To: <923480243.1260939018250.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793071#action_12793071 ] 

Hadoop QA commented on HADOOP-6444:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12428594/hadoop-trunk-contrib-cloud.patch
  against trunk revision 892113.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/227/console

This message is automatically generated.

> Support additional security group option in hadoop-ec2 script
> -------------------------------------------------------------
>
>                 Key: HADOOP-6444
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6444
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: contrib/ec2
>            Reporter: Paul Egan
>            Assignee: Tom White
>            Priority: Minor
>         Attachments: hadoop-ec2-py-0.3.0.patch, hadoop-trunk-contrib-cloud.patch, hadoop-trunk-contrib-cloud.patch
>
>
> When deploying a hadoop cluster on ec2 alongside other services it is very useful to be able to specify additional (pre-existing) security groups to facilitate access control.  For example one could use this feature to add a cluster to a generic "hadoop" group, which authorizes hdfs access from instances outside the cluster.  Without such an option the access control for the security groups created by the script need to manually updated after cluster launch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.