[13:49] <Utking> Hi!
[13:49] <Utking> I'm having a hard time with juju
[13:49] <Utking> Getting an error : current model for controller not found
[13:50] <Utking> any fix for it? i've tried google already ^^
[14:07] <pmatulis> Utking, can you provide more info? like how you created the controller and any models. also what command is giving that error?
[14:09] <Utking> Sure!
[14:09] <Utking> juju status Openstackmaas
[14:09] <Utking> gives the error
[14:09] <Utking> Openstackmaas is the name of the controller :)
[14:39] <Utking> also stuff like juju sync-tools gives the same error
[14:40] <Utking> juju status --model admin/default works though
[20:55] <Stormmore> so I am back to architecting environments, woot! Trying to determine how I want to build my build env
[21:02] <Stormmore> no to figure out how to get it to actually give me a string and not a list of ascii codes!
[21:02] <Stormmore> now*
[21:37] <kwmonroe> Cynerva: you were the last objector to https://github.com/juju-solutions/layer-filebeat/pull/32.  with the decorator swizzle, any objection to me merging that?
[21:38] <Cynerva> kwmonroe: no objection here, +1 to merge. thanks for following up on that
[21:38] <kwmonroe> np
[21:59] <Stormmore> My odd question of the day, does anyone know how CDK would handle workers between stopped / started depending on load?
[22:34] <jose-phillips> hi anyone know how to setup manually the lxc network with juju?
[22:34] <jose-phillips> im just want to assing manually the ip address of each container
[22:34] <jose-phillips> how i can do that?
[22:56] <knobby> Stormmore: I don't understand your question. Are you asking about automatic scaling of machines in CDK?
[22:57] <Stormmore> knobby, short answer - yes and no
[22:58] <Stormmore> knobby, long answer, I want to build a dynamic build environment where the underlying machine can be "powered off" during quiet periods and spun up when needed
[23:00] <Stormmore> I am thinking of using jenkins which can handle it appropriately but I want my build slaves to be containers not machines
[23:23] <knobby> Stormmore: you can certainly instruct juju to add and remove workers whenever you want, but I'm not sure about any sort to automatic scaling. It might be a good idea to have the jenkins slave run as a daemonset with some tag on the kubernetes cluster and then create machines via juju and add that tag via kubectl whenever you want to grow. Jenkins would then have to be cool with slaves coming and going.