[00:06] <lazyPower> magicaltrout :)
[00:08] <magicaltrout> lazyPower: as a  non employee showing those slides of mark makes my life so  much more entertaining ;)
[00:08] <magicaltrout> ironically i was the last talk of the night
[00:10] <jrwren> brexit was cool if all you care about is your currency purchasing power when you visit UK.
[00:12] <magicaltrout> hey jrwren i get paid in USD... if i ignore the political side of it, i'm fine ;)
[00:12] <magicaltrout> i dont' visit the uk either, I live there.. being english n'all ;)
[00:15] <jrwren> so... if you live in UK and get paid in USD... you got a pretty hefty raise when the pound sunk?
[00:15] <magicaltrout> yeah
[00:15] <magicaltrout> i voted remain..
[00:15] <magicaltrout> shows what i know
[01:23] <blahdeblah> Anyone around to give me some initial feedback on https://code.launchpad.net/~paulgear/charm-helpers/nrpe-service-immediate-check/+merge/300682 ?
[01:24] <blahdeblah> I'm not quite sure if I've updated the test suite correctly.
[05:14] <stub> arosales: I have already set up a new nrpe upstream - https://bugs.launchpad.net/charms/+bug/1603891
[05:14] <mup> Bug #1603891: Promulgate cs:~nrpe-charmers/nrpe <Juju Charms Collection:New> <https://launchpad.net/bugs/1603891>
[05:17] <stub> gnuoy: There is nothing to review in the prereq branch - it is just pulling in updated charmhelpers
[05:18] <stub> cory_fu, bdx : That charm is just cs:trusty/storage (the storage subordinate) with an updated series. I use it for testing PostgreSQL with Xenial.
[05:42] <bdx> stub: does it currently support aws ?
[05:54] <stub> bdx: I don't know. I just use it for testing locally. The storage subordinate (cs:storage) is dumb. The actual backend integration is done by https://jujucharms.com/block-storage-broker/. So whatever it supports.
[05:55] <stub> It claims to support EC2
[05:55] <bdx> totally
[06:03] <bdx> stub: I can't seem to get it to work .. no one else can verify that it works ... would you mind giving it a wherl using aws if you get a chince?
[06:03] <bdx> chance*
[06:06] <stub> I'm not setup for aws.
[07:16] <gnuoy> stub, merged. Shall I create a mp for updating maintainer in metadata.yaml ?
[07:16] <stub> gnuoy: That is https://bugs.launchpad.net/charms/+bug/1603891 really.
[07:16] <mup> Bug #1603891: Promulgate cs:~nrpe-charmers/nrpe <Juju Charms Collection:New> <https://launchpad.net/bugs/1603891>
[07:18] <gnuoy> stub, ok. Are you going to sync the lp branch over to the github one since I've just merged your mp into the lp branch?
[07:19] <stub> gnuoy: There is a github branch? I created a git branch on lp.
[07:19] <gnuoy> stub, oh, sorry, misread the bug
[07:19] <stub> I can resync
[07:19] <stub> (or can I?)
[07:19] <gnuoy> stub, Are you going to sync lp-bzr branch to lp-git branch ?
[07:19] <gnuoy> sorry, out-of-sync
[07:19] <gnuoy> ack
[07:20] <stub> I was hoping to have this promulgated last week
[08:00] <stub> gnuoy: resynced
[10:00] <parad0xz> hi!!
[10:00] <parad0xz> is there any tutorial how to install juju on maas on ubuntu 16 xenial?
[10:00] <parad0xz> because as I understand things have changed
[10:54] <parad0xz> how to setup juju on maas 2??!!
[11:35] <Shruthima> Hello Team,
[11:36] <Shruthima> can anyone suggest on these issue https://github.com/juju/amulet/issues/141?
[12:05] <Shruthima> Hello Team, Can anyone suggest how to resolve these issue  https://github.com/juju/amulet/issues/141 ?
[12:24] <Shruthima> tvansteenburgh: Hi, Can anyone suggest how to resolve these issue  https://github.com/juju/amulet/issues/141 ?
[13:15] <shruthima> Hello Team, Can anyone suggest how to resolve these issue  https://github.com/juju/amulet/issues/141 ?
[13:18] <lazyPower> shruthima - The tool merges referenced in that bug are still in flight and have not landed as best i can tell. We will certainly update bug 141 on amulet when everything has landed and is easy to install/upgrade. right now its a manual process and unless you know what you're doing can leave you in an inconsistent state.
[13:18] <mup> Bug #141: Revisions created with baz 1.1 are corrupt after archive-mirror <Baz (deprecated):Won't Fix> <https://launchpad.net/bugs/141>
[13:18] <lazyPower> thanks mup
[13:19] <shruthima> oh k Thankyou lazypower :)
[13:20] <godleon> hi all, is juju 2.0 + OpenStack with HA ok now ?
[13:20] <lazyPower> godleon - juju 2.0 is still in beta
[13:21] <godleon> I just tried to deploy mitaka openstack with HA(use HAProxy) by juju 2.0 and maas 2.0, but it seems not worked properly.
[13:21] <godleon> lazyPower: so......not suggest use juju 2.0 to deploy openstack ?
[13:22] <lazyPower> godleon - we dont currently recommend production deployments for 2.0 until its released as GA
[13:22] <lazyPower> otherwise, go for it :)
[13:23] <godleon> lazyPower - ok, but...... can juju 1.25 deploy OpenStack mitaka with HA ?
[13:23] <lazyPower> I do believe we have several mitaka HA deployments in the wild deployed with 1.25 yes
[13:27] <godleon> lazyPower - oh......do you have bundle configuration could be reference.....?
[13:29] <lazyPower> godleon - there's a couple options here. you can use autopilot (this ships with landscape) to build and deploy a custom openstack configuration. Or you can use the openstack base bundle  - https://jujucharms.com/openstack
[13:31] <godleon> lazyPower - yap, I have tried base bundle, it can work. But I can not find OpenStack with HA example on charm store. So I tried to add haproxy charm for every openstack service, but the result did not work properly.
[13:32] <godleon> lazyPower - So that's the reason I ask if there is Openstack with HA bundle configuration for reference.
[13:34] <lazyPower> Well that's the rub godleon, some of that is highly dependent on your infra and how that is setup. A bundle for ha I don't think is one size fits all. We could use more examples sure but I know a lot of effort has been taken with autopilot to make modeling that easy.
[13:35] <lazyPower> If that's not an option, I would recommend mailing the juju list to see if someone can share their bundle or lend a hand. I'm pretty sure we have some write ups on this subject but my Google fu is failing
[13:41] <godleon> lazyPower - hmm... got it. Thanks for your suggestion. I will talk about this with my coworkers. :)
[13:42] <lazyPower> Godleon: np. Highly recommended you ping the list though. A lot of our open stackers are still busy with the rollover from becoming an official project upstream. So chances are your question will be answered there once they see the post
[13:43] <lazyPower> And as always were here to help and guide you in the mean time :)
[13:44] <godleon> lazyPower - Good point! I'll take your advice, thank you very much! :)
[13:59] <godleon> Can juju 1.25 combined with MAAS 2.0 rc2? I can not even bootstrap after setting the environment.
[14:02] <lazyPower> godleon - juju 1.25 does not support maas 2.0
[14:03] <lazyPower> i missed that portion of your question, i apologize. When you asked if 1.25 would work with mitaka i didn't connect you were using a maas 2.0
[14:03] <godleon> lazyPower - oh......my....god... :(
[14:03] <magicaltrout> now you've gone and done it lazyPower .....
[14:04] <godleon> lazyPower - that's ok. I can reinstall MAAS 1.9.3
[14:04] <lazyPower> i know, this is all clearly my fault magicaltrout
[14:04] <lazyPower> i should be flogged
[14:04] <magicaltrout> hehe
[14:05] <magicaltrout> in the stocks for you!
[14:06] <lazyPower> http://www.reactiongifs.com/wp-content/uploads/2012/11/chicken_regret_nothing.gif
[14:06] <magicaltrout> thats making me dizzy
[14:08]  * lazyPower underlines the text 
[14:29] <magicaltrout> woop after 3 weeks of messing around with stupid sysadmin rules we finally have our docker based CI/CD environment setup on our Genomics project
[14:29] <magicaltrout> now I just need to convince them to use Juju ;)
[14:31] <lazyPower> not bad magicaltrout
[14:31] <lazyPower> what did you backend it with? swarm, k8s, or dc/os?
[14:31] <magicaltrout> swam for now
[14:32] <magicaltrout> i have a DC/OS  plan in the works but I need to get onsite to chat with the guys so i'll probably try and figure that lot out when Im out in pasadena
[14:33] <magicaltrout> i had a chat with Bill today, this type of stuff is exactly what projects like this one I'm on need. I need to be able to deploy the same stuff on my laptop, on another developers laptop, in the public dev system or in production without changing loads of stuff
[14:33] <magicaltrout> whether thats done with Juju, LXD, Docker etc, doesn't really matter, but until we did this there was just the worlds largest puppet script and a 30 minute build to dev only system
[14:33] <magicaltrout> you couldn't stand this stuff up locally
[14:34] <magicaltrout> and there  are 100's of projects like this that would benifit wildly from CI/CD container development
[14:37] <magicaltrout> as  a slight aside lazyPower you know you can run k8s on DC/OS?
[14:37] <lazyPower> in a meeting, bbiaf
[14:37] <magicaltrout> :'(
[14:37] <magicaltrout> no one to talk rubbish to
[14:38] <magicaltrout> http://kubernetes.io/docs/getting-started-guides/dcos/
[14:39] <jrwren> magicaltrout: i'll listen. so... why would I run k8s on dc/os? does it use dcos features? what features?
[14:40] <arosales> stub: gnuoy for nrpe we still need to add a series to the metadata yaml, then ping in here to have a ~charmer promulgate once you have pushed you latest version
[14:41] <magicaltrout> jrwren: i don't have a real answer as for the "why", choice I guess :)
[14:41] <magicaltrout> they did write a pretty good blog post about it
[14:41] <magicaltrout> https://mesosphere.com/blog/2015/09/25/kubernetes-and-the-dcos/
[14:42] <jrwren> whoa, 10 months ago!
[14:42] <jrwren> i'm so behind the times.
[14:43] <magicaltrout> lol
[14:43] <magicaltrout> don't worry i havve this presentation at mesoscon in a month with charms that don't fully work yet
[14:43] <magicaltrout> i'm the one behind ;)
[14:56] <lazyPower> magicaltrout - its typically for marathon support
[14:56] <lazyPower> people are in love with that scheduler
[14:56] <lazyPower> sorry jrwren ^
[14:57] <lazyPower> magicaltrout - there's an interesting crossover opportunity here, we could take the current k8s bundle and gank the scheduler in leu of marathon and release another bundler with both our work, whicih mightbcool
[14:57] <magicaltrout> yeah i was wondering that the other day lazyPower
[14:57] <magicaltrout> see how much of a crossover we can get
[14:58] <lazyPower> we can do it all G-funky, it just takes time
[14:58] <lazyPower> :)
[14:58] <jrwren> we could also make juju the best way to deploy dcos
[14:59] <magicaltrout> jrwren: we already have one of their guys interested for DC/OS MAAS deployments
[14:59] <magicaltrout> so there is certainly an opportunity there
[15:00] <bladernr> Hye, what's the trick for making juju 2.0 talk to MAAS 2.0?
[15:00] <bladernr> ISTR there was something specific you had to do to enable it...
[15:00] <bladernr> but can't remember what that was.
[15:01] <magicaltrout> jrwren: apart from some random config stuff i need to put into actions, the only real big issue with my charms currently is the unscalablility of master, other than that they work. But i need to get mesosphere on the hook to help with the packaging because I had to munch up their really weird installation procedure to build a deployable package
[15:04] <lazyPower> bladernr - unless i'm mistaken, beta-12 once you've added the cloud it just works with maas 2.0-rc2
[15:05] <bladernr> lazyPower, I followed this https://jujucharms.com/docs/2.0/clouds-maas#defining-maas-clouds
[15:05] <bladernr> but when I do an add-credentials, it complains that oauth is not supported
[15:05] <bladernr> ERROR auth type "oauth" for cloud "maas" not supported
[15:08] <bladernr> haha, nevermind... sheesh.  oauth != oauth1.  head->desk
[15:10] <magicaltrout> picnic!
[15:10] <lazyPower> bladernr  :) glad we got it sorted
[15:11] <bladernr> Yeah, I should probably put my glasses back on :/
[15:11] <lazyPower> also, cool nick :) how do we know you're not a replicant?
[15:11] <bladernr> That IS the question... I'm pretty sure the sheep I dream of are not electronic.
[15:12] <bladernr> because I like puppies?
[15:12] <lazyPower> I'll reserve judgement until you submit a charm/bundle for review
[15:13] <lazyPower> that'll tell me if you originate from the Tyrell corp or not
[15:26] <bladernr> Heh... my charm is weak.  All it does right now is install one package.  It needs some enhancement.
[15:27] <lazyPower> bladernr - if you're interested, we do office hours and it might b fun to have an interactive session during the office hours to peek at your charm and make suggestions. get some real time engineering support/face-time with charmers
[15:28] <bladernr> perhaps, we'll see what happens (I'm about to go on vacation, so focusing on this is becomming difficult).
[15:28] <magicaltrout> come to pasadena \o/
[15:28] <lazyPower> i completely understand that too
[15:28] <lazyPower> and as magicaltrout suggested, there's also a charmer summit coming up - http://summit.juju.solutions
[15:28] <bladernr> Yeah, I actually would LOVE to attend a charmer summit (I missed the one in Feb)
[15:29] <bladernr> but that one happens to end the day before I fly to .EU for a family trip
[15:29] <magicaltrout> sod the family... ! ;)
[15:29] <lazyPower> bummerrrr, scheduling conflicts :(
[15:29] <bladernr> magicaltrout, I could say that, but my wife would be ... displeased... besides, charmer summit in Pasadena vs 5 days in London and 6 days in Malta?  really no choice there.
[15:30] <magicaltrout> hmm malta seems acceptable
[15:30] <magicaltrout> I can vouch for london being nothing special ;)
[15:31] <bladernr> Well, she's never been to London.  I can agree with you there.  But I LOVE Malta, I'd live there if I could.  heh
[15:31] <magicaltrout> hmm
[15:31] <magicaltrout> might have to pay it a visit then
[15:31] <magicaltrout> London's okay, Im just messing, I live about an hour outside. Certainly there is plenty to do for families
[15:32] <magicaltrout> all the free museums, old stuff etc
[15:32] <lazyPower> Malta is tons of fun
[15:32] <lazyPower> i really enjoyed our sprint there
[15:33] <bladernr> Yeah, I actually like London, it's fun, but ulitmately, it's just another large city.  They're all basically the same, with different wrappers and accoutrement
[15:33] <bladernr> lazyPower, yeah, me too, I spent an extra week after just to explore it.  Hence the trip back now with the spousal unit.
[15:34] <lazyPower> All the Tolkein bars ^_^  but i think thats around oxford
[15:41] <lazyPower> magicaltrout - i'd like to be pro-active about talking to you re dc/os efforts. when your schedule has settled to where we can find a half hour to kick off, we should do that. I'd like to bring along mbruzek too as he's my co-pilot with containers
[15:42] <magicaltrout> indeed lazyPower sounds good
[15:42] <magicaltrout> i'll get this master charm squared away so its usable, and then we can figure out where to go next
[15:44] <lazyPower> well i have ulterior motives to try and fold you into the /u/containers namespace :)
[15:44] <lazyPower> because we <3 community contributions
[17:21] <mattrae> hi, with juju 2.0 is it possible to deploy a service to a controller? previously with 1.x i could deploy --to 0 which would put services on the controller
[17:25] <bladernr> mattrae, I was about to ask that exact question.
[17:26] <bladernr> I tried with --to=<controller name> but that didn't seem to work
[17:26] <bladernr> it accepted that, but failed to deploy...
[17:26] <mattrae> bladernr: ahh cool, i haven't tried that yet
[17:31] <mattrae> bladernr: ah ok i'm getting an error as well 'cannot run instance: No available machine matches constraints: name=jumpiest-yuko'. the node is already deployed and its not realizing its the controller
[17:41] <lazyPower> mattrae  you can
[17:41] <lazyPower> mattrae - juju switch admin && juju deploy foo --to 0
[17:41] <lazyPower> mattrae - in juju 2.0, the admin model is a reserved case, we dont recommend colocating on the controller, but if you want to - thats how you can do it. Note: you cannot relate anything to this application unless it too is deployed in the admin model
[17:45] <mattrae> lazyPower: thanks! we plan to have 3 controllers, but we want each of those controller nodes to have some services because they are big machines
[18:16] <bladernr> lazyPower, i'd prefer to run instances on the bootstrap node as well. I only have two physical nodes, and need to run one servince on one, and one on the other, and relate them.
[18:17] <bladernr> so juju switch admin && juju deploy foo --to 0 && juju deploy bar?
[18:17] <bladernr> which I think means foo goes on bootstrap node and bar goes on machine 1?
[18:23] <lazyPower> correct
[18:32] <bladernr> lazyPower, thanks
[19:02] <petevg> cory_fu, kwmonroe: I made some PRs for binding kafka to a non default interface, and kicked the ticket into review. I still need to write the same thing, but for Zookeeper, but I'd appreciate some feedback on the Kafka side. Does my approach look correct?
[19:27] <kwmonroe> petevg: got a pr link for me?  me too lazy to open the board
[19:28] <petevg> kwmonroe: there are three PR links, which is why I pointed you at the board :-p  Hang on ...
[19:28] <kwmonroe> no no petevg, i'm there now :)
[19:43] <lazyPower> bladernr mattrae - ah, for clarity, post beta-10 (i think) the admin model was renamed to 'controller' to better clarify that it's intended for juju internals. i just ran list-model and realized i was stale :)
[19:47] <magicaltrout> like an old biscuit
[20:22] <bladernr> So, dumb question, but how do you debug a hook in 2.0?
[20:23] <bladernr> AIUI, juju debug-hooks <unit> <hook> would open a tmux session in the unit in the hook context, yes?
[20:23] <bladernr> all I get now is just a root session and no ability to run hook tools or hooks manually.
[20:27] <magicaltrout> when the hook fires
[20:27] <magicaltrout> you'll drop into it
[20:27] <magicaltrout> i don't believe it's changed
[20:30] <bladernr> Hrmmm, ok.  All I get is a root login, and not dropped into it.
[20:52] <bladernr> hrmmm... ok, worked when "start" was called, but took several minutes before that happened.  How can you trigger a hook (outside of the debug console)?
[20:53] <magicaltrout> yeah so stuff like that works on a 5 minute timer
[20:54] <magicaltrout> ... and i'd tell you how to trigger it manually
[20:54] <magicaltrout> but the dev server i have isn't responding and its not in my bash history :):
[20:54] <magicaltrout> lazyPower: help me out here
[20:55] <magicaltrout> ah
[20:55]  * lazyPower reads backscroll
[20:55] <lazyPower> 1 sec, in/out of a meeting thats almost done
[20:55] <magicaltrout> juju run --unit ss/0 "hooks/install"
[20:55] <magicaltrout> or whatever
[20:55] <magicaltrout> is what you want bladernr
[20:56] <bladernr> magicaltrout, aiii, thanks
[20:57] <lazyPower> ok back
[20:58]  * lazyPower reads backscroll for real this time
[20:58] <lazyPower> ahhh no
[20:58] <lazyPower> juju run is executed in an anonymous hook context
[20:58] <lazyPower> that'll work for primary hooks like install/config-changed et-al
[20:59] <lazyPower> but you wont want to try a relationship hook that way, it'll fail on you every time, as it doesn't have the env setup for the conversation
[21:00] <lazyPower> bladernr - typically what we do, is either "break a hook" (not ideal) or attach and wait for the next hook execution. Its much easier to intercept the hoook you're intended to debug, if you break that hook so you can attach and juju resolved --retry application/unit.  We've got some older bugs referencing requests to execute hooks like so: "juju debug-hooks mysql/0 upgrade-charm" and it drops you in the upgrade-charm hook context, but it
[21:00] <lazyPower>  hasn't been addressed yet. Maybe some day when we're less focused on stabilizing 2.0 and putting the tint and chrome on the release.
[21:06] <lazyPower> magicaltrout - but decent hack :) i like it
[21:07] <magicaltrout> yeah i believe it came from cory_fu and kwmonroe
[21:08] <lazyPower> big data holding out on the good tricks these days eh?
[21:08] <lazyPower> typical cory_fu and  kwmonroe - silently genius
[21:08] <magicaltrout> thats lies
[21:08] <magicaltrout> i know that trick
[21:08] <lazyPower> lies, damn lies, and statistics
[21:09] <magicaltrout> because kwmonroe kept telling lies when writing the pdi charm
[21:09] <magicaltrout> and breaking stuff
[21:09] <lazyPower> well, i do a fair amount of breaking myself
[21:09] <lazyPower> just to be fair
[21:11] <kwmonroe> i didn't lie magicaltrout, i just made stuff up about how python worked.  totally different.
[21:13] <magicaltrout> lol
[21:14] <kwmonroe> hey petevg, the change to BIGTOP-1624 on bigtop base is just to bring it in-line with what we had upstream, right?
[21:14] <petevg> kwmonroe: correct.
[21:14] <petevg> ... and in line with the patch that is in master.
[21:15] <petevg> ... though the patch in resources/master should go away, now that we have it merged.
[21:35] <bdx> how does  __init__.py make it into lib/ on `charm build` ?
[21:37] <bdx> it seems, if lib/__init__.py doesn't exist in any layers included by the charm being built, then it never makes it to build/<charmname>/lib
[21:38] <bdx> this causes `charm build` to fail
[21:38] <bdx> :-(
[21:38] <kwmonroe> bdx: there's an __init__.py in layer-basic: https://github.com/juju-solutions/layer-basic/tree/master/lib/charms/layer
[21:39] <bdx> shoot
[21:39] <bdx> darn it
[21:39] <bdx> ooho
[21:39] <bdx> no
[21:39] <kwmonroe> bdx: you're talking crazy.. what's wrong?
[21:39] <bdx> kwmonroe: it needs to be in lib though right?
[21:39] <kwmonroe> charm build will pull it in
[21:40] <bdx> to lib/ ?
[21:40] <bdx> from where?
[21:40] <kwmonroe> assuming you include layer:basic in layer.yaml
[21:40] <kwmonroe> wait, you mean lib/__init__.py or lib/charms/layer/__init__.py?
[21:40] <bdx> lib/__init__.py
[21:42] <kwmonroe> hm.. bdx where are you seeing __init__ in ./lib?  is it possible you have a local layer-basic that didn't stick it in ./lib/charms/layer?
[21:43] <bdx> kwmonroe: omp, I'm grabbing you debug output
[21:45] <bdx> kwmonroe: paste.ubuntu.com/20366435/
[21:46] <kwmonroe> bdx: thanks for not making that link clickable
[21:47] <bdx> aha
[21:47] <bdx> http://paste.ubuntu.com/20366435/
[21:49] <kwmonroe> bdx: blow away /home/bdx/allcode/charms/builds/kibana first.. if you can
[21:49] <kwmonroe> then charm build it
[21:50] <bdx> #$(&*@
[21:50] <bdx> kwmonroe: that worked
[21:50] <bdx> kwmonroe: thx
[21:50] <bdx> my bad
[21:51] <kwmonroe> bdx: please deposit $11 into my paypal account
[21:51] <bdx> I didn't want to blow it away, bc its my .bzr
[21:51] <bdx> aha
[21:52] <bdx> kwmonroe: you rock
[21:53] <kwmonroe> bdx: if you want to keep a built charm in bzr, i suggest you 'bzr branch <foo> foo-bzr"
[21:53] <kwmonroe> then after every charm build, cp -a foo-bzr/.bzr foo
[21:54] <bdx> yea, thats where I figured this was headed ... ok
[21:54] <kwmonroe> that's not real syntax, but basially, copy the .bzr dir from your bzr charm to the output dir of your 'charm build' and you'll be able to bzr commit that
[21:55] <bdx> totally
[21:55] <bdx> ok
[21:55] <bdx> thanks man
[21:55] <petevg> kwmonroe: darn it. I think that I rebased my kafka-bind-address branch from master this morning, when I was troubleshooting, and that means bad things for merging back to the kafka branch :-(
[21:56] <petevg> Time to brush up on cherry picking ...
[21:59] <kwmonroe> bdx: consider the value of keeping a built charm in bzr (or any vcs).  we're not ingesting anymore, so when you 'charm push', you are basically preserving a copy of your charm..
[21:59] <magicaltrout> no one really wants to use  bzr...... ;)
[22:01] <lazyPower> bdx - yep kwmonroe is on to something there. The current charm push model is very much akin to an image based workflow, where your image is the assembled charm you've versioned in your namespace's charm stream.
[22:04] <kwmonroe> right, especially with layered charms.. the layer lives under some VCS, but the output of 'charm build' is what you 'charm push[; charm publish <x>]' to the store and is therefore locked to a point in time when you want that charm to be available.
[22:09] <kwmonroe> petevg: please don't worry about re-syncing the kafka branch with master
[22:09] <petevg> kwmonroe: that's exactly the opposite of what I'm worrying about.
[22:09] <kwmonroe> lol
[22:09] <petevg> I'm working on getting a version of my branch that won't introduce a bunch of muddled stuff from master.
[22:10] <petevg> I think that I have it -- cherry picking turns out to be simpler than I've always thought it to be.
[22:10] <petevg> I'm just re-running tests before I push, to make sure that I'm not introducing new bugs.
[22:11] <kwmonroe> petevg: i think the crux of the issues happened because master's 1624 patch wasn't in sync to begin with
[22:11] <petevg> kwmonroe: That's one of the problems, yes :-)
[22:11] <bdx> tracking
[22:12] <kwmonroe> whenever i find myself in these types of problems, i just commit, force rebase, take a few days off, and cory_fu seems to have it cleaned up when i return.
[22:12] <kwmonroe> i think he likes it
[22:12] <petevg> kwmonroe: new PR. It's a thing of beauty: https://github.com/juju-solutions/bigtop/pull/28
[22:14] <petevg> kwmonroe: I guess the other question is whether the puppet changes should still get merged to master or not (https://github.com/juju-solutions/bigtop/pull/27/files).
[22:15] <petevg> ... and that also ties into the discussion on the bigtop mailing list about how hard it is to figure out how to review our merges, with things split between PRs containing charms, and PRs containing patches to the puppet scripts.
[22:16] <petevg> For now, though, I've gotta EOD -- I'm on deck for dinner tonight. Catch ya later!
[22:16] <kwmonroe> petevg: i am firmly in the camp of PR 27 being redundant.
[22:16] <kwmonroe> we'll chat manana
[22:16] <kwmonroe> have a great dinner!
[22:33] <magicaltrout> dinner?!  I had a burger in the bar for the 3rd night out of 4 ;(
[22:54] <bdx> lazyPower: should I just iterate over the templates with *.spvsr.conf and extract the appname from them?
[22:54] <bdx> lazyPower: for layer-supervisor
[22:57] <magicaltrout> no one give bdx a new job
[22:57] <magicaltrout> he asks too many questions!
[22:57] <bladernr> hrmmm... another dumb question, how do you define the default series for a charm?  is series: in metadata.yaml valid?
[22:58] <magicaltrout> i believe it is bladernr
[22:58] <magicaltrout> i still use it at least
[22:58] <magicaltrout> some of it is all a bit weird thoug
[22:58] <magicaltrout> h
[22:58] <mgz> bladernr: it takes a list now
[22:59] <bladernr> ok.. I can keep using -s, but it makes more sense for me to learn how to do so (and i guessed that series: was a valid key)
[22:59] <magicaltrout> like pushing a multiseries charm is funky
[22:59] <bladernr> mgz, so... series: xenial,trusty
[22:59] <mgz> series:
[22:59] <mgz>   - xenial
[22:59] <mgz>   - trusty
[22:59] <bladernr> ahhh... yeah..
[22:59] <bladernr> thanks
[22:59] <mgz> first one is the default
[22:59] <magicaltrout> bdx: you planning to be in Pasadena?
[22:59] <bdx> you know it
[22:59] <bdx> magicaltrout: you?
[23:00] <magicaltrout> indeed. After your drunken night in ghent, i wouldn't miss it ;)
[23:00] <bdx> magicaltrout: baha thx
[23:00] <bdx> yea...
[23:01] <bdx> no
[23:01] <magicaltrout> also as a caveat although i live outside london, my office is really JPL in Pasadena, so I'm just combining a bunch of trips if  I can make it all align
[23:01] <magicaltrout> although my eldest kid starts school that week as well, so its going to be a rush
[23:01] <magicaltrout> as is my life
[23:06] <magicaltrout> actually bdx if you didn't see this you'll like it
[23:06] <magicaltrout> https://docs.google.com/presentation/d/1UdKSsuXpYSy25V9HuxnqgzQRmlC1DEtLJUgEY-5PDoc/edit#slide=id.g15623877ea_0_95
[23:06] <magicaltrout> i did a presentation yesterday with Mark in the room
[23:06] <magicaltrout> and unleashed this slide
[23:07] <magicaltrout> not sure if I'll be allowed into the charmers summit ;)
[23:07] <bladernr> YAY, charm is working!
[23:08] <magicaltrout> woop
[23:08] <bladernr> Ok, before I quit for the day... one last question... is there any way to set config on a per-unit basis?
[23:08] <magicaltrout> erm
[23:08] <bdx> magicaltrout: wow ... yea ... I was in the process of swapping out the job, woman, and house immediately before belgium .... errrgg I was hustling real hard around that time to finish school, maintain multiple openstacks, a damn dungeon dweller I was in the months preceding that event
[23:08] <bdx> I had no idea what that european vino would do to me
[23:08] <bdx> aha
[23:08] <magicaltrout> hehe!
[23:09] <magicaltrout> we should've got a video
[23:09] <bladernr> the charm I wrote is for iperf3, which can be run as either a server or a client.  I suppose the proper answer is to create two charms, one for each case, rather than one charm that can do both
[23:09] <magicaltrout> bladernr: if it makes you happier i do exactly that
[23:09] <magicaltrout> because config options will diverge
[23:10] <bdx> treacherous
[23:10] <bladernr> right... just wondering if two separate charms are more "proper".
[23:10] <bladernr> because right now, I can't just add-unit and then change the config on the new unit.
[23:10] <magicaltrout> bladernr: the other option is leader election etc, i don't know enough of what you're doing
[23:10] <magicaltrout> but it sounds like separate charms makes sense if you have server -> client stuff
[23:11] <magicaltrout> and yeah
[23:11] <magicaltrout> scale out will screw you as you seem to have noticed :)
[23:12] <bladernr> ack... I'm just happy it's finally working.  I can do more tomorrow.
[23:13] <bladernr> tonight is food, beer and then Star Trek
[23:13] <magicaltrout> never seen star trek
[23:13] <magicaltrout> not seen that other one...
[23:13] <magicaltrout> whats it called
[23:13] <magicaltrout> oh yeah
[23:13] <magicaltrout> star wars
[23:16] <lazyPower>  bdx - nah that sounds too magical. I did however miss this gem https://github.com/jamesbeedy/layer-supervisor/blob/master/layer.yaml#L5
[23:16] <lazyPower> i looked in the reactive module, saw the state and status, and grinned when there was no install bits there
[23:17] <lazyPower> and fwiw i retract that statement about moving it into the module. What you have there is bueno