custom EBS-backed AMIs

[Norbert Burger <no...@gmail.com>]

Re-sending; accidentally posted this under a different thread.

Hi all -- I'm trying to launch an HBase cluster with a custom AMI
(EBS-backed root volume) and I'm running into the same stack trace
I've seen earlier on this list (an SSH exception when trying to
contact the master [1]).  Looking through the archives, it doesn't
seem like anyone had luck getting past this point.  Any
suggestions/thoughts?  My properties file is also attached [2].

Alternatively, can anyone recommend an existing EBS-backed AMI that
works with whirr Java?  I understand the configurable EBS volumes are
still being worked on; here, I was just hoping to get an EBS-backed
root volume.

Norbert

[1]

tts-unixudp05516758uds:ec2 nburger$ whirr launch-cluster --config
cvps.properties
Bootstrapping cluster
Configuring template
Starting 1 node(s) with roles [hadoop-datanode, hadoop-tasktracker,
hbase-regionserver]
Configuring template
Starting 1 node(s) with roles [zookeeper, hadoop-namenode,
hadoop-jobtracker, hbase-master]
<< problem applying options to node(us-east-1/i-a84f35c7):
org.jclouds.ssh.SshException: ec2-user@184.73.147.242:22: Error
connecting to session.
       at org.jclouds.ssh.jsch.JschSshClient.propagate(JschSshClient.java:252)
       at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:206)
       at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:90)
       at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:140)
       at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:56)
       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
       at java.util.concurrent.FutureTask.run(FutureTask.java:138)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
       at java.lang.Thread.run(Thread.java:680)
Caused by: com.jcraft.jsch.JSchException: Auth fail
       at com.jcraft.jsch.Session.connect(Session.java:461)
       at com.jcraft.jsch.Session.connect(Session.java:154)
       at org.jclouds.ssh.jsch.JschSshClient.newSession(JschSshClient.java:247)
       at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:186)
       ... 8 more

[2]

whirr.cluster-name=cvps
whirr.instance-templates=1
zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,1
hadoop-datanode+hadoop-tasktracker+hbase-regionserver
whirr.hadoop-install-function=install_cdh_hadoop
whirr.hadoop-configure-function=configure_cdh_hadoop
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
whirr.hardware-id=m1.large
whirr.image-id=us-east-1/ami-1ce71b75
jclouds.ec2.ami-owners=130611044146
whirr.location-id=us-east-1
whirr.login-user=ec2-user
whirr.private-key-file=cvps-ssh
whirr.public-key-file=cvps-ssh.pub

---------- Forwarded message ----------
From: Norbert Burger <no...@gmail.com>
Date: Mon, Apr 18, 2011 at 3:00 PM
Subject: Re: image-id to specify a m1.large hardware in EC2
To: whirr-user@incubator.apache.org