hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Egan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6444) Support additional security group option in hadoop-ec2 script
Date Tue, 22 Dec 2009 04:30:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Paul Egan updated HADOOP-6444:

    Status: Patch Available  (was: Open)

No tests provided because an ec2 account with existing security groups would be required.

Tested manually by running the hadoop-ec2 command with the new {{--security-group}} option
and verified that the cluster nodes have been added to the specified group.

> 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: Paul Egan
>            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

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

View raw message