Re: Feature Request: -about-to-depart hook

Thanks for the feedback. I think this is something we should try to make some time for. I've copied Alexis and we'll see what can be done with the team. Alexis, can you put this on the list of things to investigate for future roadmap? Thanks On Tue, Nov 10, 2015 at 8:22 AM Mario Splivalo

Re: Feature Request: -about-to-depart hook

On Tue, Nov 24, 2015 at 12:55 PM Cheryl Jennings < cheryl.jenni...@canonical.com> wrote: > I'll be tracking these kind of feature requests here: > https://github.com/juju/juju/wiki/Feature-Requests > > There's not much there yet, but we'll be filling it out as we go through > the other various

Re: Feature Request: -about-to-depart hook

This is already on my list. I'm still figuring out a good way to organize / record these in a publicly viewable place. I'll send out a link once I get something together. (Hopefully tonight!) Thanks! -Cheryl On Nov 23, 2015 5:20 PM, "Rick Harding" wrote: > Thanks

Re: lxd provider in master

On 24/11/15 04:53, Eric Snow wrote: > On Sun, Nov 22, 2015 at 8:50 PM, Tim Penhey wrote: >> Hi all, >> >> I noticed that the lxd provider was now in master and attempted to use >> it to help debug an HA problem. >> >> In environments.yaml file I added a very simple

Re: Feature Request: -about-to-depart hook

Thank you Cheryl! On Mon, Nov 23, 2015, 6:33 PM Cheryl Jennings wrote: > This is already on my list. I'm still figuring out a good way to organize > / record these in a publicly viewable place. > > I'll send out a link once I get something together. (Hopefully

Re: lxd provider in master

On 24/11/15 12:47, Tim Penhey wrote: > On 24/11/15 04:53, Eric Snow wrote: >> On Sun, Nov 22, 2015 at 8:50 PM, Tim Penhey wrote: >>> Hi all, >>> >>> I noticed that the lxd provider was now in master and attempted to use >>> it to help debug an HA problem. >>> >>> In

Re: lxd provider in master

It is valid YAML, last one wins. On 24/11/15 15:51, Nate Finch wrote: > I guess we don't error out when we see duplicate environment names? > Shouldn't we? > > On Mon, Nov 23, 2015 at 6:47 PM Tim Penhey > wrote: > > >> In

Re: lxd provider in master

I guess we don't error out when we see duplicate environment names? Shouldn't we? On Mon, Nov 23, 2015 at 6:47 PM Tim Penhey wrote: > >> In environments.yaml file I added a very simple clause: > >> > >>lxd: > >> type: lxd > > > > found that further down the

Re: lxd provider in master

On Sun, Nov 22, 2015 at 8:50 PM, Tim Penhey wrote: > Hi all, > > I noticed that the lxd provider was now in master and attempted to use > it to help debug an HA problem. > > In environments.yaml file I added a very simple clause: > >lxd: > type: lxd This is

Re: lxd provider in master

On Mon, Nov 23, 2015 at 10:53 AM, Eric Snow wrote: > On Sun, Nov 22, 2015 at 8:50 PM, Tim Penhey wrote: >> But when I try to bootstrap, I get the following: >> >> $ juju bootstrap --debug Also note that the lxd-deploy-wily-amd64 test still

Juju stable 1.25.1 is proposed

# juju-core 1.25.1 A new proposed stable release of Juju, juju-core 1.25.1, is now available. This release may replace version 1.25.0 on Tuesday Dec 1. ## Getting Juju juju-core 1.25.1 is available for Wily and backported to earlier series in the following PPA: