Re: Automatic retries of hooks

On 21 January 2016 at 09:51, James Page wrote: > On Wed, 20 Jan 2016 at 20:31 William Reade > wrote: >> >> On Wed, Jan 20, 2016 at 8:01 PM, Dean Henrichsmeyer >> wrote: >>> >>> You realize James was complaining and not

Re: Sending binaries over relations

Two thoughts. First, I think it's interesting that you see resources as such a dynamic thing. I believe the current model accommodates this (we considered user-provided resources, and what you are describing are essentially charm-generated resources, but they would behave the same way). Second,

Re: Automatic retries of hooks

On Wed, 20 Jan 2016 at 20:31 William Reade wrote: > On Wed, Jan 20, 2016 at 8:01 PM, Dean Henrichsmeyer > wrote: >> >> You realize James was complaining and not celebrating the "success" ? The >> fact that we can have a discussion trying to

Re: Sending binaries over relations

I'm sorry, I wasn't clear about this. I wasn't consistent enough with my usage of Charm VS Service. The library is not for the connection between two charms. The library is for the connection between two services (the two services that the two Charms deploy). I've seen it common for Java services

Re: Configuring environments.yaml for lxd

I think LXD is only in 1.26-alpha3 which you can get from ppa:juju/devel On Thu, Jan 21, 2016, 10:30 AM Daniel Bidwell wrote: > I have reinstalled my machine with ubuntu 15.10 to get lxd. I have > juju-1.25.0-wily-amd64. lxc image list images: returns a list of > images

Re: Sending binaries over relations

I actually don't see why you would ever need to distribute a specific library for connecting to an API on another charm. The charm using the dynamically determined client would still require a static (i.e. backward compatible) API on the client library (otherwise the client charm would have no

Defaulting tests internal to the package

[reposting this to the wider juju-dev mailing list] So, I hit an interesting problem a while back. I have some unit tests that need to be internal tests, thus they are in 'package foo'. However, my code needs to use some testhelper functions that someone else wrote... which are in 'package

Re: Juju devel 2.0-alpha1 is available for testing

On Thursday, January 21, 2016, Marco Ceppi wrote: > Wow! A lot to play with tomorrow. Thanks for the release core team! > +,1 some solid bits to start testing with. Looking forward to exploring. Thanks juju-core folks. -Antonio > On Thu, Jan 21, 2016, 5:06 PM

Re: Sending binaries over relations

This use-case lines up almost exactly with how we deal with the Hadoop client libraries in the Hadoop core charms. We handle this using the apache-hadoop-plugin subordinate charm. The subordinate charm provides the Hadoop libraries to the client, with the versions supported being locked in the

Juju devel 2.0-alpha1 is available for testing

# juju-core 2.0-alpha1 A new development release of Juju, juju-core 2.0-alpha1, is now available. This release replaces version 1.26-alpha3. ## Getting Juju juju-core 2.0-alpha1 is available for Xenial and backported to earlier series in the following PPA:

Juju devel 2.0-alpha1 is available for testing

# juju-core 2.0-alpha1 A new development release of Juju, juju-core 2.0-alpha1, is now available. This release replaces version 1.26-alpha3. ## Getting Juju juju-core 2.0-alpha1 is available for Xenial and backported to earlier series in the following PPA:

Re: Juju devel 2.0-alpha1 is available for testing

Wow! A lot to play with tomorrow. Thanks for the release core team! On Thu, Jan 21, 2016, 5:06 PM Curtis Hovey-Canonical wrote: > # juju-core 2.0-alpha1 > > A new development release of Juju, juju-core 2.0-alpha1, is now available. > This release replaces version