[Starcluster] instance ssh problem...

[Justin Riley]

Hi Nicholas,

Sorry for the late response on this. What version of Eucalyptus are you using? 
I just created an EMI from the starcluster iso that boots and that I can ssh 
into without modifying the image. I'm using Eucalyptus 1.6.2.

What's weird to me is that I can ssh in, however, I cannot access 
169.254.169.254 ip within the instance which means the ec2-get-credentials 
file can not be running successfully at startup. Something else must be 
configuring the authorized_keys file for root. This is why I wonder if 
something's up with eucalyptus on your end? Are you sure your keypair setting 
is correct when calling euca-run-instances?

In any event, the exact file that fetches the credentials is in 
/etc/init.d/ec2-get-credentials

If you still want to try manually editing this file, you need to change line 
11 of this file to:

public_key_url = http://<ip-address>:8773/latest/meta-data/public-
keys/0/openssh-key

Replace ip-address with your Eucalyptus cloud controller ip.

Let me know if that helps,

~Justin

On Friday 26 March 2010 9:12:59 am you wrote:
> Dear Justin,
> 
> I've been trying to solve the ssh problem and I've read from your e-mail
>  that:
> 
> "The login problem is likely related to the way an "EMI" needs to fetch
> it's credentials. For starcluster on EC2, there is a script in
> /usr/loca/bin that uses curl to fetch the ssh pub keys from Amazon's
> user-data server: http://169.254.169.254. This is in fact how all EC2
> images enable ssh access (to my knowledge anyway...). So, that script
> may need to be adjusted for eucalyptus to get ssh pubkey login to work."
> 
> Could you please be more specific (name of the script, location, etc)
> since I was unable to find anything in the /usr/local/bin directory of
> the starcluster iso when I chroot into it.
> 
> Thanks,
> 
> Nicholas
>