21:00:46 #startmeeting nova 21:00:48 Meeting started Thu Nov 20 21:00:46 2014 UTC and is due to finish in 60 minutes. The chair is mikal. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:51 The meeting name has been set to 'nova' 21:00:53 o/ 21:01:11 #topic Kilo specs 21:01:11 o/ 21:01:18 So, perhaps this isn't the best title ever 21:01:26 But I wanted to highlight the priority tracking etherpad 21:01:34 #link https://etherpad.openstack.org/p/kilo-nova-priorities-tracking 21:01:44 Seems most people have found it now, its got a fair bit to review on it 21:01:48 FWIW, 21:01:53 So... cores please take a look and review some of those things 21:02:06 Any other comments on priority tracking? 21:02:07 I've already hit several of the reviews listed and really like having the list 21:02:14 Good 21:02:20 I think we should cross those off as they merge 21:02:21 having the list is nice 21:02:26 And then do a weekly cleanp 21:02:29 cleanup even 21:02:38 at the bottom I included my patch to add the priorities to nova-specs 21:02:49 Yep, I saw that. I think that's a fair thing to do. 21:03:13 Anything else on that? 21:03:30 Oh, I did that backwards 21:03:32 spot checking, I saw a few -2s on there 21:03:41 I was meant to be talking about spec approvals first 21:03:42 jogo: where? 21:03:47 such as https://review.openstack.org/#/c/102545/ 21:04:12 that was procedural, but yeah 21:04:25 Ahhh, we should ping John about that one 21:04:32 So... 21:04:37 I think it's most helpful if the things on that list are added by the priority owner as "ready to review" and "important to review next" 21:04:37 What I was meant to talk about in this topic 21:04:46 Does anyone have any spec fast track requests? 21:05:25 dansmith: yeah, I'd like the list to be short... If its 100's of patches it wont help. 21:05:40 So... no fast track requests this week? 21:05:55 Moving on in 3... 21:05:56 nova-specs can use some review love though 21:05:56 yeah, I can just see this being a place where people put their reviews they want looked at, given that it's just an etherpad 21:06:14 dansmith: we shall prune with vigour 21:06:29 jogo: yeah, I've been on vacation this week. I promise to take a look next week. 21:06:34 Let's move on 21:06:41 #topic Gate status 21:06:46 So, I've been on vacation... 21:06:50 How broken is everything? 21:07:01 mikal: not very 21:07:06 Yay! 21:07:12 earlier in the week things seemed unhappy 21:07:17 There are no critical gate bugs at the moment? 21:07:20 but in the last 24 hours things seem better 21:07:34 there have been some dependency issues 21:07:39 but not nova related 21:07:45 things like http://bugs.launchpad.net/bugs/1394408 21:07:47 Launchpad bug 1394408 in oslo.vmware "suds-jurko' is not a global requirement " [Undecided,Fix committed] 21:08:09 nova wise things are pretty calm 21:08:22 top nova bug http://status.openstack.org/elastic-recheck/#1370496 that we are tracking 21:09:19 Oh, that ssh timeout is still a thing? 21:09:28 Wow, thats one long lived bug 21:09:40 yeah its a catch all bug 21:09:56 we've fixed several real things, and I imagine there are several still remaining 21:10:03 but it's a wall that is hard to see past 21:10:10 trying to get classification rates up now 21:10:25 but so far nothing new and surprising for nova in the gate 21:10:30 Ok 21:10:36 Should we move on from this topic then? 21:10:42 Sounds like its not too terrible this week 21:11:14 mikal: things go well when your away, coincidence? 21:11:28 I am happy to go on permanent vacation if you think its called for... 21:11:32 #topic Open Discussion 21:11:45 So... This could be a record short nova meeting if we play our cards right... 21:11:52 Anything else we need to discuss? 21:12:00 mikal: https://bugs.launchpad.net/nova/+bug/1345460 21:12:03 Launchpad bug 1345460 in nova "VMware: resize fails when there is more than one compute node" [High,In progress] 21:12:13 mikal: someone seems to keep tagging that as critical 21:12:16 which is very anoying 21:12:47 +1 21:12:50 Sigh 21:13:39 So, sounds like something we should ask John to discuss in the next EU meeting when more of the vmware people are around 21:13:44 I've seen this on a few bugs 21:13:46 mikal: ++ 21:13:59 Tracy fixes it, but other people aren't listening 21:14:31 So, no meeting next week I assume 21:14:41 But I'll add it to the agenda after this so we don't forget to cover it 21:14:45 Anything else? 21:15:10 Or I could send an openstack-dev email I suppose 21:15:17 I think I can find something else 21:15:22 * jogo digs through specs 21:15:26 Heh 21:15:33 there is a push to get more PXE boot support 21:15:47 Which hypervisor? 21:15:48 libvirt? 21:15:48 and the question of should we block docker if it doesn't have volume support 21:15:51 libvirt 21:15:54 * jogo finds the spec 21:15:57 s 21:16:08 Ahhh, so I promised to do a thing with the hypervisor support matrix and haven't yet 21:16:13 I need to get onto that next week 21:16:22 I feel like the volume question should be driven by that conversation 21:16:23 https://review.openstack.org/133254 21:16:31 i.e. set a standard, then hold everyone to it 21:16:43 docker: https://review.openstack.org/128753 21:18:17 jogo: do you disagree with the hypervisor support matrix plan? 21:18:42 mikal: sounds reasonable to me 21:18:47 Cool 21:18:52 (me too) 21:18:54 So, we'll do that then 21:18:54 mikal: as long as volume support is required that is 21:18:57 but yeah sounds good 21:19:02 Heh, well... 21:19:03 heh 21:19:11 Specifics of what is required is part of that conversation 21:19:16 So let's defer that for now 21:19:24 So... can I end this meeting? 21:19:26 Pretty please? 21:19:38 Then y'all could go nap for 40 minutes 21:19:40 early mark! 21:19:44 LOL 21:19:59 Here endeth the meeting 21:20:06 #endmeeting