[12:11]  * frankban lunches
[12:27] <gary_poster> upgrade...reboot...aaand we're back
[12:27] <gary_poster> welcome back frankban! :-) have a nice time?
[12:38] <frankban> gary_poster: it's good to be back, and yes, thank you, very nice time
[12:39] <gary_poster> great :-)
[13:12] <frankban> guihelp: I need two reviews (python, mostly code removal) for https://codereview.appspot.com/13824045 . Thank you!
[13:13] <bac> frankban: will do
[13:13] <frankban> bac: thanks
[13:17]  * bac reboots
[13:33] <gary_poster> frankban, looking now also.
[13:33] <frankban> gary_poster: thanks!
[13:33] <hatch> g'morning
[13:34] <gary_poster> morning
[13:34]  * hatch isn't here, he just woke up too early
[13:35] <gary_poster> :-) sorry
[13:35] <hatch> haha, it happens
[14:18] <gary_poster> brb
[14:18] <gary_poster> (switching locations)
[14:19] <bac> frankban: tips on QA for your branch?
[14:21] <frankban> bac: for that branch, I think there is no need to QA, it's mostly moving code around. However I can quickly write 3/4 QA steps if you want to try the deployer support
[14:22] <bac> frankban: i feel the same about the branch
[14:23] <frankban> bac: cool
[14:24] <hatch> Do we have someone who's responsibility it is to approach providers and get them to write charms for their products?
[14:29] <benji> I keep having test runs abort in the middle with no status reported.  Does anyone know anything about that?
[14:31] <gary_poster> I don't, other than that there is a timer for the tests that we've had to extend in the past benji.  I'm also back, fwiw.
[14:31] <gary_poster> if anybody said anything between my "brb" and now I didn't see it--backlog is upstairs.  (hm, I can fix that for next time)
[14:34] <hatch> https://gist.github.com/hatched/a215f0d96fed6f41d165
[14:34] <hatch> ^ gary_poster
[14:34] <hatch> (chat log)
[14:35] <gary_poster> thanks hatch! the people are the charmers--Antonio's team and Jorge
[14:36] <hatch> cool I'll ping him
[14:36] <hatch> thanks
[14:46] <abentley> bac, benji: We have a replacement ready for the charmworld lander.  Unless you object, we will start trying to use it today.  Cool?
[14:47] <bac> abentley: that sounds good.  i won't have any branches for cw landing today
[14:47] <gary_poster> jujugui, fwiw we have five urgent inspector bugs to tackle.  I have some calls this morning and am trying to move the two pending reviews (huwshimi, hatch) through, but afterwards will help.  When people can take one of the urgent cards, please do.  These are not "drop your current branch" cards but "do next" cards.
[15:50] <Makyo> jujugui call in 10 kanban now
[15:58] <bac> gary_poster: no mongolian bbq for you.  bali hai burns.
[15:58] <gary_poster> bac, lol, what?
[15:58] <gary_poster> jujugui call in 2
[15:58] <bac> you never went there?  on 6 forks
[15:59] <bac> for the nerd engineers it was more about stacking the plate than eating
[15:59] <gary_poster> heh, yeah never went.  too bad it burned
[16:01] <gary_poster> hatch ping
[16:01]  * hatch pokes head up
[16:01] <bac> winter in TN now benji?
[16:01] <hatch> I'm just watching edgeconf
[16:01] <benji> bac: fall has fell
[16:01] <gary_poster> hatch oh are you out today?
[16:02] <hatch> yep, did I forget to add it to the calendar?
[16:02] <hatch> oops
[16:02] <gary_poster> hatch oh cool.  ttyl
[16:02] <hatch> I'll be around if you need me
[16:03] <gary_poster> cool thx
[16:09] <benji> gary_poster: oops
[16:09] <gary_poster> benji lol
[16:09] <gary_poster> thx
[17:06] <arosales> gary_poster, any way to pass a login URL for the juju-gui?
[17:07] <gary_poster> arosales, if someone needs to log in then the main url should challenge them.  if not, bug
[17:08]  * gary_poster goes for quick walk
[17:16] <hatch> to elaborate a little bit - any url should redirect them to a login url
[17:16] <hatch> if they aren't logged in
[17:29] <arosales> gary_poster, sorry. I didn't phrase my question right. I was wondering if there were options to the GUI url to pass in auth
[17:30] <arosales> gary_poster, user story, is we are working on a juju quick start image, and want to be opinionated as much as possible. With that we went to have the GUI up and running, but we currently block in the GUI auth. We know what the username and password is, so we just wanted to see if we could improve the story there.
[17:31] <arosales> hatch, ^
[17:32] <hatch> arosales: you can provide it in the config file
[17:32] <hatch> is that possible in your image?
[17:32] <arosales> hatch, yes I think so
[17:33] <hatch> arosales: http://bazaar.launchpad.net/~juju-gui/juju-gui/trunk/view/head:/app/config-debug.js take a peek at the `user` and `password` properties
[17:33] <arosales> hatch, we'll give that a try. We are boarding between the GUI being displayed on the host env and Juju operating in a VM
[17:33] <hatch> the charm auto generates the config though which may cause an issue
[17:35] <hatch> oh intersting
[17:35] <hatch> I've never attempted that
[17:36] <arosales> hatch, sorry when you said config I thought of https://jujucharms.com/precise/juju-gui/#bws-configuration
[17:36] <hatch> ahh - it's been a while since I've been in the charm
[17:36] <hatch> lemme see if there is a way for you to customize that
[17:38] <arosales> hatch, I would be fine with going http://bazaar.launchpad.net/~juju-gui/juju-gui/trunk/view/head:/app/config-debug.js route, not sure how to implement that in a 'juju deploy'
[17:39] <hatch> yeah just looking if we implemented a way to modify that
[17:40] <hatch> arosales: doesn't look like it :/
[17:40] <hatch> http://bazaar.launchpad.net/~juju-gui-charmers/charms/precise/juju-gui/trunk/view/head:/hooks/utils.py#L404
[17:41] <hatch> the only real option is to deploy it with staging=true
[17:41] <hatch> but that doesn't really work
[17:41] <hatch> because then it goes to a sandbox mode
[17:42] <arosales> hatch, basically my end to goal is to by-pass auth for this user story (local dev), and we can provide creds if needed since we are setting the env up anyways.
[17:43] <hatch> gary_poster: ^ any thoughts on the 'proper' approach?
[17:43] <hatch> all I can think of are ugly fragile hacks
[17:44] <hatch> I suppose the best way would be to add the u/p as a config option
[17:44] <hatch> but I don't think thats a quick addition :)
[17:45] <arosales> hatch, and there are no extra url parameters that get parsed for login, correct?
[17:46] <hatch> correct
[17:49] <hatch> arosales: a possible easy sollution could be to log out their secret from the environments.yaml to the console during the script process to tell them that that's there password
[17:50] <arosales> yup, we had that in our back-pocket, but just wanted to check with the experts here if there was any options we were overlooking
[17:50] <arosales> hatch, thanks. sounds like, atm, it is not possible to pass authentication via url or cham config to the GUI.
[17:53] <hatch> yeah unfortunately no - I'd probably vote for providing it as a config options
[17:53] <hatch> s/a//
[17:53] <hatch>  s/a//
[17:53] <hatch> I'm not sure if that came through
[17:54] <hatch> yeah unfortunately no - i'd probably vote for providing it as config options
[17:54] <hatch> :)
[17:54] <benji> At lunch I determined that my new headphones don't have a rattle.  I also determined that the headphone jack of my laptop has a short.
[17:56] <arosales> hatch, +1 on a config opt to the charm if that is possible.
[17:56]  * arosales realizes that would be dev work needed, but there are some local dev use cases. 
[17:56] <gary_poster> arosales, hatch there is one now pretty sure.  looking
[17:57]  * arosales awaits gary_poster's search
[17:58] <gary_poster> arosales, hatch, right, there's one in the GUI but we have not exposed in the charm.  would be pretty easy to add.  what's the timeframe & what's the benefit?
[17:58] <gary_poster> arosales, I understand use case, I mean in your estimation how valable is that story to the quick start story?
[17:59] <arosales> gary_poster, hmm
[17:59] <arosales> its the the cost of having the user look in the console, then copy/paste into the GUI.  
[18:00] <arosales> gary_poster, so not huge 
[18:00] <gary_poster> arosales, ack.  I want something like this in our quick start story too.  what is your timeframe?
[18:00] <gary_poster> I could have it done in probably 2-3 days.  I should get four or five urgent bugs fixed and released first
[18:01] <gary_poster> but after that this would be a quick task
[18:02] <arosales> gary_poster, we may go out with an image this week and then we can keep improving on it when you land features.
[18:02] <gary_poster> arosales, ack.  I'll try to sneak it in over the next couple of days.  will ping you when it is in, and might ask for qa to verify
[18:03] <arosales> gary_poster, we would be happy to.  Let us (arosales and utlemming) when we should test. Thanks for working on squeezing it in. 
[18:03] <gary_poster> cool arosales, welcome
[18:03] <hatch> :)
[20:39] <bac> ha, the ikea delivery man couldn't find our house so he invoked a non-existent ban on deliveries in the old city after 1pm and went back to the warehouse.  my evening just freed up.  i was looking forward to some cheap furniture assembling.
[20:43] <benji> heh; customer service does seem a bit lacking in your present neck of the woods
[21:08] <hatch> heh around here they will just leave the paper on the door and not knock because they assume I'm not home
[21:08] <hatch> very frustrating
[21:39] <bac> argh, lbox is causing my tests to crash again.  so annoying.
[23:06] <huwshimi> Morning