21:00:14 #startmeeting nova 21:00:14 Meeting started Thu Mar 14 21:00:14 2019 UTC and is due to finish in 60 minutes. The chair is melwitt. 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 . 21:00:18 The meeting name has been set to 'nova' 21:00:24 hello all 21:00:26 o/ 21:00:27 welcome to the nova meeting 21:00:30 \o 21:00:47 https://wiki.openstack.org/wiki/Meetings/Nova 21:00:58 let's get started 21:01:00 #topic Release News 21:01:08 #link Stein release schedule: https://wiki.openstack.org/wiki/Nova/Stein_Release_Schedule 21:01:12 #info Stein RC1 is March 21 21:01:21 rc1 is one week from today 21:01:28 #link Stein RC potential changes tracking: https://etherpad.openstack.org/p/nova-stein-rc-potential 21:01:56 where are we at with ^? 21:01:59 what else needs to be done? 21:02:12 I was going to ask you that 21:02:17 there's a lot on there and most look done 21:02:38 docs things 21:03:04 i'll defer to the ptl for tracking what needs to be done for rc1 21:03:17 yeah, docs for minimum bandwidth stuff 21:03:25 and cycle highlights docs 21:03:44 everything else on the pad is done 21:04:01 i'm not sure abou tthat 21:04:10 https://review.openstack.org/#/c/538498/ and the compute driver capabilities as traits stuff isn't documented 21:04:35 is someone working on the prelude writeup for the release notes? 21:04:55 oh. ok, I thought the link was the merged docs patch. sorry 21:05:08 no, I'll be doing that 21:05:47 i'm assuming aspiers isn't around 21:05:57 efried: do you know if aspiers was going to document the capabilities as traits stuff? 21:06:33 I don't know, sorry. 21:06:36 anyway i guess he'll get the ping 21:06:43 i remember talking with him about it 21:06:48 I'll try to catch him tomorrow 21:07:41 ok, anything else for release news before we move on? 21:07:57 #topic Bugs (stuck/critical) 21:08:10 no critical bugs 21:08:15 #link 74 new untriaged bugs (up 7 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 21:08:21 #link 13 untagged untriaged bugs (up 6 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 21:09:14 need help with some bug triage, as usual. I'll go through today and tomorrow to see if anything is rc1 potential 21:09:15 #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags 21:09:16 #help need help with bug triage 21:09:24 Gate status 21:09:35 this is old, 21:09:36 #help nova-live-migration ceph setup not working on bionic: https://launchpad.net/bugs/1819944 21:09:37 Launchpad bug 1819944 in OpenStack Compute (nova) "nova-grenade-live-migration job failing on ubuntu bionic due to missing ceph package" [High,In progress] - Assigned to Dr. Jens Harbott (j-harbott) 21:09:45 there's a fix approved for this 21:09:48 but, 21:09:52 the change below it is not 21:10:11 now it is 21:10:34 I approved it earlier today 21:10:49 #help nova-next tls-proxy / vnc failing on bionic: https://launchpad.net/bugs/1819794 21:10:50 Launchpad bug 1819794 in OpenStack Compute (nova) "nova-next job fail on Ubuntu Bionic" [Medium,Confirmed] 21:11:15 I've been looking into this but of course would appreciate if anyone takes a look and has any ideas 21:11:43 libvirt/qemu unable to load cert. either a permission issue or something like that 21:12:07 bc the file is copied to the expected path by devstack tls-proxy setup code 21:12:19 #link check queue gate status http://status.openstack.org/elastic-recheck/index.html 21:12:29 is this the recursive error thing? 21:12:40 no 21:12:41 oh I guess, not, vnc 21:12:42 sorry 21:13:31 gate status, as you've probably seen on the ML, been wrangling with getting our jobs to work on bionic CI nodes, since they're changing the default from xenial to bionic 21:13:38 I think we're all good there now 21:14:11 3rd party CI 21:14:11 sort of, 21:14:29 the ceph job is broken on stable, gmann_afk has a patch, and the job is nv so it's low priority 21:14:43 https://review.openstack.org/#/c/643402/ 21:14:51 oh, ok. I didn't know about that one 21:15:22 ok, cool 21:15:58 I'll ping eharney tomorrow for that one 21:16:06 #link 3rd party CI status http://ciwatch.mmedvede.net/project?project=nova&time=7+days 21:16:33 anything else for bugs or gate status before move on? 21:16:58 #topic Reminders 21:17:03 (mriedem): Proposed Train community-wide goals need wider review: project deletion https://review.openstack.org/#/c/639010/ and migrate legacy CLIs to OSC https://review.openstack.org/#/c/639376/ 21:17:12 you want to talk on that mriedem? 21:17:42 not really, just advertising, but if people aren't involved in the goal selection / review process we'll end up getting whatever the tc decides 21:19:13 yeah. take a look and review the community goals, if you're interested ^ 21:19:26 I'll look at them...soon 21:20:03 ok, any other reminders before we move on? 21:20:27 vote! 21:21:25 (that is all. carry on.) 21:22:14 ... 21:22:23 yes, ptl election is going on now, so voting is open if you're interested 21:22:42 #topic Stable branch status 21:22:53 #info ocata/pike/queens changes are blocked on tempest-slow failures until https://review.openstack.org/#/c/643052/ 21:23:13 ok, that's good to know 21:23:37 I'll see if I can get another tempest core 21:23:59 #link stable/rocky: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/rocky,n,z 21:24:19 looks like one of those needs a recheck 21:24:45 #link stable/queens: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/queens,n,z 21:24:58 #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z 21:25:12 we're trying to flush through stable reviews so we can do some releases 21:25:27 stable review help appreciated. I'm trying to go through the rest of them 21:25:46 #help stable reviews 21:25:50 #link Pike extended maintenance is coming: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003745.html 21:26:28 ok, so the next pike release will be the last 21:27:05 anything else for stable branches before we move on? 21:27:23 #topic Subteam Highlights 21:27:30 efried: scheduler? 21:27:34 #link n-sch minutes http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-11-14.00.html 21:27:34 It was a quiet one. 21:27:34 #link DRY/clean up placement objects phase 2 https://review.openstack.org/#/q/topic:cd/de-list-phase2+(status:open+OR+status:merged) 21:27:34 ^ is going nicely 21:27:34 #link negative aggregate membership https://review.openstack.org/#/q/topic:bp/negative-aggregate-membership 21:27:34 agreed to hold ^ until Train 21:27:34 * mriedem has to leave 21:27:34 END 21:27:49 cool, thanks 21:27:57 no notes from gmann_afk for API subteam 21:28:06 moving on 21:28:08 #topic Stuck Reviews 21:28:16 nothing on the agenda. assuming no stuck reviews 21:28:23 #topic Open discussion 21:28:32 I have a thing 21:28:37 nothing on the agenda. does anyone have anything for op 21:28:42 ok, go ahead 21:28:48 earlier today, danpb noted he had some serious concerns about the SEV work: https://review.openstack.org/#/c/641994/ 21:28:59 much of the same that I expressed to adam when we were discussing in denver, 21:29:07 but danpb actually has the background to back it up :) 21:29:37 ok, yeah I saw a review from him come in on my notifications 21:29:38 anyway, that review from him (which accidentally cached a bad name) was toned down from his less filtered original wording about it 21:29:40 but.. 21:30:01 I think we probably want to encourage some re-design on that and not just shoot for rubber-stamp approval 21:30:09 it was also noted in a conversation, 21:30:31 that intel has a similar thing coming soon which is substantially different from this implementation, which makes it even more problematic 21:31:04 I don't really want to put my -2 on there because I know adam will come after me with incessant politeness, but.. we probably just want to make sure that doesn't land until we can discuss in denver or something 21:31:25 kashyap wasn't at the last denver when this was discussed, but will be at the next, and can probably proxy the concerns into a discussion 21:31:49 ok, that's good to know 21:32:45 (that is all) 21:32:46 dansmith: what's the intel thing? 21:32:53 efried: meaning what's it called? 21:32:56 I can try to chase that down 21:33:03 um, or where did you hear about it, or whatever 21:33:16 oh I heard about it from danpb himself 21:33:33 kashyap will have references if you want to catchyup him in the morning 21:33:40 that was cute 21:33:41 okay. 21:33:43 (seewhatIdidthere? 21:34:51 ok, I'll look through the spec and comment 21:34:56 thanks 21:35:07 anything else for open discussion before we wrap up? 21:35:30 ok, thanks everyone 21:35:34 #endmeeting