We are pleased to announce the release of Juju 1.25.13

Hi all, Today we released Juju 1.25.13 which addressed some memory leak bugs. For a list of all bugs fixed in these release see: https://launchpad.net/juju-core/+milestone/1.25.13 Regards, Chris -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at:

We are pleased to announce the release of Juju 1.25.13

Hi all, Today we released Juju 1.25.13 which addressed some memory leak bugs. For a list of all bugs fixed in these release see: https://launchpad.net/juju-core/+milestone/1.25.13 Regards, Chris -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at:

Re: Elasticseach Charm Promulgation - things to keep in mind

Also - https://bugs.launchpad.net/elasticsearch-charm/+bug/1714126 On Wed, Aug 30, 2017 at 6:47 PM, James Beedy wrote: > Elasticsearch >= 5.x is non-compat with kibana <= 5.x. The current default > configs for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch >

Re: Elasticseach Charm Promulgation - things to keep in mind

Elasticsearch >= 5.x is non-compat with kibana <= 5.x. The current default configs for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch may break any bundles that have elasticsearch + kibana not pinned to a specific charm store uri/rev upon promulgation. This probably won't affect

Re: Elasticsearch Charm Promulgation

On Wed, Aug 30, 2017 at 02:38:42PM -0400, Tim Van Steenburgh wrote: > I checked with James Beedy and he's +1 on promulgating this one too. > > Looks like there's no bugs-url or homepage set on the charm though. Please > add those (see `charm set -h`) and then I'll be happy to promulgate it. I've

Re: Juju-gui only show localhost as the deployment option

I have a slightly different requirement. Currently in our OpenStack cloud, if a user wants to use Juju, it must install a Juju controller in his project. It would be useful to use a single controller for the whole cloud and to just switch the project which the controller uses. Juju already can

Re: Juju Charmer application

Thanks Frode, welcome to ~charmers! On Wed, Aug 30, 2017 at 4:10 PM, David Ames wrote: > Huge +1 > > On Wed, Aug 30, 2017 at 3:14 AM, Frode Nordahl > wrote: > > Dear Juju community, > > > > I would like to officially apply for membership of

Re: Juju Charmer application

Huge +1 On Wed, Aug 30, 2017 at 3:14 AM, Frode Nordahl wrote: > Dear Juju community, > > I would like to officially apply for membership of the Juju ~charmers team. > > Through the course of the past year I have made contributions to the > OpenStack Charms and other

Re: Elasticsearch Charm Promulgation

On Wed, Aug 30, 2017 at 6:27 AM, Haw Loeung wrote: > On Tue, Aug 22, 2017 at 08:54:14AM +0100, Tom Haddon wrote: > > On Mon, Aug 21, 2017 at 02:53:10PM +0100, Tom Haddon wrote: > > [...] > > > I checked with some of the ~onlineservices-charmers team and they were >

Re: Juju-gui only show localhost as the deployment option

Just to toss, out. JAAS [1] is built to be Juju as a Service across clouds doing some of the extra work to enable users to have a single dashboard across a wide array of clouds and regions. Give it a try and I'd love to chat about any feedback on where JAAS does or doesn't fit for the needs you're

Re: juju deploy docker

Can you check the juju debug-log or juju ssh docker/0 and sudo cat /var/log/juju/unit-xxx to see what's failed? It looks like the charm there is hitting an error and will have to debug what's up by checking the logs. On Wed, Aug 30, 2017 at 1:02 PM Micheal B wrote: >

juju deploy docker

Running juju vsphere cloud – current CDK Test both Juju deploy docker And juju deploy docker --series xenial –force always get hook failed: "config-changed" Tested other installs juju add-unit kubernetes-worker  --- install fine check DNS / DHCP all of that appears fine

Re: Juju-gui only show localhost as the deployment option

Akshat, Just to chip in some of my thoughts on this since we (disclosure, I'm a researcher at Lenovo) have had extensive discussions on a similar use case and consequently come down to the same challenge as you are currently looking at. 1. Juju CLI allows user to select controller, which

Re: Juju-gui only show localhost as the deployment option

Akshat, Just to chip in some of my thoughts on this since we (disclosure, I'm a researcher at Lenovo) have had extensive discussions on a similar use case and consequently come down to the same challenge as you are currently looking at. 1. Juju CLI allows user to select controller, which

Re: Promulgate request: Grafana

Done, thanks! On Wed, Aug 30, 2017 at 4:38 AM, Tom Haddon wrote: > Hi Folks, > Could we get cs:~prometheus-charmers/grafana promulgated? > > The code for the charm is https://code.launchpad.net/grafana-charm and > there's > a team that maintains it

Re: Juju Charmer application

+1 On Wed, 30 Aug 2017 at 11:15 Frode Nordahl wrote: > Dear Juju community, > > I would like to officially apply for membership of the Juju ~charmers team. > > Through the course of the past year I have made contributions to the > OpenStack Charms and other Charm

Re: Elasticsearch Charm Promulgation

On Tue, Aug 22, 2017 at 08:54:14AM +0100, Tom Haddon wrote: > On Mon, Aug 21, 2017 at 02:53:10PM +0100, Tom Haddon wrote: > [...] > > I checked with some of the ~onlineservices-charmers team and they were happy > > for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch/ to > > replace

Juju Charmer application

Dear Juju community, I would like to officially apply for membership of the Juju ~charmers team. Through the course of the past year I have made contributions to the OpenStack Charms and other Charm projects. I have also had the privilege of meeting many of you in person, and have shared

Promulgate request: Grafana

Hi Folks, Could we get cs:~prometheus-charmers/grafana promulgated? The code for the charm is

Re: Juju-gui only show localhost as the deployment option

Thank you Feng, As I understand for now there is no way to use multiple providers with juju either with a GUI or command line. My goal is to be able to allow users to deploy charms (mostly wordpress/drupal/ghost) on a cloud of their choice. Anything that allows me to do this is acceptable. The