[00:30] <Catalys> Whenever I do rebuild in Horizon, the OS doesn't seem to change or anything. Is this a known bug?
[11:56] <rick_h> lazyPower: ping when you're up and about please
[12:39] <lazyPower> rick_h: ping
[12:39] <rick_h> lazyPower: dude, how goes?
[12:40] <lazyPower> rick_h: i'm not sure, still working on the first cup of coffee :)
[12:40] <rick_h> lazyPower: can I steal 5min? I'll bring the energy, just finishing my first cup :)
[12:40] <lazyPower> sure 1 sec, i migrated laptops this weeekend, let me get signed into work services
[12:40] <rick_h> oooh, upgrade time?
[12:41] <lazyPower> its your old carbon ;)
[12:41] <rick_h> lol, awesome
[12:41] <rick_h> that thing is getting around :P
[12:42] <rick_h> lazyPower: I'm chillin in https://hangouts.google.com/hangouts/_/canonical.com/rick?authuser=1 when you get it worked out
[12:47] <magicaltrout> I was so happy to get rid of my old carbon
[12:53] <lazyPower> oh magicaltrout ?
[12:56] <magicaltrout> kids picked the keys off and you need new ones to replace them :)
[12:56] <magicaltrout> plus the screen res was pretty woeful ;)
[12:56] <lazyPower> the 1440 rez did throw me at first
[12:56] <lazyPower> but with i3 things scale pretty well
[12:57] <lazyPower> i3 is actually what brought me back to it from my crapple.
[12:58] <rick_h> I really liked it but it was too big when I was traveling like crazy
[12:58] <magicaltrout> Model name:            Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
[12:58] <magicaltrout> i got a dell instead
[12:58] <rick_h> of course I went too far with surface and that didn't last too long either
[12:58] <rick_h> magicaltrout: xps 13?
[12:58] <magicaltrout> 15
[12:58] <rick_h> biiiig
[12:59] <magicaltrout> its attached to 2 massive monitors, so in comparison its pretty small ;)
[12:59] <magicaltrout> the thunderbolt port to drive 2 hdmi outputs is pretty cool
[13:00] <rick_h> nice
[13:01] <magicaltrout> its also nice to not be on those embedded intel gfx chips as well
[13:01] <magicaltrout> not that i do much stuff thats 3d but they suck reasonably
[13:02] <lazyPower> yeah, i can understand that magicaltrout
[13:03] <lazyPower> my primary goal was to have a rig powerful enough to to day to day's and also not destroy my back when travelling
[13:03] <lazyPower> its a little underpowered in terms of being able to run a hangout AND run a deployment in lxd, but overall it does a decent job if i'm not really pushing it. And at the price point i picked it up at, it was almost a no brainer.
[13:08] <magicaltrout> i used to cycle to and from work 9 years ago with my laptop
[13:08] <magicaltrout> which was a 15inch Toshiba brick
[13:08] <magicaltrout> it used to weight a lot
[13:09] <magicaltrout> and I had a 15 mile each way ride over the yorkshire dales
[13:09] <magicaltrout> you just need to man up lazyPower ;)
[13:09] <lazyPower> i'll pass on the alpha goading :)
[13:09] <magicaltrout> ha
[13:09] <lazyPower> workouts are for the gym, not commutes
[13:10] <magicaltrout> i dunno, used to like feeling awake when i got to work compared to 90 mins on public transport
[13:16] <lazyPower> magicaltrout: this is why i walk every day after my morning meetings
[13:17] <lazyPower> I've been graphing this with google fit, which isn't a bad dashboard system for your health metrics
[13:17] <magicaltrout> from your office to the bathroom?
[13:17] <lazyPower> clever, :) only if thats a 2.3 - 3 mile hike
[13:17] <magicaltrout> nice
[13:17] <lazyPower> trying to turn it around broski
[13:17] <lazyPower> i've been lazy butt a bit too long
[13:48] <vlad_> Hey folks... quick question probably a simple answer.  If I'm deploying charms to a maas cluster... how much of the maas network configuration is exposed to those charms or does it override those previous settings completely?
[13:49] <vlad_> In this context I'm deploying the openstack base bundle to a set of maas nodes
[13:57] <rick_h> vlad_: so when you deploy you determine how the network is required. It doesn't really alter the network so much as leverage what's setup in maas as that's a hardwired setup.
[13:58] <rick_h> vlad_: you leverage spaces to control what containers on the machines are using which devices and such
[14:01] <vlad_> rick_h: First off thanks a ton! Secondly for example let's say I have a vlan in a space on a fabric with vlan tag 2030 and 10.203.2.0/24 as the CIDR. If I configure my juju charm to use that CIDR it will know to use the vlan?
[14:02] <vlad_> The specific charm configuration option only allows the use of a CIDR that's why I'm asking
[14:03] <rick_h> vlad_: so when you deploy are you specifying any binding of to a space name?
[14:03] <rick_h> vlad_: e.g. https://jujucharms.com/docs/2.1/network-spaces
[14:03] <vlad_> rick_h: The machines in question I have bound to the space, but I didn't see any configuration options in doing so from within the juju charm itself.
[14:04] <rick_h> vlad_: right, normally it's part of the deploy command or the bundle description.
[14:04] <rick_h> vlad_: so that Juju knows "this application needs to request (from MAAS) a machine with interfaces on these spaces.
[14:04] <rick_h> vlad_: and then Juju can tell the charm "you've been asked to bind to space X" and it can adjust appropriately based on that request
[14:05] <vlad_> rick_h: Ok cool makes sense I think I'm doing it right then. Thanks again for your help!
[14:05] <rick_h> vlad_: k, let me know how it goes
[16:40] <bdx> good monday morning!
[16:41] <bdx> is there a preferred method for adding the JAAS controller?
[16:41] <bdx> other than `juju register jimm.jujucharms.com` ?
[16:42] <rick_h> bdx: in 2.2 it's juju login
[16:43]  * rick_h looks for release notes stuff
[16:43] <bdx> oh nice, but JAAS isn't there yet, so its still `juju register jimm.jujucharms.com`?
[16:44] <rick_h> bdx: you can s/register/login
[16:44] <rick_h> bdx: and that'll add it
[16:44] <rick_h> bdx: that's the new way in 2.2
[16:44] <bdx> rick_h: sweet! thx!
[17:13] <Budgie^Smore> o/ juju world
[17:14] <lazyPower> \o Budgie^Smore