21:00:13 #startmeeting nova 21:00:14 Meeting started Thu Aug 3 21:00:13 2017 UTC and is due to finish in 60 minutes. The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:17 The meeting name has been set to 'nova' 21:00:26 o/ 21:00:34 \o 21:00:35 \o 21:00:39 o/ 21:00:47 o/ 21:01:03 #link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 21:01:11 ok let's get started 21:01:15 #topic release news 21:01:20 #link Pike release schedule: https://wiki.openstack.org/wiki/Nova/Pike_Release_Schedule 21:01:25 #info August 10 (1 week) is Pike RC1 21:01:35 #info Blueprints: 53 targeted, 53 approved, 46 completed (+13 from last week) 21:02:01 ^ the number completed is actually more since i haven't closed out the multi-release things, like api-ref in rst, and config option cleanup 21:02:23 but with no more FFEs I don't expect anything besides those to be news 21:02:38 #link Pike RC1 TODO etherpad: https://etherpad.openstack.org/p/nova-pike-release-candidate-todo 21:02:52 ^ is me trying to focus what's going on for the RC1 21:03:11 any questions about the release? 21:03:21 #topic bugs 21:03:28 there are no critical bugs 21:03:32 #info 0 new untriaged bugs (down 59 from last week - thanks sdague) 21:03:47 #info pike-rc-potential bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=pike-rc-potential 21:04:03 there is only one rc potential bug that hasn't been started yet 21:04:08 and that's handling shared storage in the compute 21:04:14 compute/report client 21:04:24 i'm not sure if jaypipes or dansmith have talked about it 21:04:34 ugh 21:04:46 let's talk about that when we unfsck the current stuff 21:04:51 i suppose the first step is a regression test for creating a server with a shared storage provider between compute nodes and asserting what we expect 21:04:54 yup 21:04:59 i can work the test in parallel 21:05:18 although what we expect isn't entirely clear to me yet, but we'll get there 21:05:30 gate status is pretty good 21:05:32 no news there 21:05:38 same for 3rd party ci 21:05:46 anything for bugs? 21:05:58 #topic reminders 21:06:04 #link Consider signing up for the Queens PTG which is the week of September 11 in Denver, CO, USA: https://www.openstack.org/ptg 21:06:12 #link Pike PTG topics etherpad: https://etherpad.openstack.org/p/nova-ptg-queens 21:06:18 ^ is starting to fill up 21:06:23 it's all very random right now 21:06:32 we'll sort it out after the pike stuff settles down 21:06:50 having 5 days seems like it will be a luxury compared to the forum 21:07:04 #info PTL nominations for Queens are open (July 31 - Aug 9): https://governance.openstack.org/election/ 21:07:24 anything for reminders? 21:07:38 #topic stable branch status 21:07:50 we've got a bunch of open ocata and newton changes, 21:08:03 as i said last week, i think we'll do a review push on those after pike rc1 probably 21:08:05 or around that time 21:08:19 so we can do some stable point releases after pike rc 21:08:20 *rc1 21:08:36 #topic subteam highlights 21:08:43 there was no cells v2 meeting this week 21:08:50 but there are some nice new multi-cell docs 21:09:07 #link new multi-cell v2 docs https://docs.openstack.org/nova/latest/user/cellsv2_layout.html 21:09:23 dansmith: anything else you want to say about cells v2? 21:09:31 nothing nice, no 21:09:38 alright then 21:09:41 edleafe: around for scheduler? 21:09:44 Most of the meeting was discussing the issues we've been fighting with migration/resizing. So has most of the rest of the week. 21:09:47 I've been going back and forth with the ironic folks regarding the flavor migration code. Seems like there's always one more case that needs to be covered. :) 21:09:50 Note that the amended spec for ironic instance flavor migration has not yet been approved 21:09:53 #link Amend spec for Custom Resource Classes in Flavors https://review.openstack.org/#/c/481748/ 21:09:56 EOM 21:10:06 mriedem: landing that is just paperwork right? 21:10:13 the spec amendment? 21:10:14 yeah 21:10:15 yes 21:10:16 okay 21:10:31 mriedem: you haven't +2d just because it's not a priority right? 21:10:36 like, I should +2 21:10:39 i'd also like to see jaypipes' request candidates spec cleaned up and approved at some point for similar reasons - docs more than anything 21:10:45 dansmith: i wrote it 21:10:47 i can't approve it 21:10:49 oh hah 21:10:53 thought it was ed 21:11:17 api - i don't know if there was a meeting this week 21:11:19 sdague: ? 21:11:20 not me 21:11:34 only thing left for api is some docs for the new route map stuff 21:11:37 that gmann is working on 21:11:52 there as no notification meeting this week 21:11:59 there was a short cinder meeting today, 21:12:18 apparently cinder-api with uwsgi broke the version discovery code in cinderclient, similar to what happened with nova-api + uwsgi in novaclient 21:12:26 so they are working a fix and will just have to backport, 21:12:38 since the new cinder api integration didn't land in nova in pike it's not a huge impact to us anyway 21:12:59 ildikov has been working on chasing some issues in the api integration patch which we can hopefully land early in queens, before the ptg 21:13:13 #topic stuck reviews 21:13:23 nothing in the agenda 21:13:29 does anyone need to bring something up here? 21:13:42 #topic open discussion 21:13:46 nothing on the agenda 21:13:51 anyone need to say something? 21:14:00 shortest meeting evar? 21:14:03 I've got a stupid question. 21:14:10 jangutter: damn you! 21:14:12 adding/removing sr-iov ports. 21:14:23 we've had shorter 21:14:25 Anyone looked at it lately? 21:14:29 jangutter: no, 21:14:35 there was/is a spec somewhere 21:14:45 Yep, it's archealogical. 21:14:54 https://review.openstack.org/#/c/139910/ 21:15:14 So, I guess the correct way to approach it is to propose it for queens? 21:15:16 yup that's the one i was thinking of 21:15:44 yeah 21:15:46 I guess if it was low-hanging fruit, someone would've done it by now :-p 21:16:12 Anyway, thanks, just wanted to know if someone was messing around in that neighborhood. 21:16:28 i don't know if anyone else is working on something like this 21:16:38 but it's nfv so probably 21:17:08 anything else? 21:17:22 alright thanks everyone 21:17:24 #endmeeting