16:00:15 #startmeeting nova 16:00:16 Meeting started Thu May 20 16:00:15 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:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:19 The meeting name has been set to 'nova' 16:00:21 \o 16:00:27 o/ 16:00:30 \o 16:00:37 \o 16:00:44 ~o~ 16:00:52 o/ 16:01:44 lets roll 16:01:46 #topic Bugs (stuck/critical) 16:02:01 no critical bugs 16:02:06 8 new untriaged bugs (-4 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:02:18 triage backlog looks healthy 16:02:28 is there any bug we need to discuss? 16:03:15 good 16:03:16 :) 16:03:16 o/ 16:03:20 gmann: o/ 16:03:22 #topic Gate status 16:03:27 Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly 16:03:32 placement periodic seems green 16:03:45 huzzah 16:03:50 also I saw things merging to master 16:03:59 so the master gate should be in an OK state 16:04:20 is there any gate issue we need attention? 16:05:28 #topic Release Planning 16:05:39 Milestone 1 is 27th of May, which is next week 16:05:45 I proposed a spec review day for 25th of May, next Tuesday. #link http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022436.html 16:06:02 shout please if the date is not good for you 16:06:07 lgtm 16:06:28 * bauzas needs to create a new spec 16:06:52 * stephenfin too 16:07:11 any other release releated topic to discuss? 16:07:44 * gmann too 16:07:56 gmann, bauzas, stephenfin: can we merge the existing ones first please? (joking) 16:08:14 no. 16:08:17 * stephenfin has spoken 16:08:19 ;) 16:08:19 :) 16:08:21 :D 16:08:32 then moving o 16:08:33 n 16:08:39 #topic Stable Branches 16:08:45 copying elod's notes 16:08:50 "final train release" is out (20.6.1) - train-em patch is updated and ready for review & merge ( https://review.opendev.org/790761 ) 16:08:55 rocky / queens / pike blocked, due to grenade job failure, workaround proposed in devstack ( https://review.opendev.org/791246 ) 16:09:00 however wallaby..stein is not blocked, there are too many random failure: no merge happened in the last ~ two weeks... needs investigation 16:09:09 EOM 16:09:36 I pinged another devstack core for https://review.opendev.org/c/openstack/devstack/+/791246/ 16:09:36 once those are merged, we should fixup the release notes 16:09:50 and squash them for the eol releases 16:09:52 gmann: thanks! 16:10:13 * stephenfin will try find time to do that and reap the faster build time rewards 16:10:40 gmann: https://review.opendev.org/c/openstack/devstack/+/792108 is also an issue on stable/wallaby FWIW 16:11:07 and I'd really like to get the device detach stuff landed on wallaby as we are still seeing failures with the old logic there 16:11:11 lyarwood: ack, will check thi9s 16:11:29 lyarwood: I'm kicking the recheck button on the detach one 16:11:46 gibi: ack I'll try to spend more time on stable next week 16:11:54 thank you all. 16:12:27 if you see failures that are also on master (use the logstash while we still have it) then let me know and I will try to spend some time on them 16:12:54 anything else about stable? 16:13:20 nothing from me :X 16:14:04 #topic Sub/related team Highlights 16:14:08 Libvirt (bauzas) 16:16:13 I'm guessing bauzas has gone afk 16:16:25 ok 16:16:27 moving on 16:16:30 #topic Open discussion 16:16:34 (artom) Follow up on the IRC meeting schedule change. 16:16:42 thanks artom for the poll 16:16:52 it seems we have two possible slots on Tuesday 16:16:57 * stephenfin has an item here that wasn't on the agenda in time and will pipe up later 16:17:23 stephenfin: ack 16:17:29 whoops, sorry was otp 16:17:33 nothing to report, sir. 16:17:37 bauzas: ack thanks 16:17:39 (this ran fast) 16:17:54 so for the meeting 16:18:04 Tuesday from 15:00 UTC of from 16:00 UTC 16:18:21 * bauzas nods 16:18:32 everybody was happy with both slot 16:18:44 use your stick 16:18:59 then it is 15:00 UTC so I get off earlier :) 16:19:06 So the earlier one is 7:00 for dansmith and melwitt 16:19:14 Ah, no, 8:00 16:19:20 11 - 3 is 8, not 7 16:19:43 correct, but it's 7am for 2 weeks AFAICR 16:19:48 every 6 months 16:20:00 hm, that still means 7 during the winter, isnt it? 16:20:23 yeah 16:20:39 4pm for me in winter means 7am for west coast folks, indeed 16:20:41 Yeah, with the meeting pinned to UTC we go from -4 to -5 during winter here on the East coast 16:20:53 So it'd go from 8:00 to 7:00 for the folks on NA west coast 16:21:04 or ask them to move to France 16:21:05 ? 16:21:13 I'm sure dansmith would appreciate the relocation 16:21:29 * dansmith is double booked ... again :) 16:21:42 no worries, we just said you have to move 16:21:49 dansmith: is it UTC 15:00 or UTC 16:00 on Tuesday is better for you for the weekly meeting? 16:22:01 but... no kidding, we can do 1600, this sounds better 16:22:09 it's okay, won't work when DST ends, 16:22:11 but okay for now 16:22:17 and less invasive, as we usually took this slot on Thursdays 16:22:28 yeah after DST it will be 1 hr early 16:22:41 so it would only be a straight 48 hours move 16:22:45 OK, then let's have it from 16:00 UTC on Thuesday 16:22:52 any last words? 16:23:01 on the meeting time :) 16:23:11 nothing 16:23:13 maybe we could run office hours as asked by some contributors ? 16:23:19 #action gibi to move the meeting slot to Tuesday 16:00 UTC 16:23:36 like, I can reasonably assess to be around on 0800 UTC every week 16:23:37 bauzas: yes, I offered multiple option on the ML to the dev from China, but no response yet 16:24:03 my dog will just have to pee earlier on winter 16:24:09 I'm also happy to run formal meeting during one of the mornings one a month if that is usefull 16:24:23 s/one/once/ 16:24:34 well, maybe not 'official' meetings 16:24:42 but some kind of recorded office hours 16:25:04 and people could use this slot for reaching the nova community 16:25:22 no official decisions be made tho 16:25:40 hence the 'office hours' terminology 16:25:45 best of both worlds 16:26:02 bauzas: you are right we need keep the decision in this slot 16:26:09 where we have corum 16:26:23 quorum* but yeah :) 16:26:31 that one yes 16:26:38 my greek is bad :D 16:26:57 mine is just one word better than yours :p 16:27:08 ok moving on 16:27:11 okay, sold 16:27:15 stephenfin: you wanted to say something 16:27:51 yup, looking for specless BP approval 16:28:07 do you have a link ?:) 16:28:10 https://review.opendev.org/c/openstack/nova/+/792356/2 16:28:16 sorry, had to grab it 16:28:23 and BP is here 16:28:53 https://blueprints.launchpad.net/nova/+spec/multiqueue-flavor-extra-spec 16:29:06 so it is a new flavor extra_spec 16:29:13 yup 16:29:16 for me this sounds OK 16:29:19 any objections? 16:29:20 we provide a way to enable multiqueue via image metadata props 16:29:43 I'd like to extend that to the flavor. Patch is trivial and it helps operators (no need to rebuild) 16:29:48 * bauzas looks at the spec 16:29:56 well, the bP 16:30:08 ah lol 16:30:17 bauzas: the patch is better - that's where I have it explained https://review.opendev.org/c/openstack/nova/+/792356/2 16:30:23 I can copy paste that to the BP also :) 16:30:32 I think we said in the past that extra specs don't really need a spec, but there are things we need to consider 16:31:03 since we now have validation, would that mean a difference on the api side ? 16:31:15 There's nothing really new here. We already allow this to be configured via image metadata property 16:31:29 Yes, I've added a validator for that 16:31:32 (in the past, as those weren't constrained, we were free to add as much as we wanted, without care) 16:31:42 stephenfin, wait, did we consider the resize case? 16:31:55 artom: wdym? 16:32:05 stephenfin: I'm not an API specialist, but would this validator make a different experience between two clouds ? 16:32:10 'cuz now you can resize to/from that extra spec 16:32:11 gmann: thoughts on interop ? 16:32:24 bauzas: yeah, we've discussed that quite a few times before. Extra specs aren't part of the microversion 16:32:25 stephenfin, just... if there are any implications 16:32:30 * stephenfin should write this down somewhere 16:32:49 stephenfin: yeah, that's the point I recall 16:33:32 we decided that the same flavor on two clouds getting two different return codes for the same instance isn't a problem and doesn't require some signal 16:33:43 and I'm OK with this 16:34:23 bauzas: gibi: sorry for the late reply, I was on the other meeting that conflicts with this now. My TZ math was off, even 1500UTC works for me in non-DST, so I'm good with either on tuesday and can move my conflict that is there easily enough 16:34:26 bauzas: yeah, there's already massive interop things with flavors. For example, different virt drivers support different things or treat the same spec differently 16:34:35 so we've chosen to ignore that 16:34:49 dansmith: ack, thanks. we go with 16:00 UTC 16:34:55 cool 16:35:05 stephenfin: we discussed this when we introduced the extra spec validation framework but I wanted to speak here loud 16:35:05 artom: as for implications, the only one I'm aware of is that (I think) you'd need to use ethtool to configure the number of queues in the guest 16:35:52 I don't think that's done/doable by default, but sean-k-mooney can correct me 16:35:56 or would if they were here 16:35:57 bauzas: stephenfin right. that is what we already have in existing extra specs so it is not new from interop side too 16:36:19 stephenfin: so we allow resizing in both direction off -> on and on -> off. This is fine with me 16:36:33 yup 16:36:43 the same thing could happened already with rebuild to new image 16:36:48 also yup 16:37:09 (fwiw, I seriously doubt people will ever go on -> off, mind you - multiqueue is nearly always the thing you'd want nowadays) 16:37:35 I'm trying to document that but artom is being (correctly) annoying :P 16:37:57 \o/ 16:38:06 any objection before I approve this specless bp? 16:38:31 nope. 16:38:49 then it is approved 16:39:10 stephenfin: please add the bp link to the commit message of the implementation 16:39:20 ack, will do 16:39:30 and thanks 16:39:55 any other topic for today/ 16:39:55 ? 16:41:03 if nothing else then I go an play with the meeting schedule to move our meeting 16:41:24 I will drop a mail to the ML 16:41:29 o/ 16:41:33 o/ 16:41:35 o/ 16:42:05 #endmeeting