Sounds like a good idea. Feel free to open a JIRA issue for this improvement.

Cheers,

-- Andrei Savu / andreisavu.ro

On Mon, Jul 11, 2011 at 8:50 AM, Jim R. Wilson <wilson.ji...@gmail.com> wrote:
> It has been helpful to me to edit ~/.whirr/clustername/<service>-proxy.sh
> and remove the -N and -D options.  This gives you the same shell the proxy
> uses.
> Along those lines, it would be nice if there was another script created in
> the same directory that just does this.
> -- Jim R. Wilson (jimbojw)
>
> On Mon, Jul 11, 2011 at 11:14 AM, Sebastian Schoenherr
> <sebastian.schoenh...@uibk.ac.at> wrote:
>>
>> Hi Tom,
>> yep, that works!
>> Sebastian
>>
>> On 11.07.2011 17:05, Tom White wrote:
>>>
>>> Are you able to log in using the user you launched with? That is, ssh
>>> -i<key>  <host>.
>>>
>>> Tom
>>>
>>> On Mon, Jul 11, 2011 at 3:28 PM, Sebastian Schoenherr
>>> <sebastian.schoenh...@uibk.ac.at>  wrote:
>>>>
>>>> Hi guys,
>>>> I launched the newest 32 bit Amazon AMI  (ami-8c1fece5) with WHIRR 0.5.0
>>>> and
>>>> got no errors during the setup.
>>>> Unfortunately, I'm not able to login with the standard ec2-user (ssh -i
>>>> <key>    ec2-user@<...>). I tried it with an ubuntu image and everything
>>>> worked fine.
>>>> Any guesses? Thanks a lot.
>>>> Cheers, Sebastian
>>>>
>>>> whirr.cluster-name= newCluster
>>>> whirr.provider=aws-ec2
>>>> whirr.image-id=us-east-1/ami-8c1fece5
>>>> whirr.hardware-id=m1.small
>>>> whirr.private-key-file=${sys:user.home}/.ssh/id_rsa
>>>> whirr.public-key-file=${sys:user.home}/.ssh/id_rsa.pub
>>>> whirr.hadoop-install-function=install_cdh_hadoop
>>>> whirr.hadoop-configure-function=configure_cdh_hadoop
>>>> whirr.identity=...
>>>> whirr.credential=...
>>>> whirr.instance-templates=1 hadoop-jobtracker+hadoop-namenode,1
>>>> hadoop-datanode+hadoop-tasktracker
>>>>
>>>>
>>>>
>>>>
>>
>
>

Reply via email to