It depends if your hook goes into 'error' state or 'blocked'.
Error should generally be avoided because it is a signal to Juju that you
can no longer make forward progress (generally meant to mean there is a
logic bug/typo/etc in your charm). With Error Juju may retry the hook that
failed but it
On Fri, May 26, 2017 at 11:26 AM Patrizio Bassi
wrote:
> Dear Andrew,
> what about private clouds such as maas?
>
MAAS is a bit special, because the disks are physically attached to the
machines. If and when we support something like Ceph RBD natively inside
Juju,
On Fri, May 26, 2017 at 11:26 AM Patrizio Bassi
wrote:
> Dear Andrew,
> what about private clouds such as maas?
>
MAAS is a bit special, because the disks are physically attached to the
machines. If and when we support something like Ceph RBD natively inside
Juju,
Dear Andrew,
what about private clouds such as maas?
Patrizio
Il giorno mer 24 ma 2017 alle 03:38 Andrew Wilkins <
andrew.wilk...@canonical.com> ha scritto:
> Hi folks,
>
> One of the things we're working on for the 2.3 release (not 2.2!) is
> persistent storage. What this means is the ability
Hi all,
It's been a busy week as we continue towards the 2.2-rc1 release. As Tim
said earlier in the week, the release will slip to next week as we continue
ironing out the kinks. One of the main things we've been focusing on this
week is improving scalability and resilience in large deployments,
On Thu, May 25, 2017 at 12:59 PM, Giuseppe Attardi wrote:
> I have written a charm for OpenStack Gnocchi.
> The service requires a postgresql database relation.
>
> The start hook fails, of course, because the relation is not set.
>
> I expected that, but I expected
I have written a charm for OpenStack Gnocchi.
The service requires a postgresql database relation.
The start hook fails, of course, because the relation is not set.
I expected that, but I expected that when I issue
juju add-relation gnocchi postgresql:db
it will invoke the
A big +1!
Launchpad was the reason why I didn't yet contribute to charmhelpers..
2017-05-25 14:57 GMT+02:00 James Page :
> Hi Charmers
>
> There has been a bubbling undercurrent of desire to move charmhelpers code
> hosting out of bazaar on Launchpad to git on github,com
+1 from me as well.
I'll take webhook automation for the win, Alex.
All the best,
Charles
On Thu, May 25, 2017 at 7:58 AM James Page wrote:
> Hi Charmers
>
> There has been a bubbling undercurrent of desire to move charmhelpers code
> hosting out of bazaar on Launchpad
+1 from me, especially since James is volunteering. :D Thanks for getting
this ball rolling!
On Thu, May 25, 2017 at 8:57 AM, James Page wrote:
> Hi Charmers
>
> There has been a bubbling undercurrent of desire to move charmhelpers code
> hosting out of bazaar on
On Thu, May 25, 2017 at 2:17 PM, Adam Collard
wrote:
> On Thu, 25 May 2017 at 14:14 Alex Kavanagh
> wrote:
>
>> Hi James
>>
>> I'm a big +1 to this idea, but with one tiny reservation: I have a
>> rather large merge-proposal regarding a
On Thu, 25 May 2017 at 14:14 Alex Kavanagh
wrote:
> Hi James
>
> I'm a big +1 to this idea, but with one tiny reservation: I have a rather
> large merge-proposal regarding a refactor of the hosts + ports fetch bug +
> refactor of the fetch code. It would be nice to
Hi James
I'm a big +1 to this idea, but with one tiny reservation: I have a rather
large merge-proposal regarding a refactor of the hosts + ports fetch bug +
refactor of the fetch code. It would be nice to get that in first (but
that's purely personal!)
However, we'll lose the history of the
Hi Charmers
There has been a bubbling undercurrent of desire to move charmhelpers code
hosting out of bazaar on Launchpad to git on github,com alongside other
charm ecosystem development tooling.
I'd like to get the code migrated over ASAP and then we can start enabling
automatic PR testing and
14 matches
Mail list logo