16:00:02 #startmeeting nova 16:00:02 Meeting started Tue Oct 26 16:00:02 2021 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:02 The meeting name has been set to 'nova' 16:00:15 o/ 16:00:19 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:00:35 hola everyone, nice to see your virtual faces ;) 16:00:54 * bauzas wonders how many of us are jetlagged 16:01:26 o/ 16:02:08 wow, not everyone at the same time :) 16:03:15 maybe the rest of us had enough last week D: 16:03:30 :) 16:03:36 ok, then let's start :) 16:04:01 hopefully, it would be a small meeting :) 16:04:08 #topic Bugs (stuck/critical) 16:04:12 One Critical bug 16:04:20 https://bugs.launchpad.net/nova/+bug/1947687 16:04:33 * bauzas doesn't really know why he triaged it as Critical 16:04:41 it is a gate bug 16:04:50 but it does not hit us in every run 16:04:51 maybe because it was a gate bug, yes 16:04:58 I agree to decrease this to High 16:05:03 yeah 16:05:07 I have not seen it recently 16:05:16 ok done 16:05:31 gibi: maybe we could see whether logstash still works for this one 16:05:49 bauzas: yeas a signture would be nice 16:06:07 gibi: can you test this and provide the logstash link ? 16:06:10 sure 16:06:15 * gibi took a note 16:06:16 thanks++ 16:06:35 okay, moved to High 16:06:42 anything to discuss about it now ? 16:06:52 - 16:06:56 k 16:07:01 #link 24 new untriaged bugs (+6 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:07:10 I triaged 6 or 7 16:07:25 (already, I mean) 16:07:35 I'll continue to triage a few of them tomorrow 16:08:00 but in case some contributors want to triage too, I'd be happy 16:08:11 for the moment, that's fine 16:08:17 yeah I feel the pressure but still have other pressors 16:08:29 yeah, no urgency 16:08:46 gibi: I wasn't thinking about you 16:08:57 I know 16:09:04 still I feel responsible :) 16:09:13 but in case some contributors want to be better knowing about Nova, they can do this 16:09:22 anyway 16:09:27 moving now 16:09:34 32 open stories in Storyboard for Placement # link https://storyboard.openstack.org/#!/project/openstack/placement 16:09:38 ^ this is new 16:09:41 ohh a new one 16:09:42 :) 16:09:51 as we agreed on the PTG to verify them 16:10:07 next week, I'll tell how many new stories we have 16:10:31 that said, with SB, I don't know whether it's a feature request or a bug 16:10:47 we can start tagging them 16:10:52 to differentiate 16:10:58 yeah... or moving to LP :p 16:11:14 tagging is easier :D 16:11:23 I said I'll look at some script 16:11:32 let's not discuss this one now 16:11:39 as we don't have a lot of folks 16:11:54 but, yeah, maybe next week, we'll see what folks prefer 16:12:00 sire 16:12:01 sure 16:12:08 #topic Gate status 16:12:13 Nova gate bugs #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure 16:12:20 we already discussed one 16:12:28 nothing new, AFAIK 16:12:39 we fixed one during the PTG IIRC 16:13:05 Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly 16:13:19 this goes well this time ^ 16:13:29 I have two gate fixers 16:13:35 the placement-nova-tox-functional-py38 job now works 16:13:52 gibi: loved 16:13:55 1) https://review.opendev.org/c/openstack/nova/+/814036 16:14:07 this is ready to land 16:14:11 2) https://review.opendev.org/c/openstack/nova/+/814735 16:14:31 this I will respin to add better commit message based on melwitt's findings and probably a poison to avoid breaking this again 16:14:39 oh thanks for both 16:14:46 I'll review them tomorrow morning 16:14:47 melwitt: btw, thanks you helped a lot understanding what is happening 16:14:51 * kashyap waves hi, while distracted and hungry 16:15:00 * gibi waves back 16:15:01 Err, wrong channel 16:15:05 But the hi still stands :) 16:15:14 * gibi rolls back the waves 16:15:37 Haha, no 16:16:01 :) 16:16:07 kashyap: you're still in the nova channel :p 16:16:17 welcome on the nova meeting :p 16:16:20 and of course you are welcome here :) 16:16:31 moving fast 16:16:31 bauzas: Yeah, I had the scrollback a bit up at the bug triage part 16:16:41 #topic PTG summary 16:16:54 I wrote a summary and gibi nitpicked it :p 16:16:55 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025534.html 16:17:10 bauzas: thanks for the summary and sorry for nitpicking :D 16:17:20 at least I know that people read my summary :p 16:17:21 at least you know that somebody read it :D 16:17:25 that, yeah 16:17:27 :D 16:17:50 I could have made jokes in the summary to keep people continuing to read it 16:18:07 nothing here to tell about the PTG besides the summary ? 16:18:34 I have a small "info" for the open topics 16:18:51 bauzas: nothing from me for the PTG 16:18:52 my only concern about the agreements we made is that we don't have a lot of owners for ACTION items 16:19:09 yeah, I think you should try to ask for owners 16:19:15 maybe a reply to the mail 16:19:27 next PTG, we should try to ensure that when we set an agreement, we have an ACTION item and an owner 16:19:30 I will talk to brinzhang about the OWNER things but he seems to be off 16:20:00 I hope he can take the nova side of that too, but if not then I will write the spec 16:20:01 gibi: good call, I could ask by email but I wouldn't be surprised if nobody steps up :) 16:20:20 I mean the OWNER trait thingy :D 16:20:38 I won't be the owner of everything :D 16:20:45 gibi: or the OWNED_BY you rather mean ? 16:20:54 heh, see how an adjective is better :p 16:20:55 :D 16:21:08 no confusion at all 16:21:14 anyway, was kidding 16:21:18 sure :D 16:21:21 don't wanna talk about the sky color 16:21:28 #topic Release Planning 16:21:35 just a reminder 16:21:35 Yoga-1 is due Nova 18th #link https://releases.openstack.org/yoga/schedule.html#y-1 16:21:56 just 3 weeks 16:22:02 sh*t 16:22:05 kashyap: I haven't forgotten you, will ping you when we're at open discussion topic 16:22:11 gibi: YUUUUP 16:22:30 * gibi tries to remember where he put the cloning machine 16:22:31 time flys 16:22:55 and /me needs to propose Nov 16th for spec review day at the next meeting 16:23:18 gibi: I tried using the cloning machine, buy my clones don't wanna work on IT 16:23:33 this is sad 16:23:37 let's move one 16:23:41 on* even 16:23:45 #topic Review priorities 16:23:52 #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement)+label:Review-Priority%252B1 16:24:00 I know we agreed on changing a few things 16:24:05 I've reviewed some and marked some 16:24:12 I'll work on a doc change this week if I have time 16:24:31 gibi: I need to jump on my owns sooner than later 16:24:51 bauzas: this has momentum now https://review.opendev.org/c/openstack/nova/+/815373 so I suggest to start with that 16:25:04 sean-k-mooney: once I'm done with proposing the doc change, feel free to write a dependent patch for the ACL thingies 16:25:22 sorry wrong link 16:25:26 hah 16:25:34 was wondering why you were proposing this one 16:25:37 the other mdev https://review.opendev.org/c/openstack/nova/+/810220 16:25:47 I think there are issues to discuss there ^^ 16:26:00 I will check the mdev + resume soon too 16:26:06 ki 16:26:07 bk 16:26:21 gibi: yeah, I was thinking about it when reviewing 16:26:21 bauzas: sure we did it the otherway around the last time i kind of feel like gating the docs change on the porject config one is more correct but it really dose not matter 16:26:36 gibi: we need to test it with devstack 16:26:49 I'm not sure all the services are up and the RT running 16:26:55 when we call the methods 16:27:11 but this needs me looking at the code first before I reply 16:27:19 bauzas: the only way to test the mdev stuff in devstack is if we can use the fake mdev kernel modules 16:27:29 bauzas: no before driver.init_host we should not call other driver methods and defintely there is no RT populated as we dont know about our nodes from the hypervisor 16:27:29 unless you mean just manually and not in ci 16:27:30 sean-k-mooney: or use my own env... :) 16:27:52 well, provided I'm able to create a devstack env 16:28:00 which I failed with rhel 8.2 16:28:05 but meh 16:28:21 #topic Stable Branches 16:28:23 bauzas: now that we have generic mdev support it might want to see if we can support the dummy kernel moduels at some point 16:28:30 elodilles: floor is yours 16:28:38 from xena till train the gates are not blocked 16:28:40 bauzas: On a phone call :-( Will come back here; it's not super urgent 16:28:42 sean-k-mooney: agreed 16:28:48 bauzas: In short, it's this one: http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025500.html 16:28:49 stein and older stable branches are blocked, needs the setuptools pinning patch to unblock: https://review.opendev.org/q/I26b2a14e0b91c0ab77299c3e4fbed5f7916fe8cf 16:28:56 And it's resolved now. 16:29:12 Ussuri Extended Maintenance transition is in two weeks (Nov 12) 16:29:22 (The resolution: http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025527.html) 16:29:29 we might not need another release on ussuri before the transition, as there are not that many patch merged since the last release from early October 16:29:52 (the list of open and unreleased patches anyway: https://etherpad.opendev.org/p/nova-stable-ussuri-em ) 16:30:02 that's it ^^^ 16:30:05 elodilles: when you say not many, you mean zero bugfix? 16:30:07 elodilles: if you feel we need to do some reviewing efforts before EM, let me know 16:30:26 gibi: i mean 1 or 2 bugfix :) 16:30:29 elodilles: ack i might try to rebase and submit the libvirt os-vif deleagtion patchs 16:30:51 before ussuri em if there is another release 16:30:56 elodilles: hm if there are real fixes there then I might make sense to release them before we EM 16:31:11 s/I/it/ 16:31:19 agreed with gibi 16:31:25 yes, it makes sense to release, 16:31:55 though we shouldn't hurry with merging things if we are not sure that it won't cause any regression 16:32:05 as this will be the *final* release 16:32:39 elodilles: I'm a bit busy tomorrow as I promised many things but I'd appreciate if you could chase me and a couple of other cores about reviews either Thursday or next week 16:33:11 bauzas: sure, 16:33:28 there are some bug fixes that needs a 2nd +2 16:34:01 but if anyone see any other bugfix that would be good to merge, then let us know 16:34:14 cool 16:34:52 #topic Sub/related team Highlights 16:35:01 lyarwood is still on PTO 16:35:23 so I'll skip this part and I don't think we need to discuss about libvirt by now 16:35:30 #topic Open discussion 16:35:36 #agreed Reminder : The Asian-friendly meeting is now cancelled due to lack of presence. 16:35:56 so we won't run a meeting on Nov 4th 16:36:05 I'll send an email accordingly 16:36:57 just a personal note, I'll be on company PTO on Friday 29th and Nov 1st is bank holiday in France 16:37:15 so don't expect me between Thursday EOB and Tuesday 16:37:54 we have one item that was written in the wiki 16:38:01 add Support volumes backed by VStorageObject -> https://blueprints.launchpad.net/nova/+spec/vmware-fcd and https://review.opendev.org/c/openstack/nova/+/808791 16:38:37 yes so as far as i can tell i think they implemented the feature in cinder and likely the out of tree driver 16:38:39 not sure the proposer is around 16:38:49 now they are looking to add support in the intree one 16:38:53 I don't know his IRC nick 16:39:04 so I can't ping him 16:39:49 looking at the patch the change is confined in the vmware driver 16:39:57 ya so i reviewed this and to me this si a feature not a bug so i assed them to raise this in this meeting 16:40:10 so I think it is OK as a specless bp 16:40:13 im infavor of just proceeding with this as a speckless bp 16:40:52 OK, we don't have a lof of people around 16:40:58 its not a bug so it should not be backported but as i mentioned above i stonly suspect this was implemente din the out of tree driver and they are just closing the gap 16:40:59 but we can make it a specless BP 16:41:06 do people agree ? 16:41:48 yep 16:41:54 #agreed https://blueprints.launchpad.net/nova/+spec/vmware-fcd approved as a specless blueprint 16:41:54 yep 16:42:01 the cinder feature was completed 4 years ago by the way https://review.opendev.org/c/openstack/cinder/+/521213/ 16:42:32 (/me can't remember how to formally approve BPs in Launchpad but that's something I'll sort out after this meeting) 16:42:53 that one already is 16:42:58 I just did 16:43:04 ah 16:43:08 direction and definitions are now approved 16:43:24 but nevermind, will figure it out or will hassle gibi 16:43:25 you likely shoudl set the serise goal to yoga too 16:43:41 bauzas: set approver, series goal, and maybe milestone target 16:43:55 bauzas: you can also set implementation status as we have a patch already 16:44:09 right it should be in need_review 16:44:57 ok, done 16:45:00 anyway 16:45:23 kashyap: are you done chatting ? you said you had a thing to discuss 16:45:49 bauzas: Yes, here 16:45:51 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025500.html 16:45:54 bauzas: Sorry for "talking over" earlier 16:46:08 is this^ more a FYI ? 16:46:12 Yep 16:46:26 bauzas: In short: DevStack now defults to "Nehalem" CPU model for reasons outlined there. 16:46:43 kashyap: devstack/rhel you mean ? 16:46:47 No 16:46:50 DevStack upstream 16:47:06 I worked w/ Clark to get the patch merged in DevStack 16:47:20 I mean, devstack all distros or only upstream devstack with rhel ? 16:47:40 For all. 16:47:44 ack 16:47:54 for all on x86 16:47:57 Everything is summarized and resolved in that thread. 16:48:23 Yes, x86 is "implied architecture", when we don't name an arch :) 16:48:47 okay, do we need further actions, like documenting it ? 16:48:55 in our relnotes or in the install docs ? 16:49:07 no we dont need to document anythign in nova 16:49:15 Yep; nothing needs documentation in Nova 16:49:27 my confusion comes from the fact we changed default for all distros, not only rhel 16:49:27 rhel have documented there new compilation target already in a blog 16:49:37 bauzas: No further action; just an FYI here ... if anyone in case notices "why is DevStack giving me Nehalem by default" 16:49:48 Yep; linked to in the post to the upstream list 16:50:05 kashyap: little chances that people notice this change by looking at our meeting minutes, honestly 16:50:24 but okay, noted. 16:50:31 bauzas: I've notified the Whitebox / CI folks to change their scripts too 16:50:45 So, the right parties are notified. I'm not expecting anyone to read these minutes here :) 16:50:54 bauzas: well honestly its a better default then qemu64 and its so old at this poitn everythign supprots it 16:51:02 bauzas: which is basicaly why it was done for all 16:51:30 bauzas: The change is a better default too. Yes. (Besides solving the switch to a new x86 baseline) 16:51:33 the jobs also might get slictly faster as a restult but that would just be a nice benift and not the intent 16:51:48 Yep; there will be slight improvement 16:52:15 OK, nice to hear 16:52:22 are we done ? 16:52:26 bauzas: That's all. I don't want to take up more time. But those interested / affected in CI/QE/Infra are notified, and I'm working w/ them. 16:52:31 Yep. 16:52:40 kashyap: excellent, thanks for providing guidance 16:52:54 kashyap++ 16:53:08 I think we can reasonably call this meeting a wrap 16:53:23 * gibi agrees 16:53:24 I was expecting it to be shorter, but meh, good talks 16:53:33 #endmeeting