[10:20] <magicaltrout> argh balls
[10:20] <magicaltrout> as if i'm  double booked for juju talks
[10:20] <magicaltrout> how is that possible?!
[13:37] <rcj> Is there a charmer who could do a quick review of an MP to restore function in the bip charm lost moving from precise to trusty?  7 line diff @ https://code.launchpad.net/~rcj/charms/trusty/bip/lp1604759/+merge/300585
[13:55] <stub> bradm: You're listed as maintainer of that one
[14:00] <stub> rcj: I've reviewed and merged it. It won't get in the charm store until the promulgation dances are done, which I think requires bradm since he is listed as the maintainer.
[14:01] <rcj> stub, thanks
[15:01] <ryebot> Is there some juju 2 command that will allow me to recover a registration key given a user name? e.g., if the originally provided key is lost
[15:02] <ryebot> Also, is there a way to delete a user? Not just disable; I want to be able to reuse the name for testing purposes.
[15:34] <petevg> @kwmonroe, @cory_fu: Pushed revised PRs for https://github.com/juju-solutions/bigtop/pull/27 and https://github.com/juju-solutions/bigtop/pull/28  lmk if they look good (I did re-run the tests, and they still pass.)
[16:40] <balloons> there's two juju-core packages sitting in -proposed for xenial. Could the package from 7/18 be rejected, and the package from today be accepted?
[17:56] <bdx> mbruzek: how are you installing bundletester? - I can't get past the cheetah dep on trusty or xenial ... `pip install bundletester` fails
[17:56] <bdx> on the cheetah dep
[18:03] <bdx> mbruzek: hmmm, ok, a fresh trusty container, and it installed correctly .... strange
[18:22] <bdx> mbruzek: I'm guessing bundletester doesn't work with 2.0 yet either, so I need to get a 1.x env setup .... grrr
[18:23] <tvansteenburgh> bdx: it'll work next week
[18:23] <tvansteenburgh> it actually works now if you run it in charmbox:latest
[18:23] <tvansteenburgh> lazyPower: is that the right tag? ^
[18:24] <lazyPower> tvansteenburgh - its in charmbox:devel, but he'll need to grab the deps. we didnt publish a tag
[18:24] <tvansteenburgh> oh ok
[18:29] <bdx> tvansteenburgh, lazyPower: on it, thanks guys
[19:08] <lazyPower> i should do that though
[19:49] <kwmonroe> wait wat?  lazyPower, charmbox:devel will soon have bundletester back?
[19:49] <lazyPower> kwmonroe - well, it technically has it now... but you have to manually upgrade some components
[19:50] <lazyPower> i was going to push a tag release so we could hack with it until it gets in the right spots and it just shows up in devel
[19:52] <lazyPower> kwmonroe https://github.com/chuckbutler/charmbox/commit/9e917fb4d43e91149870e3fdf6070b708d641a65
[19:55] <lazyPower> sorry kwmonroe - i cleaned that up for legibility -- https://github.com/chuckbutler/charmbox/commit/cfa3b42b0ed74fded798f0b172881dedf2a202bc
[20:03] <lazyPower> bdx tvansteenburgh - i just pushed lazypower/charmbox:beta-12 -- if you want to test with bleeding edge, that was just pressed ~ 5 minutes ago
[21:13] <bdx> marcoceppi: I think I have some stale controllers bootstrapped in my aws charm dev account, would you mind clearing them for me?
[21:14] <bdx> http://paste.ubuntu.com/20507893/ :-(
[21:38] <marcoceppi> bdx: I will later tonight, thnaks for the heads up
[21:53] <bdx> thank you
[22:06] <bdx> lazyPower: amulet
[22:07] <bdx> amulet hasn't been refactored for 2.0 yet has it?
[22:07] <lazyPower> bdx - i have all the latest deps put together for you in a container already :)
[22:07] <lazyPower> bdx  lazypower/charmbox:beta-11
[22:07] <lazyPower> er beta-12
[22:08] <bdx> lazyPower: I'm running it
[22:08] <lazyPower> otherwise, you'll need to fetch tip from the following:   bundletester, amulet, deployer, jujuclient
[22:08] <lazyPower> and install them in that order
[22:08] <lazyPower> additionally, if any of your amulet tests do something like apt-get install amulet or pip install amulet, the house of cards falls apart
[22:09] <bdx> ahh, so https://github.com/jamesbeedy/layer-kibana/blob/master/tests/tests.yaml
[22:09] <bdx> would bring her down
[22:09] <bdx> ?
[22:09] <lazyPower> yep
[22:10] <bdx> ok, thats whats up then
[22:10] <lazyPower> so, you can comment that out or just rm it while you get on with life until it lands in stable next week
[22:10] <bdx> bah
[22:10] <bdx> ok
[22:10] <lazyPower> sorry its hinky but we're mid-flight, packaging solves this
[22:10] <bdx> for the sake of finishing what I set out to do today
[22:11] <bdx> no worries.
[22:11] <bdx> perfect
[22:11] <bdx> thanks for your help today
[22:11] <lazyPower> anytime :)
[22:11] <lazyPower> anything else before i run off for the weekend?
[22:12] <lazyPower> magicaltrout - get some rest :) Big weeks coming up for you. Try to enjoy your weekend
[22:12] <bdx> nah, I'm going to try to take some time away from the screen myself this weekend
[22:13] <bdx> thanks tho - enjoy
[22:13] <lazyPower> :) awesome. see you on Monday then
[22:13] <lazyPower> cheers
[22:54] <linnn> With juju Relations between charms what's the convention when a port needs to be exposed?
[22:54] <linnn> I have a website charm and a database charm, so when I add the relation between the two the database port needs to be open.
[22:55] <linnn> Is there a way to expose ports in relation hooks?