21:00:21 #startmeeting nova 21:00:22 Meeting started Thu Apr 12 21:00:21 2018 UTC and is due to finish in 60 minutes. The chair is melwitt. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:26 The meeting name has been set to 'nova' 21:00:28 howdy everyone 21:00:29 \o 21:00:34 o/ 21:00:35 รถ/ 21:00:39 o/ 21:00:52 let's get started 21:00:59 #topic Release News 21:01:07 #link Rocky release schedule: https://wiki.openstack.org/wiki/Nova/Rocky_Release_Schedule 21:01:19 r-1 milestone is next thursday 21:02:03 so be thinking about what we want to get into r-1 and the stable branches by the milestone 21:02:15 and get your backports in order for those releases 21:02:32 #link Rocky review runways: https://etherpad.openstack.org/p/nova-runways-rocky 21:03:00 we had two blueprints leave runways this morning for their end dates 21:03:22 and they've been added to the Log area of the etherpad. please add comments in the Log area for relevant blueprints to help us capture how it went 21:03:37 two new blueprints have been added to runways in their place 21:03:43 #link runway #1: Add z/VM driver [END DATE: 2018-04-26] series starting at https://review.openstack.org/#/c/523387 21:03:44 patch 523387 - nova - z/VM Driver: Initial change set of z/VM driver 21:03:52 #link runway #2: Certificate Validation [END DATE: 2018-04-16] series starting at https://review.openstack.org/#/c/479949 21:03:52 patch 479949 - nova - Implement certificate_utils 21:03:59 #link runway #3: Placement forbidden traits [END DATE: 2018-04-26] series starting at https://review.openstack.org/#/c/556472 21:04:00 patch 556472 - nova - [placement] Filter resource providers by forbidden... 21:04:24 please do make these runways blueprints your priority for review 21:04:30 * efried adds zvm to stuck reviews... 21:04:51 yeah, there are some complications in the zvm series already 21:05:14 mikal: you around to defend yourself? 21:05:28 I'll defend him 21:05:39 so I was thinking we might have to move that one back into the queue if we can't move forward and then revisit it later. there are some issues around the config drive format and lack of tempest verification of it 21:06:01 do we want to talk about that here or in stuck reviews? 21:06:09 let's do it in stuck reviews 21:06:14 ack 21:06:34 let's move on and we'll talk about this in stuck reviews 21:06:50 does anyone have anything else for release news? 21:07:08 tempest does verify config drive 21:07:23 clarkb: they have set run_validation = False in their tempest.conf 21:07:25 clarkb: not when tempest is configured not to verify the guests at all 21:07:30 oh gotcha 21:07:53 #topic Bugs (stuck/critical) 21:08:07 no critical bugs in the link 21:08:15 #link 32 new untriaged bugs (down 5 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 21:08:33 #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags 21:08:51 thanks to those who've helped get our untriaged bugs down. more help would be appreciated 21:08:57 #link 6 untagged untriaged bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 21:09:15 bugs have mostly been categorized, though I have noticed a lot of use of unofficial tags on the NEW bugs 21:09:23 #help tag untagged untriaged bugs with appropriate tags to categorize them 21:09:29 #link 5 untriaged libvirt bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW 21:09:34 #link 3 untriaged live-migration bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+&field.status%3Alist=NEW 21:09:39 #link 4 untriaged volumes bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+&field.status%3Alist=NEW 21:10:00 libvirt, live-migration, and volumes bugs have a chunk of untriaged bugs 21:10:13 #help If you have familiarity with any of these categories, please help triage (set validity and importance) 21:10:28 #link check queue gate status http://status.openstack.org/elastic-recheck/index.html 21:10:50 I'm still noticing some TIMED_OUT occasionally. I haven't yet verified if those are the limestone hosts again 21:10:58 https://bugs.launchpad.net/nova/+bug/1763382 - nova-multiattach job failing since using Queens UCA 21:10:59 Launchpad bug 1763382 in OpenStack Compute (nova) ""libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied" in nova-multiattach job since we started using the Queens UCA" [High,In progress] - Assigned to Matt Riedemann (mriedem) 21:11:29 gate bug that mriedem_funtime has been working on. he said it's semi resolved at this point. thanks to mriedem_funtime for working on that one 21:11:44 another gate bug https://bugs.launchpad.net/nova/+bug/1763181 - test_parallel_evacuate_with_server_group intermittently fails 21:11:44 Launchpad bug 1763181 in OpenStack Compute (nova) "test_parallel_evacuate_with_server_group intermittently fails" [Medium,Confirmed] 21:12:01 if anyone wants to help look into that 21:12:09 #link 3rd party CI status http://ci-watch.tintri.com/project?project=nova&time=7+days 21:13:01 does anyone have anything for bugs or gate status? 21:13:25 #topic Reminders 21:13:31 #link Rocky Review Priorities https://etherpad.openstack.org/p/rocky-nova-priorities-tracking 21:13:56 the usual reminder about the priorities etherpad as a place to highlight subteam patches and bug fixes 21:14:26 anything else for reminders? 21:14:47 #topic Stable branch status 21:14:52 #link stable/queens: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/queens,n,z 21:14:58 #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z 21:15:13 #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z 21:15:28 we have a fair number of backports, especially on ocata 21:15:47 we will need to push through some review on those in preparation for r-1 21:16:14 does anyone have anything else for status branch status? 21:16:33 #topic Subteam Highlights 21:16:49 dansmith: cells v2, we skipped the meeting this week. anything else you'd like to highlight? 21:16:53 nay 21:17:31 k. if anyone is interested, cells v2 patches up for review are collected on the priorities etherpad in the cells v2 section 21:17:36 edleafe: scheduler? 21:17:41 Decided that requiring placement would be a graceful fail in Rocky, and a hard fail in Stein. 21:17:44 jaypipes shocked us all by being nice at the beginning of the meeting. 21:17:47 We still sat in awe of the sheer number of specs and reviews on our respective plates. 21:17:50 Our original idea was to track priorities in the Nova priorities etherpad, but no one, myself included, did that. 21:17:53 We agreed that we already have something of a priority list in cdent's placement update email. So for now we'll use that as a starting point, and if anyone wants changes, the weekly team meeting will be the time to do that. 21:17:57 jaypipes further shocked us by agreeing that efried was right about the semantics of granular requests. 21:18:00 Finally, we agreed that there would be a separate #openstack-placement channel. cdent agreed to set it up. This will help reduce the volume of stuff on the -nova channel. From now on please discuss placement issues on -placement. 21:18:04 fini 21:18:51 I thought placement has been required since ocata? 21:19:18 yeah, I don't think it should be optional in rocky 21:19:38 mriedem_funtime was proposing that 21:19:46 we've been saying it's required since ocata 21:19:49 for the placement agg mirroring 21:19:55 wait, was it ocata? I might be confusing it with cells requirement, 21:19:58 but even still, 21:20:10 yeah, I was under the impression that things won't work >= Ocata without placement 21:20:24 if we don't require it in rocky, we can't really expect people to have data in there for a switchover from cachingscheduler in S right? 21:20:30 me too, but mriedem_funtime seemed to be concerned 21:20:40 that confuses me muchly 21:20:40 http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-04-09-14.00.log.html#l-46 21:20:45 I guess we can chat about that later 21:21:02 yeah. let's chat about it later 21:21:05 edleafe: that's about requiring placement in api right? 21:21:09 not placement altogether 21:21:21 because api config hasn't had placement config requirements yet 21:21:38 dansmith: ah, ok. That distinction was lost on me 21:21:44 pretty sure that's what he's talking about there 21:21:46 So does that make more sense now? 21:21:50 yes 21:21:53 kewl 21:22:30 okay, I'm not sure what that means so I'll look at it after this 21:22:48 and thanks for bringing up the new #openstack-placement channel. might want to do a separate ML post to alert people about it 21:22:56 That happened 21:23:05 * efried finds... 21:23:13 on its own thread? okay. I didn't see other than the placement update thread 21:23:30 http://lists.openstack.org/pipermail/openstack-dev/2018-April/129215.html 21:23:34 oh, yeah, not on its own thread. 21:23:38 cdent ^^ 21:24:12 I guess copied to ops 21:24:13 gibi_awa1 is still on vacay so there's not been a notifications meeting this week 21:24:31 he will be back next week 21:24:33 I saw a lot of notification dedup patches go by. He'll have fun with those when he gets back. 21:24:41 heh, yeah 21:24:55 anything else for subteams? 21:25:12 #topic Stuck Reviews 21:25:21 zvm time 21:25:36 https://review.openstack.org/#/c/523387/ -- ZVM initial patch. 21:25:37 patch 523387 - nova - z/VM Driver: Initial change set of z/VM driver 21:25:44 FWIW, I don't think the requirements thing is the major concern with that stuff 21:25:48 Note: I didn't put the config drive one on here because I believe we're waiting for further details from Jichen on how that works. 21:25:59 it's a concern, and I think we should make some progress on doing better there 21:26:09 but I also don't really think this warrants stuck-review status yet, 21:26:11 yes, I agree the requirements thing is not a major issue 21:26:15 since the concerns are like 24 hours old 21:26:41 I will say that I think the configdrive thing, if unresolvable, is a big red flag to me 21:26:49 but we have time to let that play out yet 21:27:15 yeah, that is my view as well