You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Paul Egan (JIRA)" <ji...@apache.org> on 2009/12/16 05:50:18 UTC
[jira] Created: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
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
Priority: Minor
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.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Paul Egan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Egan updated HADOOP-6444:
------------------------------
Attachment: hadoop-trunk-contrib-cloud.patch
Updated patch to latest trunk and corrected paths
> 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, 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.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Paul Egan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Egan updated HADOOP-6444:
------------------------------
Attachment: hadoop-ec2-py-0.3.0.patch
Patch against [cloudera-for-hadoop-on-ec2-py-0.3.0-beta.tar.gz|http://cloudera-packages.s3.amazonaws.com/cloudera-for-hadoop-on-ec2-py-0.3.0-beta.tar.gz] adding a {{security-group}} option.
> 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
> Priority: Minor
> Attachments: hadoop-ec2-py-0.3.0.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.
[jira] Commented: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791511#action_12791511 ]
Tom White commented on HADOOP-6444:
-----------------------------------
Security groups are an EC2-only feature so it would be good to document that in the option help (just like --key-name, for example). Otherwise, this looks good.
> 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
> Priority: Minor
> Attachments: hadoop-ec2-py-0.3.0.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.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6444:
------------------------------
Resolution: Fixed
Fix Version/s: 0.22.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I've just committed this. Thanks Paul!
> 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
> Fix For: 0.22.0
>
> Attachments: hadoop-ec2-py-0.3.0.patch, hadoop-trunk-contrib-cloud.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.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Paul Egan (JIRA)" <ji...@apache.org>.
[ 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, 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.
[jira] Commented: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794010#action_12794010 ]
Hudson commented on HADOOP-6444:
--------------------------------
Integrated in Hadoop-Common-trunk #196 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/196/])
. Support additional security group option in hadoop-ec2 script. Contributed by Paul Egan.
> 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/cloud
> Reporter: Paul Egan
> Assignee: Paul Egan
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: hadoop-ec2-py-0.3.0.patch, hadoop-trunk-contrib-cloud.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.
[jira] Commented: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793706#action_12793706 ]
Hudson commented on HADOOP-6444:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #123 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/123/])
. Support additional security group option in hadoop-ec2 script. Contributed by Paul Egan.
> 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
> Fix For: 0.22.0
>
> Attachments: hadoop-ec2-py-0.3.0.patch, hadoop-trunk-contrib-cloud.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.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Paul Egan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Egan updated HADOOP-6444:
------------------------------
Attachment: hadoop-trunk-contrib-cloud.patch
Updated help text for {{--security-group}} option.
> 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 launch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White reassigned HADOOP-6444:
---------------------------------
Assignee: Paul Egan
> 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
>
>
> 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.
[jira] Commented: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793499#action_12793499 ]
Hadoop QA commented on HADOOP-6444:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12428692/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 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/230/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/230/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/230/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/230/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: Paul Egan
> Priority: Minor
> Attachments: hadoop-ec2-py-0.3.0.patch, hadoop-trunk-contrib-cloud.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.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Paul Egan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Egan updated HADOOP-6444:
------------------------------
Assignee: Tom White (was: Paul Egan)
Status: Patch Available (was: Open)
Updated patch as requested
> 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.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6444:
------------------------------
Assignee: Paul Egan (was: Tom White)
Status: Open (was: Patch Available)
Paul, thanks for the updated patch. Hudson can't apply it since it needs to be relative to Hadoop Common's root - i.e. paths starting with "src/contrib/cloud/src/py/hadoop/..." Could you regenerate it please? (BTW you can leave this issue assigned to yourself since you are working on it.)
> 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 launch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
Posted by "Paul Egan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Egan updated HADOOP-6444:
------------------------------
Attachment: hadoop-trunk-contrib-cloud.patch
Patch against [contrib/cloud|http://svn.apache.org/repos/asf/hadoop/common/trunk/src/contrib/cloud] adding a {{security-group}} option.
> 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
> Priority: Minor
> Attachments: hadoop-ec2-py-0.3.0.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.