juju command progress ui

[Andreas Hasenack]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28-02-2013 18:50, Ian Booth wrote:
>> 
>> 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

Why can't "juju status" just return immediately if the bootstrap isn't
done yet? Saying something like "Bootstrap in progress", or just "not
done". That's a status, after all. Like ec2-describe-instances
returning "pending": it doesn't block just because the instance isn't
running yet.



- -- 
Andreas Hasenack
andreas at canonical.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlEwq3oACgkQeEJZs/PdwpBEXACdFt7yDaku8ou2UQ25ZeDhR4EB
LiwAoK0PkArVaC6ecGIHOC8I674SMGQF
=pHru
-----END PGP SIGNATURE-----