Synchronous Bootstrap

Nate Finch nate.finch at canonical.com
Tue Dec 3 12:06:32 UTC 2013


It seems going from asynchronous to synchronous is highly unlikely to break
anything.  It might slow things down a little, if you were counting on
being able to get some stuff done while it runs, but it shouldn't
*break *unless
someone was specifically trying to race the bootstrap and needed to get
something done before it finishes.... and that's just bad design anyway.


On Tue, Dec 3, 2013 at 6:49 AM, Andreas Hasenack <andreas at canonical.com>wrote:

> On Tue, Dec 3, 2013 at 4:31 AM, Andrew Wilkins <
> andrew.wilkins at canonical.com> wrote:
>
>> Ahoy,
>>
>> Just wanted to inform everyone that synchronous bootstrap has landed on
>> trunk. If you've got any scripts that bootstrap an environment and expect
>> it to chug away in the background, then some script changes will be
>> necessary.
>>
>>
> Why not introduce this behavior via a switch to the existing bootstrap
> command? Something like:
>
> juju bootstrap --wait
>
> Then existing scripts wouldn't break.
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20131203/35348a02/attachment.html>


More information about the Juju-dev mailing list