API change: juju subcommands will wait for connection to Zookeeper
gustavo.niemeyer at canonical.com
Thu Nov 17 18:47:52 UTC 2011
>> One alternative was to put the waiting in the bootstrap subcommand, but
>> this approach feels much cleaner. All subcommands that depend on ZK will
>> simply be gated in this fashion.
> Yep -- as I recall the motivation was that juju commands should block
> until they've read/written all the state they're responsible for. So
> bootstrap exits fast, because it does all it can quite quickly; the next
> command may block for a while because it's waiting for state to exist,
> but once it's performed its interactions it too can exit.
Indeed. It would be nice to have that rationale as part of the spec, Jim.
+1 from me too as we talked over UDS.
-- I'm not absolutely sure of anything.
More information about the Juju