[Starcluster] SOLVED!! instance ssh problem...

[Nicholas Ampazis]

Dear Justin,

I've finally SOLVED the ssh problem as follows:

I connected into a standard ubuntu emi in which I could ssh without
any problem (a standard karmic server version). I noticed that the
script  "/usr/bin/ec2-fetch-credentials" was invoked which in turn
depended on  "/usr/lib/python2.6/dist-packages/ec2init/__init__.py".

I opened it up and saw the following code:

class EC2Init():
    api_ver  = '2008-02-01'
    conffile = '/etc/ec2-init/ec2-config.cfg'

    location_locale_map = {
        'us' : 'en_US.UTF-8',
        'eu' : 'en_GB.UTF-8'
    }

    location_archive_map = {
        'us' : 'http://us.ec2.archive.ubuntu.com/ubuntu',
        'eu' : 'http://eu.ec2.archive.ubuntu.com/ubuntu'
    }

    def __init__(self):
        self.meta_data_base_url =
'http://169.254.169.254/%s/meta-data' % self.api_ver
        self.user_data_base_url =
'http://169.254.169.254/%s/user-data' % self.api_ver
        self.config = ConfigObj(self.conffile)

which means that the %s part of  meta_data_base_url was substituted by
the value of  api_ver  (2008-02-01)

Therefore all I had to do was to chroot into starcluster  and then
edit  "/etc/init.d/ec2-get-credentials" by simply replacing  the line

public_key_url=http://169.254.169.254/1.0/meta-data/public-keys/0/openssh-key

with

public_key_url=http://169.254.169.254/2008-02-01/meta-data/public-keys/0/openssh-key

and then re-bundle and re-register the new image!

Now it works as a charm (even though of course there's currently no
other account than the root).


Hope this helps other people with the same problem.


Best regards,


Nicholas

>
> On Sunday 28 March 2010 10:52:39 pm Justin Riley wrote:
>> 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
>>