juju command progress ui

[Gustavo Niemeyer]

On Wed, Feb 27, 2013 at 1:23 PM, Brandon Holtsclaw
<me at brandonholtsclaw.com> wrote:
> juju returns after the command successfully runs because by design its async
> , you would not want the console to block when your doing something like
> 'juju deploy -n 50 hadoop' ... waiting for 50 nodes to finish before i could
> do something else is not good.

+1! I think the best idea I've seen in that regard so far is Tim's
"juju observe" command, that enables one to keep an eye on what's
happening, without getting in the way elsewhere.

That said, Ian still has a point. Right after one bootstraps, and
before the environment is live, that deploy command *will* take a long
time no matter what, because it must wait for the environment to be
responsive. For the short term, what I suggest is something simple
such as a single message on stderr:

warning: this can take several minutes because the environment is
still bootstrapping


gustavo @ http://niemeyer.net