Re: [Starcluster] SOLVED!! instance ssh problem...
This archive was generated by
I do have a "add_key.pl" in the "/usr/share/eucalyptus" directory.
However this might not be much relevant in the process of copying the
ssh key in later versions of Eucalyptus (i.e. 1.6.x), since I've
discovered that I could have achieved the same fix if I had
(instead of public_key_url=http://169.254.169.254/2008-02-01/meta-data/public-keys/0/openssh-key
in /etc/init.d/ec2-get-credentials" of starcluster iso.
Notice that in this case "latest" points to the same directory as
"api_ver" which in your eucalyptus installation (1.6.2) just happens
to be "1.0", so it works out of the box!
P.S. Is there any progress in the starcluster git python code with
regards to commands that did not work with eucalyptus credentials
(e.g. starcluster start , etc)?
On Mon, Mar 29, 2010 at 7:35 AM, Justin Riley <jtriley_at_mit.edu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Hi Nicholas,
> Awesome, glad to hear you've got the StarCluster ami working with
> Eucalyptus. I'm still a little curious as to why I didn't need those
> modifications to /etc/init.d/ec2-get-credentials and you did.
> My current theory on this:
> I believe that Eucalyptus is running the script
> $EUCALYPTUS/usr/share/eucalyptus/add_key.pl somewhere in the process of
> bringing the instance up.
> Looking at this script it appears that they manually pipe the pub key
> into root's authorized_keys file (ie they're mounting the iso and
> creating the authorized_keys outside of the instance).
> My only guess as to why my EMI worked out of the box with respect to ssh
> is because of this script. Maybe it's not being executed for some reason?
> Can you check if that script exists for you in /usr/share/eucalyptus?
> Thanks and in any event, thanks for tracking this down :D
Received on Mon Mar 29 2010 - 11:06:39 EDT