Orchestration charms

2017-01-09 Thread Simon Kollberg
Hello Juju people! I'm currently working on a charm with a some what special characteristics. We call it the CharmScaler. The purpose of the charm is to automatically scale the number of units of a charm depending on the current usage of the application. Much like the autoscaling in Kubernetes and

Re: [Review Queue] Elastisys Charmscaler Promulgated!

2017-03-20 Thread Simon Kollberg
On 20 March 2017 at 18:13, Charles Butler wrote: > Greetings, > > I realized last week I had completed a review and failed to send an update > to the mailing list. As some of you may have heard on the Juju Show that > Elastisys released their Charm Scaler to the promulgated channel. > > > This wa

Re: [Review Queue] Elastisys Charmscaler Promulgated!

2017-03-21 Thread Simon Kollberg
> > > 2017-03-20 21:54 GMT+01:00 Simon Kollberg : > >> >> >> On 20 March 2017 at 18:13, Charles Butler >> wrote: >> >>> Greetings, >>> >>> I realized last week I had completed a review and failed to send an >>> update t

Re: Normalizing output dir for charm build

2017-05-11 Thread Simon Kollberg
+1! While you're at it; I think it could be wise to namespace everything with Juju. For example $JUJU_LAYER_PATH and ~/.cache/juju/charm-build/deps or something similar. I think it would make everything more coherent and also eliminate the possibility of naming collisions. This could of course be

Re: Juju 2.2-rc2 has been released

2017-06-09 Thread Simon Kollberg
conjure-up still seem to be on rc1 % sudo snap install conjure-up --classic --candidate conjure-up (candidate) 2.2-rc1-20170606.0106 from 'canonical' installed % juju --version 2.2-rc1-xenial-amd64 % conjure-up --version conjure-up 2.2-rc1 % sudo snap remove conjure-up conjure-up removed % sudo sn