[10:42] <rick_h_> urulama_: howdy
[10:42] <urulama_> rick_h_: hi
[10:43] <rick_h_> urulama_: pm
[10:52] <rick_h_> welcome back luca!
[11:48] <luca> hey rick_h_, hows it going? 
[11:48] <rick_h_> luca: heh, I'll tell you in an hour?
[11:48] <luca> rick_h_: lol sure
[11:48]  * rick_h_ goes for coffee and breakfast now that first meeting is done wheee
[11:53] <bac> rick_h_: i just entered leave into hr system
[12:00] <rogpeppe> rick_h_: one thing occurs to me: do we want clients of the store to be able to update individual files in charms/bundles? for, example, do we want them to be able to change a README independently of the rest of the files in a charm?
[12:00] <rick_h_> rogpeppe: no, I don't think so. 
[12:00] <rogpeppe> rick_h_: ok, that's cool
[12:00] <rick_h_> rogpeppe: if you wanted to do something like that it'd fall under resources. 
[12:01] <rick_h_> a resource could be some single doc referenced, but a change to the base of a charm I think is a new charm version
[12:01] <rick_h_> bac: doh, I've got to catch up on that holiday update email. 
[12:01] <rick_h_> bac: thanks, will approve here shortly. 
[12:03] <luca> rick_h_: can you give me the link to your work items doc?
[12:07] <rick_h_> luca: hmm, https://docs.google.com/a/canonical.com/document/d/14XvT-6RjHKjUhGJLuwMC1y7JCkUeuUv-XxjYsPtWhng/edit ?
[12:07] <luca> rick_h_: cheers
[12:25] <bac> rick_h_: i got the jenkins details from mgz and now need to get an account and credentials from curtis
[12:26] <bac> i think he starts a little later than us
[12:26] <rick_h_> bac: rgr
[12:26] <rick_h_> a morning person he is not :)
[13:38]  * rogpeppe lunches
[13:57] <rick_h_> jujugui make sure to welcome urulama and jrwren today. Will do face to face in the standup but if they hit you up with any questions/etc they're our new locals
[13:58] <bac> welcome urulama and jrwren
[13:58] <kadams54> Hi jrwren and urulama!
[13:58] <urulama> hi all
[13:58] <rogpeppe> urulama, jrwren: yo!
[14:00] <urulama> ok. finished the traveling form.
[14:00] <urulama> so, hi all, glad to be part of juju :D
[14:00] <jrwren> yo.
[14:10] <hatch> rick_h_ hey with the new EOY dates should we delete the old entries in hr and create new ones?
[14:10] <hatch> and g'morning :)
[14:13] <rick_h_> hatch: yea if you can try
[14:14] <hatch> ok here goes.... *puts on helmet* I'm going in
[14:14] <rick_h_> hatch: I found they didn't collide for me
[14:14] <hatch> oh ok, maybe it'll be ok here too
[14:15] <rick_h_> hatch: yea, for me I had to add one more day off from my holiday stash :(
[14:16] <hatch> yeah looks like I do too
[14:17] <rick_h_> hatch: cool, yea so no surgery required
[14:35] <rick_h_> jrwren: did you get the leankit invite?
[14:35] <rick_h_> jrwren: you and urulama up for meeting in the standup hangout 10min before the call to get a board overview?
[14:36] <urulama> rick_h_: fine by me
[14:36] <rick_h_> urulama: k, will ping in 15 and we'll meet early for a run down
[14:37] <jrwren> i can hangout anytime, I guess. I'm still trying to figure out all this account info stuff.
[14:37] <jrwren> i got distracted reading the wiki. does anyone use the voip stuff?
[14:37] <rick_h_> jrwren: cool, take your time and let me know if you hit anything that's not clicking
[14:37] <rick_h_> jrwren: most of us don't. The only main interaction is calling into the conf call system for large meetings
[14:38] <rick_h_> jrwren: honestly, we use hangouts almost for everything until we hit the 15person limit
[14:38] <rick_h_> that and irc
[14:38] <jrwren> the, i'll low prioritize that.
[14:38] <jrwren> *then
[14:39] <rick_h_> jrwren: if you can signup for leankit soonish that'd be great so I can get you access before the call
[14:40] <jrwren> ok
[14:42] <jrwren> hrm, google apps weirdness
[14:42] <rick_h_> yea, dualing accounts takes some getting used to
[14:42] <hatch> easy peasy!!
[14:42] <rick_h_> hah
[14:42] <rick_h_> hatch: are you supposed to be lake-fronting it today?
[14:43] <hatch> rick_h_ yeah but it's bloody pouring! 
[14:43] <jrwren> i did this 1mo ago when old job switched to google apps. was no problem with all chrome, but a little different because google is pointing to me LP account
[14:43] <rick_h_> hatch: poor guy
[14:43] <hatch> rick_h_ yeah tough life...
[14:43] <rick_h_> jrwren: yea, the 2fa fun
[14:50] <Makyo> jujugui callin 10
[14:50] <Makyo> Buh. Coffee hasn't reached my fingers yet.
[14:50] <rick_h_> urulama: jrwren https://plus.google.com/hangouts/_/canonical.com/daily-standup
[14:50] <rick_h_> or https://plus.google.com/hangouts/_/canonical.com/daily-standup?authuser=1 if this is your second google account :)
[14:52] <bac> Makyo: thanks for the stickers.  the many, many stickers.  :)
[14:53] <Makyo> bac, Hah, glad they made it.    Should keep you stocked up for a while.
[14:53] <bac> Makyo: yes, now i can juju-power my fridge, microwave, water heater, ...
[14:54] <Makyo> We already have internet-enabled fridges, it's only a matter of time.
[14:55] <kadams54> juju add-unit fridge
[14:56] <kadams54> er
[14:56] <kadams54> juju add-unit -n100 fridge
[14:56] <kadams54> web scale appliances
[14:57] <hatch> haha
[14:58] <kadams54> AaaS - Appliances as a Service
[14:58] <rick_h_> jujugui call in 2
[15:00] <rick_h_> Makyo: ^
[15:16] <jrwren> i should have said in standup, I have to run out for 30min, brb
[15:18] <rick_h_> jrwren: rgr
[15:26] <rick_h_> hey luca, how did the meeting go?
[15:27] <rick_h_> actually, I'll ask in PM :)
[15:29] <bac> Makyo: it was inevitable: https://flic.kr/p/oa9D3B
[15:30] <Makyo> Hahaha!  Fantastic!
[15:30] <rick_h_> bac: awesome
[15:30]  * rick_h_ goes to find food before the next meeting
[15:31] <hatch> bac haha nicw
[15:53] <jcsackett> hatch: are there any major tripping points for the dispatched service/unit detail views, or is that going to feel a lot like dispatching the local charm stuff?
[15:53] <kadams54> rick_h_: wanted to follow up more on your comments to Jeff and I about visual treatments/wireframes for deleting units and whatnot…
[15:53] <kadams54> rick_h_: it's actually one of the last TODOs in my code :-)
[15:54] <rick_h_> kadams54: sure thing in the visuals for inspector v3 there's some stuff in the inspector where removed units are moved into a grouping and there's a 'are you sure' step for removing the service, the last image in the group on the right
[15:55] <hatch> jcsackett it will be pretty easy
[15:55] <rick_h_> kadams54: https://drive.google.com/a/canonical.com/#folders/0B7XG_QBXNwY1cWQ4TmRmRXJBc0E
[15:55] <jcsackett> hatch: awesome. i'll start in on that then.
[15:56] <hatch> jcsackett the inspector dispatcher will need to instantiate the inspector with a 'select this unit' flag, then after it's instantiated it will need to open the dropdown, select the unit, etc etc
[15:56] <hatch> jcsackett so 'easy' but lots of work
[15:56] <kadams54> rick_h_: OK, taking a look…
[15:56] <hatch> jcsackett but you won't have to reinvent the wheel like you did with the local inspector stuff
[15:56] <rick_h_> kadams54: sure thing, let me know if you want to walk through it
[15:56] <rick_h_> kadams54: but honestly, I think they'll be follow up cards
[15:57] <kadams54> rick_h_: hah! yeah, that was going to be my next question.
[15:57] <rick_h_> kadams54: so be aware, but I'd move forward with the 'backendish' cards now and we'll clean up the UX as a follow up
[15:57] <kadams54> rick_h_: Excellent, we're on the same page then.
[15:57]  * rick_h_ feels like a winner!
[15:58] <hatch> jcsackett I'll probably be still online, so ping me if you have any q's 
[15:59] <jcsackett> hatch: will do.
[16:30] <kadams54> guihelp: looking for a review and a tiny bit of QA on https://github.com/juju/juju-gui/pull/412 (The first build failure has already been fixed, so… fingers crossed.)
[16:34] <kadams54> Heading out for dr. appt.
[16:35] <rick_h_> good luck kadams54 
[18:07] <hatch> hey is ci down?
[18:08] <rick_h_> hatch: seems so, /me looks
[18:08] <hatch> did MS decide to upgrade the instance? lol
[18:09] <rick_h_> hmm, our other one is down as well :/
[18:09] <rick_h_> network issue? 
[18:09] <hatch> posssssssssibly
[18:09]  * rick_h_ is checking dashboard
[18:10] <rick_h_> oh boy
[18:10] <rick_h_> jujugui all our azure vms are gone, working with our account holder to figure out what's happened
[18:11] <rick_h_> bac: can you please go to the dashboard and make sure we pull down our last backups of both?
[18:11] <bac> uh oh
[18:11] <rick_h_> bac: and look at setting up a shared account info for bringing up a new CI under ec2 (ssh key, etc) and I'll setup some credentials in a few minutes
[18:13] <bac> rick_h_: are you asking me to recreate our jenkins on ec2?
[18:13] <rick_h_> bac: to get ready to
[18:13] <rick_h_> bac: get the backups in place, generate a shared ssh key, whatever else we need to setup a shared env correctly
[18:13] <bac> rt
[18:14] <rick_h_> bac: because if this doesn't move forward very fast with MS then we'll bring it up and recreate it 
[18:14] <jrwren> does it run on US West?
[18:15] <rick_h_> jrwren: was east I believe
[18:15] <rick_h_> but the mvs are just gone, the storage buckets are still there though
[18:17] <hatch> heh that's no good
[18:17] <hatch> anything I can help with?
[18:18] <rick_h_> hatch: no, not unless you know where azure would log "by the way all your machines belong to us" messages
[18:18] <rick_h_> :)
[18:18] <hatch> lol no sorry - is there an access log? Maybe one of us accidentally clicked 'delete all!!!!!!'
[18:18] <jrwren> maybe I'm following the scavenger hunt incorrectly and I killed it :)
[18:19] <hatch> uh oh , the tweens woke up are taking selfies....my internet just slowed to a crawl
[18:21] <rick_h_> http://uploads.mitechie.com/lp/azure-ci.png :(
[18:22] <hatch> what the heck....
[18:25] <bac> rick_h_: i see we have backups as of 6/29 20:00Z (us) and 6/26 (blues)
[18:25] <rick_h_> :(
[18:56] <rick_h_> jujugui CI is down and out. We've identified the issue and bac is recreating the environment. 
[18:56] <rick_h_> jujugui so all code landings will have to wait until it's back up. Sorry for the delay if bac needs a hand please jump and help him. 
[19:53] <kadams54> Sorry, I may have missed something while I was away… is it just me, or is CI down?
[19:55] <jrwren> 14:56   rick_h_| jujugui CI is down and out. We've identified the issue and bac is recreating the environment.
[19:55] <jrwren> 14:56   rick_h_| jujugui so all code landings will have to wait until it's back up. Sorry for the delay if bac needs a hand please jump and help him.
[19:56] <kadams54> Ah thanks jrwren!
[19:56] <bac> jujugui: i'm having trouble getting azure to bootstrap.  if this latest attempt fails i'm moving to ec2.
[19:56] <kadams54> bac: OK, thanks for the update.
[20:00] <rick_h_> bac: rgr thanks for trying
[20:01] <bac> ha, must've scared azure.  next try came right up.
[20:02] <bac> rick_h_, jcsackett: what were the two jenkins instance called? jenkins and jenkins-the-blues?
[20:02] <bac> rick_h_: who controls the dns entry?
[20:08] <rick_h_> bac: I do, let me know what cname to point to
[20:12] <rick_h_> bac: that works. 
[20:49] <kadams54> rick_h_, hatch: I've got my choice of services, containers, or machines on these delete cards. Any recommendations about what to tackle next?
[20:49] <hatch> well machine and container are one and the same
[20:51] <hatch> I suppose there are some nuances, but I'm not sure one can be done without the other
[21:04] <hatch> kadams54 so machines/containers will also have some cascading tasks which need to be done
[21:05] <hatch> like removing placeUnits onto a ghost machine 
[21:05] <kadams54> hatch: sounds to me like you're voting for services :-)
[21:06] <hatch> nah that will also have cascading tasks. 
[21:06] <hatch> remove relation
[21:06] <hatch> remove addUnits
[21:06] <hatch> remove setConfigs
[21:06] <hatch> heh
[21:08] <hatch> kadams54 so probably doing remove containers/machines will be the best place to start
[21:08] <hatch> it'll have the least 'extras' I think
[21:08] <rick_h_> kadams54: the other thing is to take a break and go look at the upgrade service UX and such as well
[21:12] <kadams54> rick_h_: I'm not seeing any cards for the upgrade service UX… do they need to be created?
[21:12] <rick_h_> kadams54: hmm, /me looks thoght it was there
[21:12] <hatch> jcsackett how goes the inspector unit stuff?
[21:12] <rick_h_> Makyo: can help get you some direction
[21:13] <rick_h_> kadams54: oh, huw got it in progress
[21:13] <jcsackett> hatch: alright; my lxc was fubared for a chunk of the day, so i haven't gotten as far as i would like.
[21:14] <hatch> ahh, do you dev in a lxc ?
[21:14] <jcsackett> hatch: i do. don't like to install lots of crap on the main machine, and don't care for VMs.
[21:14] <jcsackett> mind you, apparently LXCs have their own flaws. :p
[21:15] <hatch> haha, interesting, I never thought of that, I also have an issue with install bloat after a year of working on stuff
[21:15] <hatch> lxc's would sure help that
[21:15] <kadams54> rick_h_: looks like there's another UX-ish card for adding uncommitted cues to service view/blocks
[21:16] <jcsackett> hatch: it also has the benefit of meaning i'm always developing on a system that's at least the same ubuntu release as our production instance.
[21:16] <rick_h_> kadams54: sure, that'll get you into some fun stuff
[21:17] <hatch> jcsackett yeah good call - I'm really trying to get Ubuntu to run properly on this hardware, it's not going so well, the dual gpu is really a gong show
[21:17] <hatch> rick_h_ how id the new laptop? have 14.04 on it yet?
[21:18] <jcsackett> hatch: what are you using?
[21:19] <rick_h_> hatch: yea, 14.04 on it, got the touchpad going a bit better
[21:19] <rick_h_> but it's a mix bag
[21:19] <hatch> jcsackett OSX with a vm
[21:22] <hatch> jcsackett I'd like to work with someone to get the drivers are fixed up but I'm guessing whoever is writing it would need the machine for quite a while
[22:22] <bac> jujugui: trying to install dependencies on CI machine following HACKING guide.  calls for python-selenium but one is not found.  anyone know where it comes from in precise
[22:51] <Makyo> jujugui review/qa for destroy service in ECS https://github.com/juju/juju-gui/pull/413 (also, just found some coyote kill in the yard, going to be afk while I get that taken care of)
[23:04] <huwshimi> Morning
[23:04] <rick_h__> morning huwshimi 
[23:04] <huwshimi> rick_h__: hey
[23:04] <rick_h__> huwshimi: heads up, CI went boom today and we're recovering still
[23:05] <rick_h__> huwshimi: so no landing/test runs for the moment. 
[23:05] <huwshimi> yay!
[23:05] <rick_h__> heh, like a snow day?
[23:07] <huwshimi> :)
[23:14] <rick_h__> huwshimi: do you have anything to merge?
[23:14] <huwshimi> rick_h__: Not yet. Probably today sometime though.
[23:15] <rick_h__> huwshimi: ok cool
[23:40] <hatch> Makyo i'm reviewing your branch, fyi
[23:40] <Makyo> Thanks
[23:54] <hatch> Makyo looks good - looks like the approach we discussed worked well