maas-devel team mailing list archive

[Michael Hughes <itismike@xxxxxxxxx>]

Hi Francis. I'm continuing to test MAAS and seem to have what looks to
me like an SSH error when I check juju's status:

$ juju status

The authenticity of host 'node1 (172.16.1.161)' can't be established.
ECDSA key fingerprint is f7:9e:45:d4:1d:75:74:5d:ab:b8:b9:f3:c2:1e:ed:fc.
Are you sure you want to continue connecting (yes/no)?

The documentation doesn't mention anything about this, so rather than
typing 'yes' I figure it could be an anomaly you'd like to know about.
The message is slowly scrolling on my terminal indefinitely. I did run
ssh-keygen under my user account on the MAAS server prior to juju
bootstrap, which appeared to complete successfully, and per your
instructions I did not copy any ssh keys anywhere.

-Mike

On Fri, Apr 20, 2012 at 10:18 AM, Francis J. Lacoste
<francis.lacoste@xxxxxxxxxxxxx> wrote:
>
>
> On 12-04-20 10:12 AM, Diogo Matsubara wrote:
>>> > That's a misunderstanding. You don't need to associate your SSH key with
>>> > your account in MAAS to use Juju. Juju will automatically add the user's
>>> > SSH key to the ubuntu account. Associating SSH keys is only required if
>>> > you want to manage the instance without Juju.
>> Ah! Thanks for clarifying this Francis.
>> Out of curiosity, how does juju adds the key to the node without
>> previously adding it?
>> Using the MAAS api key, it queries the MAAS server, adds the key to
>> the MAAS account and then MAAS boots up the node and the key will be
>> there? When I tested this, it didn't quite work, but I might have done
>> something wrong. I'll try again today.
>>
>
> No. Juju provides it's own user-data that will do the right thing when
> cloud-init is invoked.
>
> Basically, Juju will put the user's SSH keys in the clout-init
> user-data. So when the nodes install itself, it will install the keys in
> the account.
>
> You won't see these keys in MAAS.
>
> --
> Francis J. Lacoste
> francis.lacoste@xxxxxxxxxxxxx
>