Juju 2.3 release train starting

Hi folks, We are gearing up to release Juju 2.3. Juju 2.3 brings two headline features: * Cross model relations - the ability to relate applications in different models * Persistent storage - storage can outlive the unit or model it was created for. The team will be releasing 2.3-beta1

Juju 2.3 release train starting

Hi folks, We are gearing up to release Juju 2.3. Juju 2.3 brings two headline features: * Cross model relations - the ability to relate applications in different models * Persistent storage - storage can outlive the unit or model it was created for. The team will be releasing 2.3-beta1

Charm Tools distribution channels and versions

Hey folks, I'm having a bit of a hard time figuring out which distribution of charm-tools I can/should use and how they are versioned in order to keep track of bugfixes. As far as I understand, the snaps are preferred over the packages in the Juju PPA and PyPI falls somewhere in between? The

Re: set_state not setting the state immediately

So the best practice here is to touch a file and test for the existence of that file before running must_be_called_exactly_once()? I think part of the issue here is that without knowing the extent of the hook it is hard to enforce idempotency as a charm writer. It's easy to look at the code above

Re: set_state not setting the state immediately

Hi there On Tue, Oct 3, 2017 at 1:34 PM, Konstantinos Tsakalozos < kos.tsakalo...@canonical.com> wrote: > Hi, > > It seems the reactive framework is flushing the states at the end of hook > execution. This may surprise charm authors. Consider the following code: > > @when_not("initialized") >

intro to speaking juju, the show and blog

Last week we did an intro to the terminology used in Juju during the Juju Show [1]. I've gotten up the blog post [2] to go with it now. Please check it out and let me know if you find it useful for introducing folks to Juju. Thanks Rick 1: https://www.youtube.com/watch?v=_yMx129uhYc 2:

Re: set_state not setting the state immediately

On 3 October 2017 at 19:34, Konstantinos Tsakalozos wrote: > Hi, > > It seems the reactive framework is flushing the states at the end of hook > execution. This may surprise charm authors. Consider the following code: > > @when_not("initialized") > def init(): >

set_state not setting the state immediately

Hi, It seems the reactive framework is flushing the states at the end of hook execution. This may surprise charm authors. Consider the following code: @when_not("initialized") def init(): must_be_called_exactly_once() set_state("initialized") @when("initialized") @when_not("ready") def