[00:03] <rick_h_> morn huwshimi 
[00:03] <huwshimi> rick_h_: Hey :)
[01:06] <hatch> hey huwshimi 
[01:07] <huwshimi> hatch: Hey
[01:07] <hatch> glad to start the week off without an active PR? heh
[01:09] <huwshimi> hatch: Yes!
[01:09] <huwshimi> hatch: Thanks :)
[01:09] <hatch> haha np
[01:10] <hatch> there was one small cleanup I wanted but i think kyle is going to add it to his branch
[01:10] <hatch> he found a bug with his branch that he said he was going to fix over the weekend but I haven't seen it land yet
[01:12] <huwshimi> yeah
[01:12] <hatch> I just updated the PR with the bug he found for others....I guess he didn't add the comment afterall
[01:13] <rick_h_> huwshimi: getting the next set of cards lined up in the backlog/on deck for the next 2wk cycle
[01:13] <rick_h_> huwshimi: let me know if anything seems odd or there's anything missing we don't have cards for that we should
[01:14] <huwshimi> rick_h_: Ah great, I'll have a look
[01:14] <rick_h_> huwshimi: I think this next 2wk cycle is mainly around the updated scale up journey and the 'change version' update and really we're finishing/polishing it seems. 
[01:14] <huwshimi> yay!
[01:15] <rick_h_> huwshimi: so shatter my dreams of having this become a scaled back 'polish' task after this 2wk iteration if you can think of anything :) 
[01:15] <rick_h_> but better now than later
[01:15] <huwshimi> ok :)
[01:15] <hatch> haha
[01:15] <hatch> rick_h_ have you ever used `setcap` http://linux.die.net/man/8/setcap ?
[01:16] <rick_h_> hatch: nope
[01:16] <hatch> rick_h_ darn, I'm having a hard time trying to figure out how it'll help me use port 80 in the ghost charm https://bugs.launchpad.net/charms/+bug/1229377/comments/7
[01:16] <_mup_> Bug #1229377: Charm needed: Ghost blogging platform <Juju Charms Collection:Fix Committed by hatch> <https://launchpad.net/bugs/1229377>
[01:17] <rick_h_> hatch: why not just have apache/proxy requirement for port 80?
[01:17] <hatch> rick_h_ currently, that's what it is - but until bundles become first class citizens in juju it's not a perfect experience if the user doesn't fully read the readme
[01:18] <hatch> and I really don't want to build in nginx or the sort
[01:18] <rick_h_> hatch: hmm, ok guess. Most frameworks default to a non-80 port though, but yea it'd be cool to support
[01:18] <rick_h_> hatch: so since hooks run as root why not just have root bind and run with it
[01:18] <rick_h_> ?
[01:19] <hatch> a previous comment said that ghost shouldn't run as root
[01:19] <hatch> it's been quite confusing
[01:19] <hatch> don't use root, use port 80...ahhhhh
[01:19] <hatch> lol
[01:19] <rick_h_> well, if it's run in a container/etc then what's the issue?
[01:20] <rick_h_> I'd push back and ask for an example charm that does this without running as root. What does wordpress use? 
[01:20] <hatch> I think it has apache running inside or something
[01:20] <hatch> I have pushed back on the port 80 requirement
[01:20] <huwshimi> rick_h_: There are a few things in Luca's QA doc that don't have cards: https://docs.google.com/a/canonical.com/document/d/1p-wPlgVqZoYlMRuChLpAjkJAKZcw-wkSZfs6deIWmc8/edit
[01:20] <hatch> so hopefully they let it in
[01:21] <rick_h_> huwshimi: onboarding is saved for last
[01:21] <rick_h_> huwshimi: and some of these I think are fixed released. Will go back through it
[01:22] <huwshimi> rick_h_: Things like the popover size controls
[01:23] <huwshimi> rick_h_: close controls on the summary
[01:23] <huwshimi> rick_h_: I can add cards for the ones I know are missing if you like?
[01:23] <rick_h_> huwshimi: hmm, thought those were the cards in backlog
[01:23] <rick_h_> huwshimi: yea, those are in the backlog on deck
[01:24] <huwshimi> oh yeah that's there
[01:24] <rick_h_> huwshimi: but do feel free to add anything you see missing that's not fixed already
[01:24] <huwshimi> ok sure
[01:26] <huwshimi> rick_h_: I'll start picking up some of those backlog cards today as I'm nearly done here.
[01:26] <rick_h_> huwshimi: oh ok, I was going to mention it but you had a card in 'branch start' so figured you were set
[01:27] <rick_h_> huwshimi: but definitely, grab any on deck if you're free
[01:28] <huwshimi> great
[03:41] <hatch> huwshimi did the review on your branch
[03:41] <hatch> you seem to be getting the hand of this js thing :)
[03:41] <huwshimi> hatch: Ah brilliant thanks.
[03:41] <hatch> s/hand/hang
[03:42] <huwshimi> hatch: Would you prefer a switch?
[03:43] <hatch> 6:1 6:12 of another :)
[03:43] <hatch> I think a switch would minify smaller
[03:44] <hatch> I would probably go with a switch if I was doing it, but the benefit would be negligible 
[03:44] <hatch> :)
[03:44] <huwshimi> hatch: Sure, I'll change it :)
[03:46] <hatch> hah ok cool
[03:56] <huwshimi> hatch: Ugh, 'this' isn't passed into switch cases? Yay!
[03:58] <hatch> :) if it's gona be too much of a pita you don't have to do it 
[04:00] <huwshimi> hatch: Ah, no, I forgot to pass this to the new forEach
[04:04] <huwshimi> hatch: Changes are up if you want to take a look: https://github.com/juju/juju-gui/pull/398
[04:06] <hatch> cool looking
[04:07] <hatch> looks good
[04:07] <huwshimi> great
[04:07] <huwshimi> thanks!
[04:49] <hatch> huwshimi I set up to re-run your merge
[04:49] <huwshimi> hatch: Ah thanks
[04:49] <hatch> it failed with a intermittent error
[04:50] <huwshimi> hatch: We seem to have a lot of those
[04:50] <hatch> dont I know it!
[04:56] <hatch> huwshimi the other branch failed with the same error
[04:56] <huwshimi> hatch: Yay!
[04:57] <hatch> it looks like saucelabs might be borked
[04:57] <huwshimi> Yay!
[04:57] <hatch> I can try and land them in the morning
[05:03] <huwshimi> thanks
[05:08] <hatch> annnnd I'm out, have a good one
[07:42] <rogpeppe1> mornin' all
[11:35] <rick_h_> morning party people
[12:28]  * rogpeppe1 lunches
[13:19] <hazmat> why is charm config read only during deploy?
[13:19] <hazmat> also why do interfaces/relations not show for a  deployed charm?
[13:20] <hazmat> oh.. you have to explicitly select not default configuration..
[13:20] <hazmat> odd
[13:23] <rick_h_> hazmat: charm config is getting updated and we're looking at pulling that read-only bit
[13:23] <rick_h_> hazmat: the thought was that the defaults should be sane and to make it as clean/few things to click on as possible to get deployed/going
[13:24] <rick_h_> hazmat: but we've got work this 2wk cycle to update that
[13:24] <rick_h_> hazmat: and for interfaces/relations, no idea. I guess by clicking the charm you can see what to relate to. Constructed relations show in the tab for them
[13:25] <rick_h_> but never really had relation info, not sure if we get that from the charm data from the env or not. 
[13:25] <hazmat> rick_h_, ie. i've deployed nova-compute.. charm details on it, doesn't show the related/interface tab
[13:25] <hazmat> charm browser does..
[13:26] <rick_h_> hazmat: yea, because we don't have the data from the charm model data from the environment so we scope down the tabs to match the data we have
[13:26] <hazmat> rick_h_, we do get interfaces/relations from env.. (not related though)
[13:26] <rick_h_> hazmat: with the work in progress to add the data/update the apis to the juju store we'll be able to update that
[13:27] <rick_h_> hazmat: right, we don't have the info to build that tab. We didn't have any request/requirement to build an alt UI to that tab
[13:27] <hazmat> rick_h_, this is part of the charm definition.. doesn't need the store to display named rels and interfaces
[13:27] <hazmat> its available in the charm info api off the env
[13:27] <rick_h_> hazmat: right, sorry. You're right that we have the end points, but the api doesn't match the info to build the UI. It needs updating to work for deployed charms. 
[13:28] <rick_h_> hazmat: and just never been asked for or thought about to be honest. 
[13:29] <hazmat> seems like a basic usability bit.. ie. i've got x deployed, what can i do with it (what else do i need to deploy)
[13:29] <rick_h_> hazmat: right, there's work in the machine view stuff to update the inspector to show 'popular relatable charms'
[13:30] <rick_h_> and moving config to it's own tab. I'll file a bug on the tab though for deployed charms 
[13:32] <rick_h_> hazmat: https://bugs.launchpad.net/juju-gui/+bug/1333258
[13:32] <_mup_> Bug #1333258: gui does not show related charms tab for deployed charms <juju-gui:Triaged> <https://launchpad.net/bugs/1333258>
[13:53] <hatch> morning all
[13:53] <rick_h_> party
[13:54] <hatch> so party
[14:01] <bac> rick_h_: i submitted a vacation day request
[14:01] <rick_h_> bac: k thanks. hatch sent me an email as well will get those in
[14:02] <hatch> w00t
[14:02] <rick_h_> jujugui any time off the next 2 weeks please submit so we can plan cards for the 2wk sprint
[14:02]  * hatch isn't sure if new system is better than old system
[14:02] <hatch> :P
[14:02] <bac> hatch: yeah.
[14:02] <bac> be aware, if you click on the big calendar to start a new request, it pre-populates not with the date you clicked on but with today's date.  sneaky.
[14:06] <hatch> I suppose this new one actually allows you to go back and modify things
[14:07] <hatch> that almost makes up for the scheduled downtime that seems to be a feature in the salesforce world lol
[14:07] <bac> jujugui: does anyone know if the new HR system allows you to see a calendar for colleague's work schedule? i can't find it.
[14:07] <hatch> yep
[14:07] <hatch> go to Team Members
[14:07] <hatch> Paid Time Off
[14:07] <hatch> then click on the team members face
[14:08] <hatch> you can also change the level of PTO.....I always change it to level 10.....( I don't think this does anything but I feel special at level 10 days off ) :D
[14:09] <hazmat> rick_h_, thanks
[14:14] <bac> rick_h_: i'm going to be traveling on the thursday before the sprint, the 17th. mark that as a swap day so you'll see i'm unavailable?
[14:15] <rick_h_> bac: sure, works for me. 
[14:16] <bac> hatch: that works but you can't see schedule for people not on the team
[14:18] <hatch> ohh, I suppose - could you with the old one? I never tried
[14:18] <hatch> tbh
[14:27] <hatch> jujugui in ecs mode do we really need to confirm removing relations? Or can we just do it and then they can add it back in before hitting commit if they did it by accident (somehow)
[14:28] <rick_h_> hatch: you mean do we need to ecs remove relation at all?
[14:28] <hatch> no, there is a dialogue that pops up asking you to confirm that you want to remove the relation
[14:29] <rick_h_> hatch: ah, no. I'd assume that no we'd not need to
[14:29] <rick_h_> we should ping UX though on how to represent a removed relation in the canvas. I feel like that's a whole in the UX
[14:29] <hatch> good point, I'll fire off an email
[14:39] <rick_h_> bac: pm
[14:50] <Makyo> jujugui call in 10
[14:51] <rick_h_> get your planning poker buzzers ready!
[14:56] <hatch> 3
[14:56] <hatch> 2
[14:56] <hatch> 4
[14:56] <hatch> 4
[14:56] <hatch> 4
[14:56] <hatch> 1
[14:56] <hatch> 2
[14:56] <hatch> 3
[14:56] <hatch> *phew*
[14:56] <hatch> ok warmed up
[15:00] <rick_h_> jujugui call in 1
[15:00] <rick_h_> antdillon: ^
[15:12] <hatch__> kadams54 http://fromanegg.com/post/67170468715/intro-to-go-from-a-javascript-developer-barcamp-yxe
[15:50] <hatch> kadams54 of course there was a whole spoken track which outlined the differences while showing it in go
[15:50] <kadams54> 813345
[15:50] <kadams54> hah!
[15:50] <kadams54> hatch: Thanks, looks like some good material.
[15:51] <hatch> yeah the talk got good ratings in the reviews 
[15:52] <hatch> ugh Ci
[15:52] <hatch> rick_h_ I wonder if we used a bigger instance for our CI if we would end up with the same issues
[15:53] <hatch> kadams54 I re-triggered the merge run for #399
[15:53] <kadams54> 859619
[15:53] <hatch> 368718641818143813
[15:53] <hatch> I win
[15:53] <kadams54> Man, I gotta quit doing that.
[15:53] <hatch> lol!
[15:53] <kadams54> hatch: thanks
[15:54] <hatch> I'm thinking of painting the edge of mine with some clear nail polish and only leaving a small sliver open
[15:54] <hatch> then it can't be hit as easy
[15:54] <hatch> going to try it first with some tape
[15:58] <rick_h_> hatch: it's a big instance currently
[15:58] <hatch> rick_h_ interesting - I'm just wondering why the http requests are so.....darn......slow......
[15:59] <kadams54> dilrklkdecijlvjntbluutlkffgkbebjfbfvlr
[16:00] <hatch> rofl
[16:00] <rick_h_> hatch: it's 4 cores and 8gb of ram
[16:00] <hatch> rick_h_ lol what the heck
[16:00] <hatch> blame java?
[16:00] <hatch> :D
[16:00] <rick_h_> hatch: :)
[16:31] <hatch> everyone, in your local laws do you have a legal limit of .04 BAC for driving? 
[16:33] <rick_h_> hatch: .08
[16:33] <hatch> ours are changing to .04 and the penalties are bonkers imho
[16:33] <rick_h_> hatch: with .02 for < 21yrs old and .17 is bad bad times
[16:33] <hatch> I've tweeted at the govt asking for statistics 
[16:33] <hatch> http://www.sgi.sk.ca/about/articles/2014/trafficsafetychanges.html
[16:34] <hatch> http://www.sgi.sk.ca/images/0-content-pages/2014_consequences_660.jpg
[16:34] <rick_h_> well, I'm always for locking that down imo. Too many people, my family especially, going about :/
[16:34] <hatch> I'm very very skeptical that it will help anything
[16:34] <hatch> .04 is one beer after work
[16:34] <rick_h_> http://www.michigan.gov/msp/0,4643,7-123-64773_22774-49577--,00.html
[16:35] <hatch> right, but what those stats dont' say is the BAC of the person
[16:35] <hatch> just that they were alcohol related
[16:36] <hatch> that's the problem with all of these stats they are missing the details
[16:39] <hatch> rick_h_ lol 289,000 crashes.....in a year???
[16:39] <rick_h_> hatch: for our one steate
[16:39] <rick_h_> state
[16:39] <hatch> jeebus you guys like your booze 
[16:39] <hatch> lol
[16:39] <hatch> maybe you should drop yours to .04 :P
[16:39] <rick_h_> :)
[16:39]  * hatch says that while he waits for his own traffic stats
[16:40] <hatch> ""Michigan law enforcement agencies arrest an average of 103 motorists a day for drunk and impaired driving.""
[16:40] <hatch> wow!
[16:41] <hatch> I am kind of guessing that those stats as a % are not outliers and each state/prov probably follows similar stats
[16:41] <rick_h_> well I think it does depend on states
[16:41] <rick_h_> driving, the types of driving, conditions, etc
[16:42] <rick_h_> michigan with the snow/ice seasons, the overall rush/poor driving, really poor roads. I'd expect us to be towards the upper 10%
[16:42] <hatch> I suppose worse conditions would increase the probability that an impaired driver would crash
[16:43] <rick_h_> right
[16:43] <rick_h_> and get noticed/pulled over/etc
[16:43] <hatch> true true - I drove around a lot this weekend, people don't need any help driving like idiots 
[16:43] <hatch> lol
[16:52] <rick_h_> jujugui heads up the board is ready for the cycle. We almost hit planned counts and had a little over 20% unsched work. 
[16:52] <hatch> really? awesome - I thought we were sunk :)
[16:52] <hatch> go us!
[16:53] <rick_h_> well last cycle I over sub'd the board a bit to get a feel for the bigger team size and the blues is a lot of unknowns
[16:53] <rick_h_> so the board wasn't a good indicator, but all good
[16:53] <rick_h_> this time we're right on, so should be good and if the new starters help with any of it we should be golden. 
[16:54] <hatch> great
[16:57] <hatch> jujugui fyi 'make devel' almost works 100% on osx :)
[16:57] <rick_h_> lol
[17:19] <hatch> rick_h_ just reviewed Huw's latest branch, needs a touch of work so I'm sure he'll get it landed early his morning
[17:19] <rick_h_> hatch: rgr, ty much
[17:29] <rick_h_> bac: rogpeppe can you guys take a peek at https://github.com/juju/charmstore/pull/6 when you get a few mins and make sure that makes sense?
[17:29] <rogpeppe> rick_h_: i'm pretty much at eod, but i'll try to take a look
[17:29] <rick_h_> rogpeppe: tomorrow is ok
[17:30] <rick_h_> rogpeppe: just on the radar. with francesco out and bac getting up to speed going to lean on you for review help
[17:31] <bac> rick_h_: will do
[17:35] <hatch> jujugui - if I tell juju-core to delete a machine which has a number of containers in it (via the api) will it auto tear down the containers or will it throw an error?
[17:36] <rogpeppe> hatch: i'm not sure
[17:36] <rogpeppe> hatch: there has been some debate about the desired semantics there
[17:36] <hatch> ok - at the moment for the ecs I'm going to assume that any delete operation will 'just work' and we can re-evaluate later I suppose. 
[17:36] <rick_h_> hatch: throw up a branch on ec2 and let's see?
[17:36] <rogpeppe> hatch: personally i would prefer the former, but some people want things to be more explicit because you might be tearing down important stuff
[17:37] <hatch> rick_h_ I'm not sure how to easily simulate an api call through the gui
[17:37] <rogpeppe> hatch: it shouldn't be hard to try it out
[17:37] <hatch> 'easily' being the key word there
[17:37] <rick_h_> hatch: we have the api calls, just need to console.log to find and build the right call?
[17:37] <bac> rick_h_: i looked at cmars PR.  it may be good as a first start but i think webops is leaning towards storing dependencies in an S3 bucket for prodstack deploys rather than bundling.
[17:37]  * bac wishes jcsackett were around
[17:38] <hatch> rick_h_ rogpeppe I think I found my answer in the gui source 
[17:38] <hatch>       @param {Boolean} force Whether to force machines removal even if they
[17:38] <hatch>         host units or containers.
[17:38] <rick_h_> bac: oh didn't realize that. Good to know I guess. So for deploying we need a step to get deps into the private space s3 bucket?
[17:38] <rogpeppe> hatch: cool
[17:41] <bac> rick_h_: yes.  i'll check with sinzui to see how they've set things up
[17:42] <rick_h_> bac: ok cool. 
[17:42]  * rogpeppe is done for the day
[17:42] <rogpeppe> g'night all
[17:43] <bac> bye rogpeppe
[18:23] <hatch> heh state bites again...oops https://bugs.launchpad.net/juju-gui/+bug/1333376
[18:23] <_mup_> Bug #1333376: Clicking links in relation dialogue shows inspector under charmbrowser headers <juju-gui:New> <https://launchpad.net/bugs/1333376>
[18:31] <hatch> hmm, we need ghost-service-name to service-name utilities 
[18:32] <rick_h_> hatch: yea, we dance around that and probably needs to be more formal
[18:33] <hatch> atm removing a ghost relation between two ghost services fails because of that
[18:33] <hatch> I'm investigating but it might be a follow-up
[18:34] <rick_h_> hatch: rgr
[18:37] <hatch> yep follow-up Ill create a bug
[18:39] <kadams54> hatch: https://github.com/juju/juju-gui/pull/393 should be QA-able again. Also addressed review issues.
[18:42] <hatch> ok looking
[18:46] <hatch> ugh github 'expand' buttons aren't working
[18:47] <hatch> this is makign this review very difficult
[19:01] <hatch> well I totally borked my develop branch...
[19:01] <rick_h_> stop doing that hatch 
[19:02] <hatch> but it's so funnnnn
[19:07] <hatch> ugh git
[19:10] <hatch> ok NOW I can qa the branch
[19:17] <hatch> kadams54 (Note: should this link be hidden when a machine is not selected?) <--- you should send an email to design and create a bug/card to track the response so we don't forget about it
[19:17] <kadams54> Will do
[19:18] <hatch> is clicking create supposed to close the create-machine box?
[19:24] <kadams54> hatch: Yes. Close the form, create the machine.
[19:25] <kadams54> The mocks don't have the form sticking around after machine creation… unless I'm misunderstanding?
[19:26] <hatch> see the qa issue in your PR
[19:29] <hatch> kadams54 if I create a machine, then drag a unit to that machine my only options are lxc or kvm, so I can't put it on bare metal....is this by design because it feels like a bug?
[19:31] <hatch> I'll add it as a qa issue in the PR 
[19:32] <hatch> kadams54 ok qa done
[19:42] <bac> hi rick_h_, do you have some time to talk?
[19:42] <rick_h_> bac: in 10?
[19:42] <bac> sure. ping when free
[19:44] <rick_h_> bac: ping freee! told ramm I had important calls to make :)
[19:44] <bac> ha.
[19:44] <bac> standup
[19:44] <rick_h_> rgr
[20:15] <hatch> I wonder if i could hire an intern to write tests for me
[20:16] <kadams54> testern
[20:16] <hatch> lol
[20:16] <hatch> that
[20:16] <hatch> it would actually be a great education
[20:16] <rick_h_> hatch: but you've gotten so much better at writing them :P
[20:16] <hatch> haha
[20:16] <hatch> I could then pass this knowledge on
[20:16] <hatch> !
[20:16] <rick_h_> there you go, hatch the test teacher
[20:17] <rick_h_> here's your 'homework' and make sure it's done by tomorrow so I can get my code review in
[20:17] <hatch> lol
[20:17] <hatch> exactly
[20:28] <hatch> rick_h_ I think that #1333395 should be my next card after this branch lands because the relation removal story is incomplete/broken until then
[20:28] <_mup_> Bug #1333395: Cannot delete ghost relation between two ghost services <juju-gui:Triaged> <https://launchpad.net/bugs/1333395>
[20:28] <bac> rick_h_: is there a plan for local charm support in bundles? i know we've talked about it but i'm unclear about the decision/roadmap
[20:32] <rick_h_> bac: we've talked about a lot of them to be honest. No one is settled on at the moment. 
[20:32] <rick_h_> hatch: ok
[20:32] <rick_h_> hatch: makes sense
[20:33] <rick_h_> bac: if there's a store in every environment out of the box, then you'd just publish to your environment. 
[20:34] <rick_h_> bac: or there's some bugs to work out around juju-core and versioning to make bundles work in the current form 
[20:34] <rick_h_> bac: and then there's resources/fat charms/bundles that could be used to solve the problems
[20:34] <rick_h_> but that's not on the current todo list
[20:34] <bac> rick_h_: gotcha.
[20:42]  * rick_h_ runs away for the day
[20:42] <rick_h_> evening all
[20:53] <hatch> lata!
[21:19] <hatch> Makyo any idea where the add relation tests are? There are the add_relation tests for non mv in test_env_go but I don't see any which test the mv path
[21:19] <Makyo> one sec.
[21:19] <hatch> thanks
[21:20] <Makyo> test_env_change_set.js:462 (I think that's what you're looking for, correct me if not)
[21:21] <hatch> well that tests the change set stuff - but nothing that the actual call to the go env ends up in the ecs
[21:21] <hatch> I was looking for something to copy....lol
[21:27] <hatch> maybe it was just overlooked?
[21:42] <Makyo> Not sure..
[22:39] <hatch> oh well no problem
[23:07] <huwshimi> Morning
[23:11] <rick_h_> morning huwshimi 
[23:11] <huwshimi> rick_h_: Hey