[00:00] petevg: https://github.com/juju-solutions/layer-apache-zeppelin/pull/13 [01:01] greets [01:03] return greetings pragsmike [01:03] beta18! [01:04] on the way [01:04] how long does it usually take before a release winds up in http://ppa.launchpad.net/juju/devel/ubuntu [01:04] pragsmike: few hours for things like getting launchpad builds and such [01:04] k [01:05] streams sync/etc [01:05] is there a picture somewhere of that process [01:05] it sounds cool [01:05] not that I've got handy unfortunately [01:06] it's part magic heh [01:15] rick_h_ - at some point, you should give a talk over our release pipeline for juju [01:16] as a lightning talk :) [01:16] lazyPower: hah, I see what you did there :P [01:17] i do try :D [12:31] It's not just you! http://streams.canonical.com looks down from here. [12:40] pragsmike: try now [12:45] ok, that's reachable now, thanks [13:48] sad to report that even with beta18 my containers still end up on the lxdbr0 bridge, and not on br-eno1 [13:50] i'm trying again, this time with MAAS 2.0.0+bzr5189-0ubuntu1 as Dimiter said he hadn't tested with MAAS 2.1.0 alpha yet [14:40] MAAS 2.0 from stable won't even successfully deploy the machine to run the juju controller, curtin hangs forever on "install kernel" [14:40] so i'm going back to MAAS 2.1 === rmcall_ is now known as rmcall