16:00:30 #startmeeting nova 16:00:34 Meeting started Thu Mar 11 16:00:30 2021 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:37 The meeting name has been set to 'nova' 16:01:18 o/ 16:01:37 o/ 16:02:03 o/ 16:02:15 ~o~ 16:02:25 #topic Bugs (stuck/critical) 16:02:30 No Critical bugs 16:02:35 #link 18 new untriaged bugs (+5 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:02:43 \o 16:02:51 I've closed ~80 bugs opened about fault injections 16:03:07 it was fun 16:03:23 :O 16:03:24 is there any bug we need to talk about here? 16:03:52 (btw this was the first fault injection bug https://bugs.launchpad.net/nova/+bug/1918340 ) 16:03:53 Launchpad bug 1918340 in OpenStack Compute (nova) "Fault Injection #1 - improve unit test effectiveness" [Undecided,Incomplete] 16:04:26 fun 16:04:35 gibi: sorry you had to go through that :) 16:04:56 we can spend time on the bug backlog next week, I guess 16:05:03 sure 16:05:05 o/ 16:05:10 niice 16:05:26 if no needy bug then moving on 16:05:26 #topic Gate status 16:05:34 gate is in a shape as expected around FF 16:05:56 pretty decent, considering actually 16:06:03 please try to recheck only things that are either bugs or has a chance to be approved before EOB today 16:06:16 s/bugs/bugfixes/ 16:06:43 #topic Feature status 16:06:58 let meg copy a list from the agenda 16:07:03 #link https://blueprints.launchpad.net/nova/+spec/nova-support-webvnc-with-password-anthentication : in merge conflict with negative review so I assume it is deferred from Wallaby 16:07:11 #link https://blueprints.launchpad.net/nova/+spec/compact-db-migrations-wallaby : patches has been approved, implementation going through the gate 16:07:19 #link https://blueprints.launchpad.net/nova/+spec/modernize-os-hypervisors-api : merged, the policy part is deferred out from Wallaby 16:07:20 * bauzas is around 16:07:28 #link https://blueprints.launchpad.net/nova/+spec/libvirt-default-machine-type : merged, except the integration testing. That can still land after FF. 16:07:38 #link https://blueprints.launchpad.net/nova/+spec/pci-socket-affinity : expected to be approved today 16:07:44 #link https://blueprints.launchpad.net/nova/+spec/port-scoped-sriov-numa-affinity : expected to be approved today 16:07:49 #link https://blueprints.launchpad.net/nova/+spec/libvirt-vdpa-support : still open 16:07:53 #link https://blueprints.launchpad.net/nova/+spec/allow-secure-boot-for-qemu-kvm-guests : still open 16:08:04 for nova-support-webvnc-with-password-anthentication, we're deferring 16:08:05 the secure boot series got +Wd 16:08:05 the rest is either merged or in a shape that means it is deferred 16:08:21 bauzas: thanks that is good news 16:08:33 stephenfin: ack 16:08:34 Melwitt and I took a close look at it and there were some serious issues with usability that meant we weren't happy merging it 16:08:42 we still have a few patches up, but those are FUPs that can merge after FF 16:08:56 bauzas: sure 16:09:23 is there any other bp that I'm not listed up there but the author still thinks it has a chance to land? 16:09:30 regarding https://blueprints.launchpad.net/nova/+spec/libvirt-vdpa-support I've been going through that with Sean and helping them reorder things so they're fit to merge. I've gone through it with a fine comb now and am happy with all but a few things 16:09:56 problem is you need some PCI knowhow to really review, hence why it's got so few eyes I suspect 16:10:26 I can take a look at one series before I time out for today 16:10:39 so if nothing else pops up then I will look at the vdpa 16:11:22 that would be great 16:11:30 one more thing I not listed above is the smartnic support. I finished with the review today but I had a lot of findings so I assume that is also deferred 16:12:05 anything else about features? 16:12:46 the other thing I had on my list was the change to enable 'openstack server --hostname' 16:12:56 it's small, but it's had no attention so I think we should defer 16:13:00 and merge early in Xena 16:13:06 yeah, I had no time to dig into that 16:13:12 sorry 16:13:16 is that just an osc thing, 16:13:18 All good. I left it late 16:13:19 or requires an api? 16:13:24 Nah, microversion change 16:13:42 okay 16:13:46 just a new field in the request, but any microversion change brings a lot of boilerplate changes with it 16:13:54 *server create request 16:13:55 sure sure, 16:14:03 just wasn't sure if we had it already and just needed to pass it or not 16:14:28 not yet, no 16:14:32 change is here for context https://review.opendev.org/c/openstack/nova/+/778550 16:14:48 (ignore the fail - it's irrelevant) 16:15:02 but like I said, I'm happy to defer. This was really a nice-to-have 16:15:10 yup. I was just curious 16:15:18 ack 16:15:21 anything else? 16:15:36 not from me 16:15:41 #topic Release Planning 16:15:48 so we have Feature Freeze today EOB 16:16:03 FFE process posted on the ML #link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020772.html 16:16:11 but I not expecting FFE requests 16:16:49 So from tomorrow lets focus on high priority bugs and patches that preparing the RC1 16:16:54 RC1 is in two weeks 16:17:15 (and do the rechecks for the already approved things_) 16:17:19 I think we're looking for another rev of the rpc bump 16:17:35 I can put my eyes on it when needed 16:18:27 release todos are tracked on the etherpad #link https://etherpad.opendev.org/p/nova-wallaby-rc-potential 16:18:54 like cycle highlights, reno prelude and other necessities 16:19:37 also please use wallaby-rc-potential tag on bugs that you consider warranting a new RC if fixed 16:19:55 Currently there are none, FWIW 16:19:58 (Yey?) 16:20:13 because we are awesome and everything works :) 16:20:37 any other release related topic to discuss 16:20:38 ? 16:20:41 * dansmith hopes those words tase good later 16:20:44 *taste 16:21:01 I'm not naive I'm sarcastic :) 16:21:30 heh I know :P 16:21:36 :) 16:21:47 oh one more thing the TC and PTL nominations are closed this week 16:22:04 as thing looks you stuck with me as the PTL for the next 6 months 16:22:34 \o/ 16:22:52 #topic PTG planning 16:22:59 PTG date had been announced: April 19-23, 2021 16:23:05 Use the PTG etherpad to collect topics: #link https://etherpad.opendev.org/p/nova-xena-ptg 16:23:18 Please fill the doodle about the timing of the nova slots before end of next week #link https://doodle.com/poll/ib2eu3c4346iqii3 16:23:36 as I have to "book" those virtual roomns 16:23:57 any questions about the PTG? 16:24:12 gibi: did you have a deadline in mind for topics? 16:24:51 I will do etherpad reorg before the PTG week 16:25:13 so that is sort-of deadline. anything comes after might end up at the end of the pad 16:25:33 yeah ack that's fine, just something to keep in mind as stuff comes in from downstream ;) 16:25:55 but if you have topics that needs more than the nova team (e.g. cinder, neutron, cyborg) then please prioritize those as we need to find a common time with the other teams then 16:26:07 yup understood 16:26:40 anything else about the PTG? 16:27:09 #topic Stable Branches 16:27:20 copying elod's update from the agenda 16:27:23 lyarwood found issue with ceph plugin, that seems to block now *train* and older branches -- fix: https://review.opendev.org/c/openstack/nova/+/780014 16:27:27 victoria + ussury should be OK 16:27:32 elod prepares victoria + ussuri + train(?) release patches tomorrow, March 12th 16:27:35 EOM 16:27:51 thanks elod 16:27:55 FWIW I had nothing urgent to land ahead of the releases elod 16:28:12 lyarwood: ack 16:28:53 if nothing else then I skipping over the libvirt subteam topic as bauzas told me that nothing to report there 16:29:08 #topic Open discussion 16:29:12 nothing on the agenda 16:29:19 is there anything we need to discuss? 16:29:28 I have a thing 16:29:51 go 16:30:07 so, I want to do that funny thing and ask a glance question in the nova meeting.. BUT I have a good reason :) 16:30:23 is anyone here familiar with the glance metadef api, how it may be used, and by who? 16:30:33 the reason I ask is that it seems mostly there to collect nova-related metadata 16:31:16 as was noted earlier on the list, there are multiple low-grade security problems with the API, and the glance team needs some info from people that actually use it in order to know how and when to fix it 16:31:37 since it's nova metadata (i.e. image metadata that affects instances) related, I thought maybe someone here might know 16:32:13 dansmith: sean isn't here, weirdly, but they talk about it a lot 16:32:19 besides some common image metadata usage I did not see metadef usage in our downstream bug tracker 16:32:41 gibi: ack, that's good to know, not in ours either :) 16:32:55 stephenfin: ah yeah I thought sean might be a candidate, but didn't notice he wasn't in here 16:32:58 they wanted to use it for the extra spec validation stuff we did in microversion 2.87 but we found it was mega out-of-date and the definitions were really hard to define/extend 16:33:12 xml-- iitv 16:33:14 *iirc 16:33:43 so they thought maybe it would be useful, but decided not to try, is that right? 16:33:44 not.. are using it, or were using it, or.. 16:34:10 yeah, correct. I added that microversion and just went with our own schema format 16:34:19 it seems to be a "feature" that was "designed" and dropped on the community all in a short period, and then the originators are all long gone, 16:34:31 yeah, that's my impression too 16:34:32 so it's hard to know if anyone actually uses it, whether it serves any purpose anymore, etc 16:34:35 I think Horizon might use it too 16:34:51 yeah, horizon and heat are the two things we're wondering about 16:34:56 when you're creating the guest I see some "CIM" metadata and I think that's coming from the Glance API 16:34:57 horizon was one of the original goals, I think, but.. 16:35:16 okay there are some CIM things in there by default, so maybe that's right 16:35:51 if it were an option, deprecating it in Glance might make more sense. nova already validates image metadata and flavor extra specs for you 16:35:56 by default, it's completely wide open, any user can create anything they want, and as much as they want (until the DB is full), and there isn't proper tenancy protection 16:36:08 deprecating is an option, 16:36:21 we're recommending disabling it in policy by default and unless you want or need it for something 16:36:31 but we want to know if we should fix or deprecate 16:36:43 and we (nova) could add an API if people wanted a way to retrieve information about the metadata we support (extra specs and image meta props) ahead of time, though I suspect that's a very small use case 16:36:52 I think the goal is to make things like horizon able to offer up common metadata, not so much for the validation part 16:37:25 yeah, basically a serialized ImageMetadataProperties representation I guess 16:37:38 yeah 16:37:50 nova at least will ignore everything else 16:37:58 though nova isn't the only thing talking to glance of course 16:38:05 aight, so gibi you just checked your downstream bug tracker in response to the OSSN I guess to see if your customers were using it? 16:38:13 or at least, reporting issues with it I guess 16:38:17 yes 16:38:24 (I say of course but I'm not actually sure if anyone else talks to Glance) 16:38:25 nothing really popped up 16:38:29 and are you planning to just push out policy to disable? 16:38:55 I don't have the infor about that yet 16:38:57 but I can ask around 16:39:07 okay 16:39:07 I would disable with policy yes 16:39:45 okay, well, we're asking ops to come to ptg with use cases or data about it, 16:40:05 not sure if we'll get any, but if you have anything that comes from asking that you want me to point out there, let me know 16:40:26 and I'll poke sean after this 16:40:32 that's all, thanks for the discussion 16:40:33 sounds good 16:40:45 anything else for today? 16:41:55 then thanks for joining today. Happy FF folks! :) 16:42:07 thanks! o/ 16:42:12 #endmeeting