[
https://issues.apache.org/jira/browse/WHIRR-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer updated WHIRR-63:
------------------------------
Attachment: WHIRR-63.patch
This is a preliminary patch - it depends on Whirr going to jclouds 1.5, and
jclouds 1.5 itself fixing
http://code.google.com/p/jclouds/issues/detail?id=1024 (which may be done
shortly anyway), but with those in place, it works. If you specify
whirr.hardware-id=cc1.4xlarge and a valid HVM AMI (which admittedly is a bit
hairy at the moment - there's a Precise HVM AMI, but no Lucid HVM AMI), it'll
automatically create a placement group and put all the nodes from the created
cluster in it. And if you specify whirr.aws-ec2-placement-group=foo, it'll look
for an existing placement group named "foo" and put the nodes in that.
> Support EC2 Cluster Compute Groups for Hadoop
> ---------------------------------------------
>
> Key: WHIRR-63
> URL: https://issues.apache.org/jira/browse/WHIRR-63
> Project: Whirr
> Issue Type: New Feature
> Components: service/hadoop
> Reporter: Tom White
> Fix For: 0.9.0
>
> Attachments: WHIRR-63.patch
>
>
> We should support the new EC2 cluster compute groups which have high
> bandwidth between nodes in the cluster. See
> http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?using_cluster_computing.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
