20:02:06 #startmeeting glance 20:02:07 and rosmaita! 20:02:08 Meeting started Thu Jan 9 20:02:06 2014 UTC and is due to finish in 60 minutes. The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:02:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:02:11 The meeting name has been set to 'glance' 20:02:20 hi 20:02:25 greetings everyone 20:02:28 happy 2014 20:02:53 agenda link 20:02:55 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 20:03:50 a lot of boiler plate to go through I think 20:03:56 so I'll go ahead and get started 20:04:05 #topic mini summit 20:04:20 I hope folks saw my email announcing the details for the mini summit 20:04:34 #link http://lists.openstack.org/pipermail/openstack-dev/2013-December/023153.html 20:04:47 I've kicked off a draft agenda here 20:04:57 #link https://etherpad.openstack.org/p/glance-mini-summit-agenda 20:05:01 do you have an idea approximately how many people will attend? 20:05:04 it had some initial looks and feedback 20:05:14 arnaud: I think the upper end is around 25 folks 20:05:22 ok sounds good! 20:05:23 probably somewhere in the high teens 20:06:06 so we need your help to make this meeting a success, have a look at the agenda, add to it, add your interest 20:06:15 if there is anything that seems missing let me know 20:06:38 I think by next week we should have enough to start actually scheduling so folks know what they need to prepare in terms of discussion notes / slides / etc 20:06:52 sounds good 20:07:09 this is the first time doing a mini summit for. . um. . all of us? so I guess we'll be playing most of the parts by ear :-) 20:07:25 so we'll try to have fun :-) 20:07:26 it's just like a regular summit, only mini 20:07:30 any questions about the summit? 20:08:20 so will we have separate time apart from these talks for discussions i hope ( i presume yes_ 20:08:56 yes, I think so 20:09:03 there will be some downtime for sure 20:09:05 and meals etc 20:09:36 if you like, we can leave open some time for informal lightning talks etc 20:09:37 for now, there are ~10 talks, if all of them are 1h, 10h in 2 days, it seems there is time left for discussion 20:10:04 I also thought there might be some room if folks want to do a little hackathon type thing 20:10:26 but I'm not exactly sure what form that would take, and would like to have a good idea before we devote time to it 20:10:34 anyway, food for thought in case anyone especially likes the idea 20:10:53 moving on for today 20:10:58 #topic Icehouse 2 is closing soon 20:11:01 markwash: is there some plan to allow people "attend" the summit remotely who can't go there? like a remote video will be great 20:11:24 zhiyan: hmm, no plan as yet but maybe we can figure something out? it will probably be a terrible timing for you :-) 20:11:27 +1 do we plan to at least record the talks? 20:11:28 maybe set up etherpads for notes. or use the same one 20:11:48 zhiyan: but since its a small group it is possible that it would be easier to share e.g. with a google hangout or skype or some other software 20:12:13 humm...i'm ok for the time, if we have way to attend remotely, i will join on that time :) 20:12:19 heh cool 20:12:53 iccha: perhaps some rackspace video equipment could be commandeered 20:12:55 arnaud: good idea 20:13:32 markwash: fir recording or transmission? will ask around :) 20:13:44 recording I guess is probably easiest and most important 20:13:51 but I would love transmission if somebody knows how to do that 20:14:01 markwash: that will be great, transmission. iccha 20:14:12 we are only going to have 1 room / 1 track so transmission might be easier than with the regular summits 20:14:33 markwash: indeed 20:15:00 anyway, sometimes this stuff turns into a disaster, not much better than nothing, so let's not sink too much into it unless we feel confident 20:15:13 this stuff -> trying to support full remote participation 20:15:30 recording is a clear win, so if that's all we can get so be it 20:15:49 any further mini summit thoughts? 20:16:23 will ask about recording and let u know markwash 20:16:31 cool 20:16:39 On to Icehouse 2 20:16:50 all my thoughts are there on the meeting agenda page 20:16:58 #link https://launchpad.net/glance/+milestone/icehouse-2 20:17:12 we've got less than 2 weeks, since we'll probably want to cut on the 20th 20:17:27 the gate has been really rough lately, even without a crunch time 20:17:35 so I'm expecting very bad weather, so to speak 20:17:56 if you want to land something, you probably need to get it into the gate queue by the middle of next week 20:18:09 and reviewers need to be on hand to help with that process 20:18:24 I will note, we have some blueprints that aren't started yet 20:18:48 should we consider deferring https://blueprints.launchpad.net/glance/+spec/new-download-workflow ? 20:18:54 or is the work just not up to date? 20:19:15 also, flaper87 was working on https://blueprints.launchpad.net/glance/+spec/split-image-size but I haven't seen a patch yet, am I just missing it? 20:19:29 we do not have import script merged yet. so maybe we will have to jump similar hurdles for export 20:19:43 i know nikhil started work on it but not sure where he is at 20:21:19 hmm okay 20:21:32 well, if I don't hear back by tuesday I'm going to defer those two 20:21:50 any other thoughts on icehouse-2? questions? 20:22:26 I think it would be good at the minisumit to have some time allocated to look at what is done, what was expected, what is left 20:22:29 for icehouse 20:22:42 +1 20:22:47 arnaud: good idea 20:23:24 that should be a good motivating discussion 20:23:36 yeah could tie into the blueprint discussion 20:23:38 and help constrain our wilder plans on some of the other topics 20:23:55 ashwini: says videoeqipment is a yes! 20:24:07 huzzah, thanks ashwini 20:24:08 nice :) 20:24:35 sorry joining let but yes i will take care of that 20:24:44 s/let/late 20:24:46 ashwini: iccha thanks 20:24:50 okay cool, let's take a look at the review queue, my favorite topic :-P 20:24:57 #topic review backlog 20:25:13 I posted a bunch of links in the agenda, not going to repost here 20:25:24 but I think something ameade brought up in the past is still very relevant 20:25:43 I think we're still just trimming our queue with "abandoned due to inactivity" 20:25:46 sad times 20:26:10 we've had queue growth over the past 3 months 20:27:01 I'm a bit afraid we're only going to recover from this when we figure out how to block out some of the noise 20:27:10 in terms of patches that are more churn than value 20:27:26 hopefully some automation around bugs, blueprints, and patches can help that 20:27:41 Anyone have thoughts on how we can fix our review backlog? 20:28:12 is the problem not enough reviews or not enough reviewers or neither or both? 20:29:14 Glance Core team size: 10 (avg 1.0 reviews/day) 20:29:23 Nova Core team size: 19 (avg 2.5 reviews/day) 20:29:26 for 90 days 20:29:46 I suppose the glance core team is a bit inflated, we probably have more like 5 active core members 20:29:48 some of the core glance are not reviewing code right? 20:29:56 which would bring us up to 2.0 reviews/day 20:30:33 the whole thing needs to be considered against our patch volume as well 20:31:09 we get about 15 patchsets a day 20:31:21 and we get about 4 patches per change 20:31:27 so that's really only about 4 changes per day 20:31:36 oh, 3.7 per day over the past 90 days 20:32:10 of course, the number of reviews needed is something like patchsets / day + changes / day 20:32:29 Changes abandoned in the last 90 days: 97 (1.1/day) 20:32:30 so that has us needing 18.5 reviews a day 20:33:10 I can see a few ways to affect this 20:33:24 more reviews (more reviewers * more reviews per reviewer) 20:33:27 fewer changes 20:33:33 fewer patchsets per change 20:34:00 how can you control fewer changes? 20:34:06 hi 20:34:10 more reviews on a given patchset 20:34:16 or more complete reviews 20:34:40 arnaud: I think we can potentially have some automatic -2s that essentially remove changes from consideration 20:34:50 I see, interesting 20:34:56 arnaud: its essentially figuring out a way to raise the barrier to entry 20:35:05 which isn't considered a good thing by many 20:35:20 yes I see, a queue before the queue :) 20:35:24 however, I just don't see how we can have much in the way of sanity if our review queue isn't averaging something close to zero 20:35:28 for example jenkins job fialing 20:35:33 on py27 tests or soemthing 20:36:45 iccha: I do feel like maybe something along the lines of better blueprint triage, like you've been looking into, could allow us to say "auto -2" to things that didn't have approved blueprints 20:36:58 I think better bug triage is another part of that picture 20:37:39 since if we tightly control only one of blueprints or bugs, then the uncontrolled one becomes a shunt and everyone with an untagged change will just tag it as a bugfix or blueprint, whichever is easiest 20:37:58 without really adding any value in terms of up-front consideration 20:38:38 oh well, again more food for thought. . if the 5 active core folks we had just all tried to get 4 reviews per day, I think the queue would gradually go down 20:38:39 is there a repo for gerrit or all this automation? 20:38:59 I'm trying to do 10-20 a day to get down to a lower queue level but I burn out kinda fast 20:39:13 markwash: cool 20:39:22 zhiyan: thanks so much for your help in that, btw! 20:39:33 markwash: np at all 20:39:36 I love how we seem to trade off timezones and the "Needs One More +2" queue :-) 20:40:04 markwash: yes, actually that's my first page on the morning 20:40:09 mine too :-) 20:40:14 :) 20:40:22 awwww :) 20:40:27 sorry could not help it :p 20:40:30 lol 20:40:35 do you guys use some kinda of special query for that? 20:40:46 sorry jenkins filters dont seem intuitive to me 20:40:50 https://review.openstack.org/#/q/status:open+project:%255Eopenstack.*glance.*+branch:master+label:CodeReview%253D2+-label:CodeReview%253D-1+-+label:CodeReview%253D-2+-label:Approved%253D1,n,z 20:41:22 ty markwash 20:41:37 markwash: btw, could you pls share another worth quick-link with me/us? (maybe you can help do that on each meeting) 20:42:04 zhiyan: I don't exactly follow, can you elaborate? 20:42:28 markwash: oh, another link, just like this "Needs One More +2" 20:42:55 markwash: which can help me/us accelerate review/landing change 20:43:05 sure, what do you want this other link to point to? 20:43:52 is there anything reviewers (who are not core), can do to accelerate the review process? 20:44:11 reviews from everyone are welcome 20:44:11 well, we could promote some active non-core folks to core 20:44:13 core or not 20:44:14 (maybe focus of reviews related to approved bp?) 20:44:16 to help move things along? 20:44:29 markwash: no particular idea, just want to know your experience 20:44:30 I think -1s are always helpful when needed, also 20:44:36 zhiyan: ah sure thing 20:46:01 zhiyan: I can post all of the ones I use in an email if you like 20:46:12 markwash: lzy.dev@gmail.com 20:46:13 there is something I noticed, is that sometime, reviewers give one review on a patch, and then when the code is updated or whatever, it is harder to get another review.. do you guys have the same feeling? 20:46:22 yeah absolutely 20:46:26 markwash: maybe share it in meeting etherpad? 20:46:30 markwash: thanks! 20:46:31 so all of us can have access to it 20:46:34 that's part of the insanity of having such a long queue 20:47:00 arnaud: if you tend to feed off the bottom of the queue, then the second review after a fix takes forever to loop back around 20:47:16 I wonder if to respond to that we should try to top-feed off of the queue of reviewable items 20:47:32 btw, link to reviewable changes: 20:47:33 https://review.openstack.org/#/q/-label:CodeReview%253C%253D-1+-label:Verified%253C%253D-1+-label:Approved%253E%253D1++-status:workinprogress+-status:draft+-is:starred+-owner:mark.washenberger%2540markwash.net+project:%255Eopenstack.*glance.*,n,z 20:47:46 probably want to put in your own name to that filter 20:49:01 markwash: cool 20:49:02 the problem with that link I just shared is that its hard to find out when someone simply disagrees with a -1 and doesn't push a new patchset 20:49:13 because any -1 removes you from the queue 20:49:41 okay, I wanna open up for discussion, but we can keep talking about reviews 20:49:53 I don't have any action items for this yet, I just want people to know the scale of the problem 20:49:57 #topic open discussion 20:50:08 about the export script 20:50:37 Have started the work on swift store side of things, Fei had mentioned about working on the filesystem one 20:50:55 he was waiting on the executor to be pushed up 20:51:07 reviews out? 20:51:14 This is an important change and more diverse reviews the better on this one: https://review.openstack.org/#/c/34801/ 20:51:14 I'm planning to work for next 3-5 days on export and then work on executor 20:51:26 markwash: ^^ 20:51:55 nikhil___: okay great, daily or semi-daily report emails appreciated, they're great reminders for me 20:52:05 don't have to be long or formal at all :-) 20:52:32 iccha: does that patch do what you guys want it to at RS? 20:52:45 I've been a bit nervous though I look at it in my queue every day 20:53:15 markwash: sure will start them back on starting tomorrow. (Have just been distracted by either being sick or having my apartment getting flooded), Focus on reviews and MP would be back on next week onwards. 20:53:22 oh my 20:53:36 well I hope your health and apartment are returning to working order! 20:53:46 markwash: it looked like the best temporary solution. it makes me nervous too. thats why not rushing it and would like more eyes on it 20:54:03 thank you! 20:54:54 iccha: okay cool I'll stop avoiding it then :-) 20:55:06 iccha: will look at it too 20:55:11 Any other thoughts? or shall we close out? I can start my lunch ;-) 20:55:33 markwash: just one comment 20:56:02 I will try to have the tasks demo in the mini summit on RS cloud + swift 20:56:08 oh awesome! 20:56:12 thanks nikhil___ 20:56:16 not sure if I can have it done on filesystem +devstack though 20:56:19 great 20:56:35 that sounds really good 20:56:51 okay, thanks everyone, have a nice rest of your week and weekend 20:56:55 bye! 20:56:57 bye 20:56:57 thanks markwash 20:57:00 think about what you want out of the mini summit! 20:57:03 bye! 20:57:03 #endmeeting