SSH keys

[Andrew Wilkins]

So, synchronous bootstrap broke CI. The reason for this is that we're now
using SSH as part of the process; I can see in the CI logs that a
non-default identity file is being used with "juju scp". That explains why
"juju ssh" (during bootstrap) is failing -- it just tries the default keys.

To workaround, CI could specify the key in ~/.ssh/config (see
https://bugs.launchpad.net/juju-core/+bug/1257371/comments/9). To fix the
problem for good, we can do a couple of things:
 - Add yet more configuration to Juju to specify which key to connect with,
or (and/or?)
 - Auto-generate an SSH key for each new environment at bootstrap.

The second option is far more user-friendly IMHO; the less configuration
the better. Is there any reason why we should not do this? If we did this,
then "authorized-keys" would be changed to implicitly include the
auto-generated public key.

On a related note, it occurred to me that the Windows CLI won't be able to
bootstrap anymore. We're going to need to update the code to use the plink
executable from PuTTY.

Cheers,
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20131205/127dd7f1/attachment.html>