juju command progress ui

[Ian Booth]

> 
> We have feedback problems in some of our logic, and that can be fixed.
> If we made asynchronous commands block for no reason, when they're in
> fact done, we'd be going to a lesser model.
> 
> 

Mark, Julian and John have summarised the issue well, especially the part about
making the UI fit the user's model, so I won't repeat their points here. While I
agree the async commands should not block (although status and deploy do
currently block for minutes or more if bootstrap is not finished yet), the
current situation is clearly sub optimal from a usability perspective. My vote
would be for the commands (eg bootstrap) to automatically go into observe mode
once the request has been actioned and the user can ^C any time after that if
they want. My view is that that model captures the best of both worlds, and as a
juju user is what I'd prefer to see happen.