=== frankban is now known as frankban|afk === natefinch-afk is now known as natefinch === frankban|afk is now known as frankban [10:20] argh balls [10:20] as if i'm double booked for juju talks [10:20] how is that possible?! [13:37] 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] bradm: You're listed as maintainer of that one [14:00] 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] stub, thanks [15:01] 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] Also, is there a way to delete a user? Not just disable; I want to be able to reuse the name for testing purposes. === zeus is now known as Guest58260 === Guest58260 is now known as zeus` === zeus` is now known as zeus [15:34] @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.) === JoseeAntonioR is now known as jose === macgreag1ir is now known as macgreagoir [16:40] 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? === scuttle` is now known as scuttlemonokey === scuttlemonokey is now known as scuttlemonkey === frankban is now known as frankban|afk [17:56] mbruzek: how are you installing bundletester? - I can't get past the cheetah dep on trusty or xenial ... `pip install bundletester` fails [17:56] on the cheetah dep [18:03] mbruzek: hmmm, ok, a fresh trusty container, and it installed correctly .... strange [18:22] 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] bdx: it'll work next week [18:23] it actually works now if you run it in charmbox:latest [18:23] lazyPower: is that the right tag? ^ [18:24] tvansteenburgh - its in charmbox:devel, but he'll need to grab the deps. we didnt publish a tag [18:24] oh ok [18:29] tvansteenburgh, lazyPower: on it, thanks guys [19:08] i should do that though === freyes__ is now known as freyes [19:49] wait wat? lazyPower, charmbox:devel will soon have bundletester back? [19:49] kwmonroe - well, it technically has it now... but you have to manually upgrade some components [19:50] 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] kwmonroe https://github.com/chuckbutler/charmbox/commit/9e917fb4d43e91149870e3fdf6070b708d641a65 [19:55] sorry kwmonroe - i cleaned that up for legibility -- https://github.com/chuckbutler/charmbox/commit/cfa3b42b0ed74fded798f0b172881dedf2a202bc [20:03] bdx tvansteenburgh - i just pushed lazypower/charmbox:beta-12 -- if you want to test with bleeding edge, that was just pressed ~ 5 minutes ago === natefinch is now known as natefinch-afk [21:13] marcoceppi: I think I have some stale controllers bootstrapped in my aws charm dev account, would you mind clearing them for me? [21:14] http://paste.ubuntu.com/20507893/ :-( [21:38] bdx: I will later tonight, thnaks for the heads up [21:53] thank you [22:06] lazyPower: amulet [22:07] amulet hasn't been refactored for 2.0 yet has it? [22:07] bdx - i have all the latest deps put together for you in a container already :) [22:07] bdx lazypower/charmbox:beta-11 [22:07] er beta-12 [22:08] lazyPower: I'm running it [22:08] otherwise, you'll need to fetch tip from the following: bundletester, amulet, deployer, jujuclient [22:08] and install them in that order [22:08] 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] ahh, so https://github.com/jamesbeedy/layer-kibana/blob/master/tests/tests.yaml [22:09] would bring her down [22:09] ? [22:09] yep [22:10] ok, thats whats up then [22:10] 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] bah [22:10] ok [22:10] sorry its hinky but we're mid-flight, packaging solves this [22:10] for the sake of finishing what I set out to do today [22:11] no worries. [22:11] perfect [22:11] thanks for your help today [22:11] anytime :) [22:11] anything else before i run off for the weekend? [22:12] magicaltrout - get some rest :) Big weeks coming up for you. Try to enjoy your weekend [22:12] nah, I'm going to try to take some time away from the screen myself this weekend [22:13] thanks tho - enjoy [22:13] :) awesome. see you on Monday then [22:13] cheers [22:54] With juju Relations between charms what's the convention when a port needs to be exposed? [22:54] 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] Is there a way to expose ports in relation hooks?