[
https://issues.apache.org/jira/browse/WHIRR-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153742#comment-13153742
]
Andrei Savu commented on WHIRR-63:
----------------------------------
An AMI that can be used for cluster compute instances in jclouds should match
the following queries:
See
providers/aws-ec2/src/main/java/org/jclouds/aws/ec2/AWSEC2PropertiesBuilder.java
{code}
// amazon, alestic, canonical, and rightscale
properties.setProperty(PROPERTY_EC2_AMI_QUERY,
"owner-id=137112412989,063491364108,099720109477,411009282317;state=available;image-type=machine");
// amis that work with the cluster instances
properties.setProperty(PROPERTY_EC2_CC_REGIONS, Region.US_EAST_1);
properties
.setProperty(
PROPERTY_EC2_CC_AMI_QUERY,
"virtualization-type=hvm;architecture=x86_64;owner-id=137112412989,099720109477;hypervisor=xen;state=available;image-type=machine;root-device-type=ebs");
{code}
I suggest you try with a 64bit AMI provided either by Amazon or Canonical.
> 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.8.0
>
>
> 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
