16:00:38 #startmeeting nova 16:00:38 Meeting started Tue Feb 21 16:00:38 2023 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:38 The meeting name has been set to 'nova' 16:00:46 o/ 16:00:55 hey folks, hola everyone 16:01:06 o/ 16:01:15 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:01:29 o/ 16:01:46 let's start, some people have to leave early 16:01:57 #topic Bugs (stuck/critical) 16:02:03 #info No Critical bug 16:02:08 #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16 new untriaged bugs (-1 since the last meeting) 16:02:12 o/ 16:02:19 auniyal helped me with triage 16:02:33 I created an etherpad 16:02:44 and I have a bug I'd like to discuss with you folks 16:02:59 #link https://etherpad.opendev.org/p/nova-bug-triage-20230214 16:03:10 the bug in question : 16:03:13 #link https://bugs.launchpad.net/nova/+bug/2006770 16:03:28 as you see, i did set it to Opinion 16:03:42 tl;dr: this is about our ip query param for instances list 16:03:57 we directly call Neutron to get the ports 16:04:07 it basically works, but the reporter had some concerns 16:05:14 people want to discuss this bug now or later ? 16:05:27 (we can discuss it in the open disc topic if we have time) 16:06:02 let's say later then :) 16:06:14 (people can lookup the bug if they want meanwhile) 16:06:17 opinion seems right to me :) 16:06:47 let's discuss this then later in the open discussion topic 16:06:53 so people will have time 16:06:55 moving on 16:07:02 #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster 16:07:20 Uggla: works for you to get the baton this week ? 16:07:28 bauzas, ok 16:07:32 ack 16:07:37 #info bug baton is being passed to Uggla 16:07:42 #topic Gate status 16:07:48 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:07:55 but the best is to track the etherpad 16:08:00 #link https://etherpad.opendev.org/p/nova-ci-failures 16:08:15 it was a dodgy week 16:08:36 so, 16:08:41 this got merged: https://review.opendev.org/c/openstack/devstack/+/873646 16:08:52 which seems to allow halving the memory used by mysqld 16:09:08 haha, gtk 16:09:08 which may help with the OOM issues we see, especially in the fat jobs like ceph-multistore 16:09:31 we could enable that in our nova-ceph-multistore job if we want to be on the leading edge and try to make sure that it's actually helping 16:09:36 (it's opt-in right now) 16:09:39 indeed, I'll double check later if we continue to have some OOM issues 16:09:48 ah my bad 16:09:58 we could remove it if it causes other problems, but.. might be good to try it 16:10:14 surely 16:10:20 dansmith: thanks for having worked on it 16:10:35 dansmith: I can write a zuul patch for novza 16:10:45 I can do it too, just wanted to socialize 16:10:57 dansmith: ack cool then, ping me for reviews 16:11:02 ack 16:11:25 ++ again 16:12:03 dansmith: I also need to look at all the Gerrit recheck comments I wrote last week 16:12:12 I maybe found some other races 16:12:18 but we'll see 16:13:11 we also have the OOM logger patch that was telling us a few things 16:13:46 https://paste.opendev.org/show/bfvZX0XeKsELzY54EGb8/ 16:13:54 but let's discuss this off-meeting 16:14:19 * gibi had not time to look at the extra logs from the functional race 16:15:18 gibi: basically, each of the 6 failures having logs was having a different functest 16:15:37 cool, that can serve as a basis for a local repor 16:15:50 anyway, moving on 16:15:52 bauzas: they are all in teh libvirt test suite 16:16:01 so likely all have the same common issue 16:16:11 but ya lets move on 16:16:14 maybe, I didn't had time yet to look at the code 16:16:23 #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status 16:16:28 all of them are green ^ 16:16:35 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:16:40 #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures 16:16:44 that's it 16:16:50 #topic Release Planning 16:16:57 #link https://releases.openstack.org/antelope/schedule.html 16:17:05 so we're now on Feature Freeze 16:17:10 #link https://etherpad.opendev.org/p/nova-antelope-blueprint-status Blueprint status for 2023.1 16:17:16 you can see what we merged 16:17:36 I also created two changes for my own series that were asked 16:17:46 but I'll ping folks tomorrow about them 16:17:56 #info Antelope-rc1 is in 1.5 weeks 16:18:18 now, we need to prepare for our RC1 where we branch master 16:18:31 #link https://etherpad.opendev.org/p/nova-antelope-rc-potential 16:18:40 as you see ^ I created an etherpad 16:18:54 thanks btw. again takashi for creating some changes that are needed 16:19:26 as a reminder, if people find some bugs, they can use a specific tag : 16:19:32 https://bugs.launchpad.net/nova/+bugs?field.tag=antelope-rc-potential 16:19:54 before RC1, any bug report can be using this tag, but we prefer to make sure they are regressions 16:20:04 after RC1, only regressions should use this tag 16:20:29 I created a cycle highlights change too : 16:20:43 #link https://review.opendev.org/c/openstack/releases/+/874483 Cycle highlights for Nova Antelope 16:20:48 please review it 16:21:25 at least gibi, dansmith, artom and other folks that were having merged changes 16:21:40 ack 16:21:46 I'll +1 on Thursday 16:22:02 we need to merge this before this Thursday for the Foundation market folks 16:22:38 we also have https://review.opendev.org/c/openstack/releases/+/874450 to +1 16:22:47 I guess we're done with our clients 16:23:20 so I'll branch os-vif, osc-placement and novaclient unless people have concerns 16:23:46 as you see in the commit msg, it will be merged eventually on Friday 16:24:09 * bauzas will just verify the SHA1 16:24:10 or earlier if a release liaison +1s it 16:24:27 elodilles: yup, but I'm asking people if they have concerns 16:24:33 speaking of which im not sure if i ill have time to continue to do that 16:24:44 looks not, so I'll just verify the SHA1s before +1ing 16:24:54 i may leave my slef for this cycle if no on else want to take on that role 16:25:08 sean-k-mooney1: yup, I know and I was planning to ask you 16:25:13 but i am not sure of my aviablity to keep an eye on it this cycle 16:25:35 ok, so maybe it's not time yet to ask if someone else wants to be a release liaison 16:25:48 but I'll officially ask it next week 16:25:51 ok 16:26:00 we can have more than one release liaison btw. 16:26:16 no need to remove you before someone arrives or something like that 16:26:43 ack the primary role is to reducec the bus factor and ensure that release are done correctly and in a timply fashion so it does not all fall on the PTL 16:26:43 and we can even have *two* liaisons if we really find *two* people wanting to be :) 16:26:46 no need to battle :po 16:27:07 I'll explain next week what a release liaison is and what they do 16:27:21 but if people want, they can DM me 16:27:34 before next meeting 16:28:04 #info If someone wants to run as a Nova release liaison next cycle, please ping bauzas 16:28:34 I think that's it for the RC1 agenda 16:28:36 oh 16:28:43 one last thing 16:29:01 thanks to takashi, https://review.opendev.org/c/openstack/nova-specs/+/872068 is merged 16:29:10 you can now add your specs for Bocat 16:29:13 Bobcat even 16:30:05 like, people who had accepted specs for Antelope can just repropose them for Bobcat and I'll quickly +2/+W directly if nothing changes between both spec files 16:30:23 * bauzas tries to not eye at folks 16:31:00 I'll do the Launchpad Bobcat magic later next week (I guess) 16:31:07 that's it this time 16:31:22 #topic vPTG Planning 16:31:30 as a weekly reminder : 16:31:32 #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 Register your free ticket 16:31:46 * gibi needs to drop, will read back tomorrow 16:31:56 maybe you haven't seen but we are officially a PTG team 16:32:13 I don't know yet how long we could run the vPTG sessions 16:32:32 but like every cycle, I'll ask your opinions about the timing 16:32:41 not today, but once I'm asked 16:32:58 good time for saying 16:33:03 #link https://etherpad.opendev.org/p/nova-bobcat-ptg Draft PTG etherpad 16:33:12 I feel alone with this etherpad ^ 16:33:24 and I'm sure people have topics they want to discuss 16:34:25 anyway, moving on 16:34:33 (just hoping people read our meeting notes) 16:34:41 #topic Review priorities 16:34:50 #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) 16:34:54 #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review 16:35:08 #topic Stable Branches 16:35:14 elodilles: your turn 16:35:28 #info stable gates seem to be OK (victoria gate workaround has landed and it is now unblocked) 16:35:36 well, unblocked 16:35:52 though it's not everywhere easy to merge in patches 16:36:03 #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci 16:36:26 indeed 16:36:35 that's the short summary 16:36:42 I still have the ussuri CVE VMDK fix to be merged 16:36:50 I rechecked it a few times 16:37:00 elodilles: thanks for the notes 16:37:04 np 16:37:13 #topic Open discussion 16:37:19 so, nothing on the agenda 16:37:47 we can discuss https://bugs.launchpad.net/nova/+bug/2006770 if people want or close the meeting 16:37:56 the fact is, I wrote Opinion 16:38:04 unless people have concerns with what I wrote, I'm done. 16:39:07 looks not 16:39:11 then I assume we're done. 16:40:16 ++ 16:40:18 thanks all 16:40:23 #endmeeting