[01:11] <bdx> http://paste.ubuntu.com/24709556/
[01:11] <bdx> hehehe
[01:11] <bdx> anyone who can see whats going on there gets a gold star
[07:15] <kjackal> Good morning Juju world!
[11:05] <BlackDex> hello there
[11:05] <BlackDex> i'm getting this message
[11:05] <BlackDex> ERROR some agents have not upgraded to the current model version 2.1.3.1: machine-1
[11:06] <BlackDex> i have a ha juju running
[11:06] <BlackDex> and apperently one agent wasn't up/failed
[11:06] <BlackDex> how can i fix this?
[11:23] <SimonKLB> is it possible to run the etcd charm without persistent storage?
[11:39] <SimonKLB> nvm, just skip the --to flag =)
[15:11] <kwmonroe> hey lazyPower, arch question for ya... do you know why k8s went with etcd vs something like zookeeper?
[15:11] <lazyPower> kwmonroe: that question has come up quite a bit on their lists, but with consul instead of zookeeper. I think it was because coreos was in there early and did that heavy lifting but its hard to say
[15:12] <kwmonroe> ah, roger dodger.  just curious.  not saying zookeeper is some kind of panacea by any stretch ;)
[15:12] <lazyPower> kwmonroe: yeah, there was talk at one time of doing a libkv that would abstract the providers
[15:14] <kwmonroe> something with a small footprint like https://jujucharms.com/hadoop-hbase/ would have fit the kv bill nicely.
[15:14] <kwmonroe> because why have a microservice when you can just have 10 machines
[15:14] <lazyPower> :) no comment
[15:14] <kwmonroe> :)
[15:18] <admcleod> kwmonroe: probably go vs java
[15:54] <Budgie^Smore> o/ juju world!
[15:58] <rick_h> what's up Budgie^Smore
[15:59] <Budgie^Smore> not much, still evangelising juju in interviews :)
[15:59] <rick_h> :)
[16:00] <Budgie^Smore> had someone say the master / slave model is bad though :-/
[16:02] <Budgie^Smore> has anyone figured out what juju's performance is in terms of cpu & mem per host managed?
[16:03] <rick_h> yea, 2.2 does a lot of work on that as it's a limiting factor in JAAS being effective
[16:04] <rick_h> so there's regular testing of scalability and chattiness and such
[16:15] <Budgie^Smore> yeah it is a limiting factor in any master / slave environment... is the testing documented anywhere?
[16:22] <rick_h> Budgie^Smore: hmm, there's notes in the bugs/etc where things are identified but yea, nothing really to point to other than the various bugs as things are identified.
[16:24] <Budgie^Smore> rick_h it would definitely be useful to have since there is a fear that master / slave environments are not scalable, which we both know is bull and makes it impossible to auto scale in and out
[16:24] <rick_h> Budgie^Smore: fair enough. I might take some time to show off the 2.2 improvements in a visible way or something.
[16:24] <rick_h> Budgie^Smore: thanks for the nudge
[16:25] <Budgie^Smore> rick_h no worries, just giving back the feedback that I am getting when talking about Juju :)
[16:25] <rick_h> good stuff
[16:27] <Budgie^Smore> rick_h at the very least it would be good to have documentation on scaling controllers beyond a minimal ha setup
[16:27] <rick_h> Budgie^Smore: yes, that's firmly in my current working list
[16:27] <rick_h> Budgie^Smore: I'm doing the troubleshooting, but the goal post-troubleshooting is to turn into the "best practices" for juju taking expected scale into account
[16:27] <rick_h> Budgie^Smore: so look for "operating Juju" documentation
[16:28] <rick_h> in the near future
[16:28] <Budgie^Smore> rick_h is there anything else I haven't though about that is in your work list ? ;-)
[16:28] <rick_h> Budgie^Smore: let's see, I've got some metrics, blogs posts, and 2.2 testing on my todo list :P
[16:32] <urulama> Budgie^Smore: adding cpu cores scales how many units a controller can operate pretty much linearly. last updates to 2.2, a 8-core machine was able to run 1400 machines with 2300 units, using 10GB of RAM and 70% of CPU
[16:32] <urulama> (as an example)
[16:34] <Budgie^Smore> urulama oh awesome, thanks :) that funnily enough is in line with the example of about 1000 slaves / master that I was talking about in an interview last week
[16:35] <urulama> Budgie^Smore: there are some changes before RC1 is out, that will help lower CPU usage from what you've seen with 2.1.x even more. 2.2 will be awesome :D
[16:35] <Budgie^Smore> it is worth knowing that I am usually dealing with networks of systems in the 10k+ range
[16:35] <urulama> we'll get there :)
[16:36] <Budgie^Smore> urulama I don't doubt it, but I do think 10 masters for 10k system is not a bad ratio to start with
[16:37] <urulama> hm.
[16:37] <Budgie^Smore> but that depends if the controllers can share the world load or if HA is more a active / passive affair
[16:37] <Budgie^Smore> work*
[16:38] <urulama> HA doesn't do full load balancing atm
[16:38] <Budgie^Smore> ah ... on the roadmap?
[16:39] <urulama> yep
[16:39] <Budgie^Smore> :P
[16:39] <urulama> and not "some distant future" either :D
[16:39] <Budgie^Smore> oh if you are talking being able to hand hyperscale it better not be :P
[16:39] <urulama> but until then, current HA is not so much about scaling as it is about redundancy
[16:40] <Budgie^Smore> handle*
[16:48] <Budgie^Smore> sometimes I wish I was a stronger dev than I am, just this discussion has given me ideas :)
[21:52] <NicolinoCuralli> hi there: how can set an EIP on AWS for the controller at bootstrap phase? juju bootstrap set a dinamic public ip and if i reboot machin i can' login again
[22:36] <NicolinoCuralli> i understand that becuase there is HA configuration it is not necessary to have a EIP : is it correct?