17:14:37 #startmeeting qa 17:14:38 Meeting started Thu Oct 4 17:14:37 2012 UTC. The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:14:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:14:40 The meeting name has been set to 'qa' 17:14:43 jaypipes, dwalleck : Last chance to add something to the QA summit agenda...? 17:15:08 jaypipes, dwalleck : I am going to leave one slot open. 17:15:19 davidkranz: I'd like to, but I'm not exactly sure what would make the most sense 17:15:45 dwalleck: Just let me know your thoughts and I'll figure out how to fit it in. 17:15:50 Alot of the things I wanted to discuss are already in a few people's talks 17:15:54 sure, I can do that 17:16:13 dwalleck: Remember, there are no talks. It is all discussion. 17:16:30 Right. Bad wording on my part 17:17:04 dwalleck: It's more than wording. We can move discussions to different topics as needed. 17:17:22 dwalleck: Some will need more than 40 minutes, some less. 17:17:22 davidkranz, dwalleck: the following gets our gate working again: https://review.openstack.org/#/c/14049/ 17:17:48 jaypipes: Great! Will check it out as soon as we're done. 17:17:54 same here 17:17:56 it builds on torandu's patches. 17:20:22 Good morning. sorry for running late today 17:20:34 no worries 17:20:38 no problem 17:21:30 is there an agenda for the meeting? 17:21:46 I don't have much more to report. I've been fighting to upgrade a live cluster to Folsom. 17:22:20 There is a session on this and we (openstack) really need to do better. 17:23:15 davidkranz: I know. We were doing well for awhile, but then I know I slacked pretty bad 17:23:57 dwalleck: What did you have to do with the current situation? 17:24:30 Right now my priorities are swift branch -> nova admin api tests -> instance verification additions 17:24:58 dwalleck: I think the problem is that openstack upstream is not doing a good enough job of describing how a live cluster could be upgraded. 17:25:15 And then each distro introduces its own complications. 17:25:42 davidkranz: Maybe I misunderstood. I thought you were referring to better planning, and I was referring to the fact that I know I wasn't able to fufil my meeting captain responsibilities for a few months 17:25:42 But we can discuss this at the summit. 17:26:00 dwalleck: No, I was referring to the upgrade issue. 17:26:11 ahh, ignore me then 17:27:24 dwalleck: I think the best thing we can do at the summit is to get blueprints for what we decide needs to get done and really try to 17:27:28 get more people involved. 17:27:54 agreed 17:28:34 ++ 17:28:50 is there a list of QA/ test pain points that need to be addressed? or is that the summit topic list? 17:28:58 dwalleck: For the "bringing QA into the open session", I am going to try to get QA people from the major players to show up. 17:29:38 torandu: These should be covered by the summit session. If there is something you think is missing, please let me know. 17:30:00 torandu: pretty much the same as last summit... a) parallel execution/speeding up test runs, b) monitoring skips over time, c) overcoming limits of nose, d) automating the collection of coverage stats for non-unit tests 17:30:06 We have 6 hours of scheduled time. 17:33:06 Anything else? 17:33:32 No, just going to review and code 17:34:10 dwalleck: OK, review and debug for me :) 17:34:20 can do 17:34:30 nothing from me at this time. I got the feedback re review 14030. I'll make the changes asap & continue w/ tempest wrk 17:37:30 has anyone taken a look at the grenade code? any initial thoughts on that? 17:38:01 I saw the name in the schedule, but I don't think I've seen the purpose or project code 17:38:07 https://github.com/nebula/grenade 17:38:32 torandu: I looked a little. It should solve the upstream part of the upgrade issue. 17:39:08 torandu: But not, I think, the rolling upgrade issue which is critical. 17:39:39 ok. is the summit list "the list" or still under review as proposals? 17:39:55 torandu: Still under review until tomorrow. 17:40:27 I have to step out for three minutes. 17:40:29 ah. ok. presumably, we'll solicit or add more detail once finalized. y/n? 17:41:13 And I didn't notice if we them this time around, but last time we free-formed an unconference to go through things not on the schedule 17:45:12 anything else for now? 17:45:21 dwalleck: We can do that again. 17:46:24 dwalleck: I will leave the last Wed session open and we can unconference on Wed afternoon and/or Thur. 17:46:29 that sounds great. I haven't been before, so don't know what to expect. how did you make ppl aware of the unconference topics? 17:47:19 torandu: I don't think we did but we should this year. There is a "board" to write them. 17:47:38 davidkranz: ok. sounds good. I don't want to miss anything. :) 17:48:15 torandu: No worries. You are guaranteed to miss things with so much going on at once. 17:55:38 #endmeeting