[Maas-devel] SSH keys not being added to nodes. Recurring problem?

[Kevin Jackson]

Hi,
I'll jump in at this point - I gave up on using MAAS as I could never get
past this issue.  I had issues troubleshooting what seemed to be a basic
task: provision a server and then the output of such tools suggests the
machine is ready.  The bootstrap instance becomes a black-box and you can't
expect a user to keep ssh'ing to see its up.  Or do you?
To a user, this expectation isn't managed very well and personally I think
should be addressed.  When I provision other nodes in my cloud environment,
within a few seconds I can SSH in.  That's *my* expectation unless some
output from a tool tells me differently.

Cheers,

Kev



On 11 July 2012 09:49, Jeroen Vermeulen <jtv at canonical.com> wrote:

> On 2012-07-11 03:35, Gavin Panella wrote:
>
>> There seem to be a few people having problems with MAAS right now
>> relating to SSH keys. I spoke briefly with roaksoax about it. Edited
>> transcript:
>>
>
> Is the node actually allocated?  One usability problem we've had is that
> sometimes people expect to be able to ssh into a node after commissioning,
> before it's been deployed.
>
>
> Jeroen
>
> --
> Mailing list: https://launchpad.net/~maas-**devel<https://launchpad.net/~maas-devel>
> Post to     : maas-devel at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maas-**devel<https://launchpad.net/~maas-devel>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>



-- 
Kevin Jackson
@itarchitectkev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20120711/cf3870e4/attachment.html>