[02:01] <bdx> lazyPower, mbruzek: just browsing around and found this interesting pertaining to kub + lets encrypt https://github.com/kelseyhightower/kubernetes-letsencrypt-tutorial
[02:02] <bdx> that guy is a bad ass, check out some of his other work too if you have a minute .... super cool
[02:06] <bdx> https://github.com/kelseyhightower/vault-controller
[02:56] <bdx> xenial+reactive+python3 jenkins refactor -> https://github.com/jamesbeedy/juju-charm-jenkins
[02:56] <bdx> jamespage: ^
[03:23] <bdx> boom https://jujucharms.com/u/creativedrive/jenkins/4
[05:38] <jamespage> bdx, oh nice
[05:38] <jamespage> beisner, ^^
[05:38] <jamespage> bdx has been busy
[08:08] <kjackal> Good morning Juju world
[10:12] <marcoceppi> bdx: I feel like I'm constantly the bearer of bad news
[10:12] <marcoceppi> bdx: https://github.com/jenkinsci/jenkins-charm
[10:12] <marcoceppi> bdx: in the future, I think we should start pushing a policy of people announcing what they're working on, we're (me) are terrible at this
[11:38] <kjackal> magicaltrout: you should setup a ci it is supper easy (took me one evening). You just chekin something and your work is pushed to the store automagically. I have only good words to say!
[11:40] <magicaltrout> I have CI kjackal just not for charms, I'm lazy :P
[11:41] <magicaltrout> that said, its not like I code charms for a living, so I suspect our priorities differ ;)
[11:42] <kjackal> magicaltrout: true!
[11:42] <magicaltrout> got knocked back by the apache mesos folk when asking about LXC support, silly people, they're missing a trick
[11:42] <magicaltrout> looks like I'll have to learn C
[11:43] <kjackal> magicaltrout: I hope someone from juju-qa will step up and say "kjackal you are doing this all wrong! We have this jenkins plugin that will make your life super easy!"
[11:43] <kjackal> Ahhh C! Best language ever!
[11:43] <kjackal> magicaltrout: not joking ^
[11:44] <magicaltrout> I don't believe you
[11:45] <kjackal> magicaltrout: Everything you do with C is like DIY! Always wear protective gear and never try this at home!
[11:45] <magicaltrout> lol
[11:46] <magicaltrout> I tried extending mesos for LXC a few weeks ago, it was very much trial and more error
[11:47] <magicaltrout> it was funny they asked me what use case they were missing.....
[11:47] <magicaltrout> why people think application containers are the best way forward I have no clue
[11:50] <kjackal> developers build these things to protect themselves from thierselves
[11:51] <magicaltrout> like Go?! ;)
[12:01] <kjackal> I think the story goes like this: In begining there was C. Then developers got annoyed by junior developers that were clumsy with C and they created Java for the Junior devs to play with. But then Java became too popular and quantity beat quality: It was better to have more Java junior devs that few quality C devs. One C dev said I will reboot C and add some of the features I am missing so we have Go. While most C devs are
[12:01] <kjackal> boosting C
[12:01] <kjackal> magicaltrout: ^
[12:01] <magicaltrout> lol
[12:02] <magicaltrout> yeah, i suspect you're not too wide of the mark kjackal
[12:22] <rock> Hi all. we pushed our juju charm to public charm store using launchpad juju account. when we pushed it is giving like  cs:~hareeshk/kaminario-cinder-10 . It was pushing with account username "hareeshk".  Can we push our charm by hiding "username". Please provide me information.
[12:33] <magicaltrout> rock: to do that you have to get it signed off and "recommended" by some of the charmers
[12:34] <magicaltrout> so you need to ensure it has tests, tests pass, a decent README etc
[12:34] <magicaltrout> then it will need to enter the review queue
[12:41] <rock> magicaltrout: Hi. Oh. For that it requires the certification right.
[12:42] <magicaltrout> well its not certification, they just check to make sure your charm is sane
[12:43] <kjackal> rock: https://jujucharms.com/docs/2.0/charm-review-process
[12:44] <magicaltrout> doesn't seem to explain how to get it in the review queue though kjackal
[12:49] <rock> Kjackal/magicaltrout :  Thanks.
[12:50] <marcoceppi> rock kjackal http://review.jujucharms.com
[12:54] <rock> marcoceppi: Thanks. How much time it will take to review?
[12:54] <marcoceppi> rock: we're a little behind, but we'll try to take a look quickly
[12:56] <rock> marcoceppi: OK. Thanks.
[14:25] <bdx> marcoceppi: yeah ... this is really defeating .... the jenkins you posted doesn't even show up in the charm store ... is in not published for some reason?
[14:25] <marcoceppi> bdx: it just landed
[14:25] <marcoceppi> I'm really sorry man
[14:25] <bdx> jesus
[14:25] <marcoceppi> we're not going to cock this up again
[14:26] <marcoceppi> you can expect us announcing the charms and layers we're working on, from the entire company, much earlier
[14:26] <bdx> entirely
[14:31] <bdx> possibly we could make an addition to charm build where on every build it would post the charm name and author name/email to and endpoint somewhere
[14:31] <bdx> or something of that fashion
[14:35] <bdx> marcoceppi: why not target xenial on that?
[14:37] <marcoceppi> bdx: we are
[14:37] <marcoceppi> we will target xenial only for that charm, I'm building and uploading now
[14:47] <marcoceppi> bdx: I feel soo bad, but I should check now - what other charms/layers you got in the works? I want to make sure we don't curb stomp your dreams
[14:48] <bdx> marcoceppi: no worries, practice makes perfect
[14:49] <bdx> marcoceppi: zuul, gitlab, documize, etherpad-lite, mailman3
[14:49] <bdx> marcoceppi: I've yet to start on zuul
[14:49] <marcoceppi> bdx: yeah, I'm interested as well in gitlab, and I know Tom Barber has a start of that somewhere
[14:50] <bdx> marcoceppi: documize, etherpad-lite, mailman3 are done minus tests
[14:50] <marcoceppi> otherwise, i'm not awayre of any of those in flight
[14:50] <bdx> ok
[14:50] <bdx> I only have a start on gitlab too
[14:50] <jhobbs> beisner: do you'll have anything around zuul?
[14:51] <bdx> I should the trout about that for sure
[14:51] <bdx> magicaltrout:^
[14:52] <bdx> marcoceppi: I have a reactive rewrite of kibana I've been deploying .... but I'm guessing the whole elastic stack should be consuming a base layer of some sort eh?
[14:52] <beisner> jhobbs, only via integration with upstream gerrit + zuul.  we don't have our own zuul deployed though.
[14:52] <marcoceppi> bdx: dude, that's awesome! we were jsut about to start moving elasticsearch to 5.0.0 and layered!
[14:52] <marcoceppi> bdx: where's your kibana?
[14:53] <bdx> https://github.com/jamesbeedy/layer-kibana
[14:53] <marcoceppi> \m/
[14:53] <marcoceppi> lazyPower: ^^
[14:54] <lazyPower> thats great news \o/
[14:59] <bdx> here are another few layers I've hacked up recently
[14:59] <bdx> https://github.com/jamesbeedy/layer-nginx-passenger
[14:59] <bdx> https://github.com/jamesbeedy/layer-postfix
[15:00] <bdx> https://github.com/jamesbeedy/layer-git-deploy
[15:00] <bdx> https://github.com/jamesbeedy/layer-apache2
[15:00] <bdx> https://github.com/jamesbeedy/layer-phalcon
[15:00] <bdx> https://github.com/jamesbeedy/layer-consul-base
[15:02] <lazyPower> bdx - we should seriously, sync and divvy up the work on the elastic stack
[15:02] <lazyPower> bdx - the goalpost got moved on me, and its not coming as soon as I was hoping. I'm wiling to put in some time if you are to split that work up and deliver the 5.0 elastic stack
[15:03] <bdx> lazyPower: fully down man .... I've been training up a two man charming team at work ... few hours a day ... its been great all around
[15:03] <bdx> we would be interested in teaming up on that
[15:03] <bdx> for sure
[15:03] <lazyPower> word, calendar sync on thursday then to meet/greet and figure out what we need to do?
[15:03] <lazyPower> i have some early planning docs that i need to fish up and dust of
[15:04] <bdx> totally .... I'm in palm springs till sunday and wont be around much, lets shoot for next week sometime
[15:04] <bdx> monday?
[15:04] <lazyPower> that sounds even better
[15:05] <lazyPower> i may need to resched due to having team members at kubecon, i'll be running support for them
[15:05] <lazyPower> but tentatively that sounds great to me
[15:05] <bdx> sweet!
[15:05] <lazyPower> excellent :)
[15:06] <lazyPower> bdx preferred time?
[15:06] <bdx> 9am my time
[15:06] <bdx> so like an hour from now
[15:06] <bdx> does that work for you?
[15:07] <bdx> want me to send you a calendar invite?
[15:08] <lazyPower> bdx  you've got mail
[15:32] <bdxbdx> Marcoceppi: do you also have a Jenkins-slave going on?
[15:33] <bdxbdx> marcoceppi: having Jenkins and Jenkins slave on xenial will be huge .... Lxd local provider + juju 2.0 can't really happen
[15:33] <bdxbdx> On any other series
[15:34] <bdxbdx> For Jenkins <-> juju ci pipelines I'm thinking it will be crucial to have this
[15:43] <lazyPower> bdx - there's an open jenkins layer review we could use your eyeballs on
[15:44] <lazyPower> ooo and to my surprise its already landed
[16:11] <bdx> lazyPower, marcoceppi: not sure I can accept the invite -> https://s12.postimg.org/8lcvygobx/Screen_Shot_2016_11_02_at_9_10_36_AM.png
[16:11] <bdx> its on my calendar though
[16:32] <bdx> nm, git it,  accepted
[16:32] <lazyPower> solid
[16:32] <lazyPower> bdx - should we make this a hangout on air and invite the community at large?
[16:33] <lazyPower> i can also reach out to my contacts at elastic to see if they are interested in participating from a curious onlooker position. They might be able to lend a body for planning and insights.
[16:33] <bdx> lazyPower: totally
[16:33] <bdx> lazyPower: my guys over here want to be part of this too
[16:34] <lazyPower> bdx ok, let me see what i can do when jcastro surfaces. He's got all this down to a science
[16:34] <lazyPower> thanks for agreeing to help chair this effort :)
[16:34] <lazyPower> magicaltrout - if you're interested, you're invited toooooo
[16:35] <jcastro> who needs help?
[16:36] <magicaltrout> i'm always interested in taking on yet more unpaid work! ;)
[16:37] <jcastro> lazyPower: hangouts on air went away, the tldr is you'd do it on youtube like how with gaming.youtube
[16:37] <jcastro> there's a little panel for livestreaming, etc.
[16:38] <lazyPower> ahhh
[16:38] <lazyPower> magicaltrout - well i didn't mean it like that, but i appreciate the sentiment :D <3
[16:38] <magicaltrout> lol
[16:38] <magicaltrout> whatever :P
[16:38] <lazyPower> magicaltrout - i was just thinking you likely have a stake in this as its solving little data problems too
[16:39] <magicaltrout> this is true
[16:39] <magicaltrout> i've been abusing people at work recently over elastic stuff
[16:39] <jcastro> man this new kibana looks so sweet though
[16:39] <lazyPower> i'm
[16:39] <lazyPower> sayin
[16:39] <lazyPower> they did a bang up job on the 5.0 release
[16:40] <jcastro> it's like, I don't even want to use the old one at all anymore
[16:41] <bdx> jcastroyeah, we all want it
[16:41] <lazyPower> sorry they kept teasing me with getting to work on that stack :\
[16:41] <lazyPower> we had other bigger ticket items
[16:42] <admcleod1> dont forget fast data
[16:42] <lazyPower> soooo free time it is :D
[16:42] <lazyPower> admcleod1 - que?
[16:42] <admcleod1> big, little and fast data
[16:42] <magicaltrout> fast big data?
[16:42] <lazyPower> is there a slow data too?
[16:42] <magicaltrout> absoutely
[16:42] <lazyPower> what about obtuse data vs acute data? now we just sound classist.
[16:42] <magicaltrout> have you ever been introduced to Map Reduce?
[16:42] <admcleod1> irc is pretty slow data
[16:42] <lazyPower> once
[16:42] <lazyPower> it was horrible
[16:43] <magicaltrout> MapR is about as admcleod1 on a good day
[16:43] <lazyPower> ooooo
[16:43] <jrwren> databased on filesystems backed by remote block devices over gigabit is slow data.
[16:43] <admcleod1> he's such a snuggly bunny
[16:43] <magicaltrout> currently i'm dealing with TB's of data... on NFS
[16:44] <magicaltrout> now that is slow data
[16:44] <lazyPower> magicaltrout - did you use glusterfs-nfs or just plain ole nfs?
[16:44] <magicaltrout> oh, pretty much what jrwren said :)
[16:44] <magicaltrout> lazyPower: not my call, plain NFS
[16:44]  * lazyPower nods
[16:44] <magicaltrout> either way, if you want fast data, don't store it on NFS
[16:44]  * lazyPower pins that message to the channel
[16:45] <magicaltrout> well the other day I got someone complaining that copying 100GB of data on an NFS cluster on EC2 took 1 1/2 hours
[16:45] <jrwren> 4.9 kernel adds supoprt for NFS4.2 COPY... so you can look forward to that speed up ;]
[16:45] <magicaltrout> this is correct! then doing it on a machine locally took a few seconds
[16:46] <lazyPower> evilnickveitch - did we get 2.0.1 release notes? i thought i saw a merge email fly by on friday but i cant seem to find it
[16:46] <jrwren> magicaltrout: was it EBS backed? EBS can be very slow sometimes.
[16:46] <magicaltrout> yeah jrwren
[16:47] <admcleod1> magicaltrout: have you tried fastnfs?
[16:47] <magicaltrout> my Sys Admin guy is putting his eggs into the Amazon EFS basket and waiting to migrate to that
[16:48] <magicaltrout> you making up words again admcleod1 ?
[16:48] <bdx> he is
[16:48] <magicaltrout> thanks
[16:48] <admcleod1> yes, yes i am
[16:48] <bdx> made me look
[16:48] <bdx> jerk
[16:48] <magicaltrout> hehe
[16:49] <evilnickveitch> lazyPower, not any that made their way to docs - I think it was just an email to the list. i will check into that
[16:49] <lazyPower> ok thanks, i must have conflated the mail to the list with a doc pr. :) my b
[16:52] <evilnickveitch> lazyPower, there was a doc PR to update the sources for the new release, but no notes, so your brain isn't that wonky
[16:52] <lazyPower> evilnickveitch - how much longer before i've earned the 'mad scientist' badge?
[16:52] <lazyPower> s/before/until/
[16:53] <evilnickveitch> I think you are halfway there
[16:53] <lazyPower> \m/,  yesssss
[17:01] <admcleod> halfway to zeno maybe
[17:52] <jcastro> stokachu: battlemidget!
[17:52] <jcastro> have you tried doing conjure-up, juju, and lxd all from snaps?
[18:47] <stokachu> jcastro: yea it doens't work
[18:47] <stokachu> not easily anyway
[18:49] <stokachu> jcastro: https://github.com/conjure-up/conjure-up/tree/master/snapcraft thats our snap build stuff
[18:49] <stokachu> havent ran it in a bit though
[18:54] <jcastro> yeah, the one I'm using is also trying to launch observable kubernetes
[20:11] <deanman> Is docker charms supported with localhost LXD setup? I've tried both the 'observable-swarm' and 'swarm
[20:11] <lazyPower> deanman - those bundles are old, but in short, that configuration is not supported today
[20:12] <lazyPower> deanman - there is work being done to make running docker containers in lxd a better story, right now you can even pilot some of that manually with lxd profiles (the lxd docker profile is available in newer lxd packages) but you'll still find a lot of limitations there
[20:13] <deanman> lazyPower: Can you suggest a working charm to test docker locally using Juju or only safe bet is using some cloud infrastructure?
[20:13] <lazyPower> deanman - the only way you can achieve a layer-docker based charm working locally today is to use a VM backed substrate like KVM or VirtualBox (both on the manual provider, RIP KVM provider) so a majority of the work on those charm are performed in the cloud on aws/gce/azure
[20:15] <deanman> lazyPower: Thanks for the hints!