[Bug 524101] Re: optionally fetch public ssh keys from Launchpad when starting an instance

[Scott Moser]

On Mon, 22 Feb 2010, Etienne Goyer wrote:

> Rather, if euca-add-keypair could be pointed to an existing id file
> (optionally, pointing to one stored in Launchpad), that would be
> terrific.  The fact that we have to generate a new key each time we
> upload an identity to EC2/Eucalyptus is terribly annoying; using an
> existing identity/key pair would be a huge usability improvement over
> ec2-api-tools.

I agree, its less than wonderful, but you have to admit that supporting on
ly launchpad as a source for keys is only slightly more useful.

The current system isn't really all that bad:

Host *.eu-west-1.compute.amazonaws.com
  IdentityFile /home/smoser/data/aws-smoser/ec2-keypair.eu-west-1.pem

I have lines like the following in my .ssh/config

Host *.eu-west-1.compute.amazonaws.com
  IdentityFile /home/smoser/.ssh/ec2-keypair.eu-west-1.pem

# for euca hosts (match however you want)
Host 192.168.2.*
  IdentityFile /home/smoser/.ssh/euca-key.pem


Then, when you create a new key with euca-add-keypair, just redirect to
/home/smoser/.ssh/euca-key.pem

-- 
optionally fetch public ssh keys from Launchpad when starting an instance
https://bugs.launchpad.net/bugs/524101
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.