Re: peergrouper tests badly need fixing

This will also be why the wily CI tests don't pass as wily has Go 1.5 Tim On 16/09/15 16:53, Tim Penhey wrote: > Hi all, > > Using Go 1.5 on trusty has the peergrouper tests failing very often. 1 > or 2 almost every time. > > Dave suggested trying "GOMAXPROCS=1" which will make the scheduler

Re: Running upgrade steps for units

Here is an approach that will work for now: http://reviews.vapour.ws/r/2672/diff/# - a 1.25 based branch If we are happy with this, I can forward port to master and add the other upgrade step. Also, do we want to back port to 1.24? When is the 1.24.6 release? Tim On 16/09/15 16:45, Ian Booth

Re: Running upgrade steps for units

On 16/09/15 12:06, Menno Smits wrote: > On 16 September 2015 at 08:41, Tim Penhey wrote: > >> On 15/09/15 19:38, William Reade wrote: >>> Having the machine agent run unit agent upgrade steps would be a Bad >>> Thing -- the unit agents are still actively running the

Re: Running upgrade steps for units

On 16 September 2015 at 08:41, Tim Penhey wrote: > On 15/09/15 19:38, William Reade wrote: > > Having the machine agent run unit agent upgrade steps would be a Bad > > Thing -- the unit agents are still actively running the old code at that > > point. Stopping the unit

Re: Running upgrade steps for units

Having the machine agent run unit agent upgrade steps would be a Bad Thing -- the unit agents are still actively running the old code at that point. Stopping the unit agents and managing the upgrade purely from the machine would be ok; but it feels like a lot of effort for very little payoff, so

[ANN] Amulet 1.11.1 released

Hello, I'm happy to announce the Amulet 1.11.1 release. You can install and upgrade amulet from the juju stable ppa: sudo add-apt-repository ppa:juju/stable sudo apt-get update sudo apt-get install amulet For all other users, amulet is available in pip pip install amulet #

Re: state of networking?

Its been hard to see much progress on this and i wanted to checkin wrt to the current state. The requirement of public ip on for the subnets sort of defeats the purpose of supporting non default vpcs. The use of vpc is typically around network segmentation and isolation semantics, ie db and app

Re: [ Docs ] - Charming with Docker

i think participating in the burgeoning docker ecosystem is a worthwhile goal by making it easier to write charms that utilize docker. I do have some concerns though about the complexity of the layering that's taking place in the charm ecosystem. I've found that juju has been fairly hard to teach

Re: [ Docs ] - Charming with Docker

I see your concerns about layering, reactive, et-al. for introductory/new charmers. I however raise you a value proposition, and will speak to the point we are generating the 'best practice' method, that we want to guide charmers down. The common feedback we've received from authors is "I'm not as