juju command progress ui

[Gustavo Niemeyer]

On Thu, Feb 28, 2013 at 3:25 AM, Julian Edwards
<julian.edwards at canonical.com> wrote:
> On 28/02/13 16:17, Gustavo Niemeyer wrote:
>> On Thu, Feb 28, 2013 at 2:35 AM, Julian Edwards
>> <julian.edwards at canonical.com> wrote:
>>>> Having a client command that blocks for 10 minutes doing absolutely
>>>> nothing while the provider decides to allocate a new machine on its
>>>> own time seems to me like a pretty poor user experience.
>>>
>>> This is exactly what "juju deploy" does if you run it immediately after
>>> bootstrap returns.
>>
>> That's not correct, and I've explained why:
>
> Well, yes it is, it hangs.  I have seen this happen.

Yes, it hangs, waiting to do something!

(...)
> So am I.  I'm just trying to explain a problem that not only I have, but
> quite a few others based on my experiences.  I just want to make things
> better.
>
> That's it from me on this thread, I am done.

My way or no way? That's not how things have to be. Both of us are
trying to improve how juju works, and all I've been pointing out is
that having a command line interface that blocks while very long
asynchronous operations complete is, frankly, a terrible user
experience. If you can't accept that, let's just acknowledge a
difference in perspective and try to solve the underlying issues you
see.


gustavo @ http://niemeyer.net