| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-02-21 | |||
| 16:25:08 | bauzas | sean-k-mooney1: yup, I know and I was planning to ask you | |
| 16:25:13 | sean-k-mooney1 | but i am not sure of my aviablity to keep an eye on it this cycle | |
| 16:25:35 | bauzas | ok, so maybe it's not time yet to ask if someone else wants to be a release liaison | |
| 16:25:48 | bauzas | but I'll officially ask it next week | |
| 16:25:51 | sean-k-mooney | ok | |
| 16:26:00 | bauzas | we can have more than one release liaison btw. | |
| 16:26:16 | bauzas | no need to remove you before someone arrives or something like that | |
| 16:26:43 | sean-k-mooney | 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 | bauzas | and we can even have *two* liaisons if we really find *two* people wanting to be :) | |
| 16:26:46 | bauzas | no need to battle :po | |
| 16:27:07 | bauzas | I'll explain next week what a release liaison is and what they do | |
| 16:27:21 | bauzas | but if people want, they can DM me | |
| 16:27:34 | bauzas | before next meeting | |
| 16:28:04 | bauzas | #info If someone wants to run as a Nova release liaison next cycle, please ping bauzas | |
| 16:28:34 | bauzas | I think that's it for the RC1 agenda | |
| 16:28:36 | bauzas | oh | |
| 16:28:43 | bauzas | one last thing | |
| 16:29:01 | bauzas | thanks to takashi, https://review.opendev.org/c/openstack/nova-specs/+/872068 is merged | |
| 16:29:10 | bauzas | you can now add your specs for Bocat | |
| 16:29:13 | bauzas | Bobcat even | |
| 16:30:05 | bauzas | 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:31:00 | bauzas | I'll do the Launchpad Bobcat magic later next week (I guess) | |
| 16:31:07 | bauzas | that's it this time | |
| 16:31:22 | bauzas | #topic vPTG Planning | |
| 16:31:30 | bauzas | as a weekly reminder : | |
| 16:31:32 | bauzas | #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 Register your free ticket | |
| 16:31:56 | bauzas | maybe you haven't seen but we are officially a PTG team | |
| 16:32:13 | bauzas | I don't know yet how long we could run the vPTG sessions | |
| 16:32:32 | bauzas | but like every cycle, I'll ask your opinions about the timing | |
| 16:32:41 | bauzas | not today, but once I'm asked | |
| 16:32:58 | bauzas | good time for saying | |
| 16:33:03 | bauzas | #link https://etherpad.opendev.org/p/nova-bobcat-ptg Draft PTG etherpad | |
| 16:33:12 | bauzas | I feel alone with this etherpad ^ | |
| 16:33:24 | bauzas | and I'm sure people have topics they want to discuss | |
| 16:34:25 | bauzas | anyway, moving on | |
| 16:34:33 | bauzas | (just hoping people read our meeting notes) | |
| 16:34:41 | bauzas | #topic Review priorities | |
| 16:34:50 | bauzas | #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 | bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | |
| 16:35:08 | bauzas | #topic Stable Branches | |
| 16:35:14 | bauzas | elodilles: your turn | |
| 16:35:28 | elodilles | #info stable gates seem to be OK (victoria gate workaround has landed and it is now unblocked) | |
| 16:35:36 | elodilles | well, unblocked | |
| 16:35:52 | elodilles | though it's not everywhere easy to merge in patches | |
| 16:36:03 | elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | |
| 16:36:26 | bauzas | indeed | |
| 16:36:35 | elodilles | that's the short summary | |
| 16:36:42 | bauzas | I still have the ussuri CVE VMDK fix to be merged | |
| 16:36:50 | bauzas | I rechecked it a few times | |
| 16:37:00 | bauzas | elodilles: thanks for the notes | |
| 16:37:04 | elodilles | np | |
| 16:37:13 | bauzas | #topic Open discussion | |
| 16:37:19 | bauzas | so, nothing on the agenda | |
| 16:37:47 | bauzas | we can discuss https://bugs.launchpad.net/nova/+bug/2006770 if people want or close the meeting | |
| 16:37:56 | bauzas | the fact is, I wrote Opinion | |
| 16:38:04 | bauzas | unless people have concerns with what I wrote, I'm done. | |
| 16:39:07 | bauzas | looks not | |
| 16:39:11 | bauzas | then I assume we're done. | |
| 16:40:16 | dansmith | ++ | |
| 16:40:18 | bauzas | thanks all | |
| 16:40:23 | bauzas | #endmeeting | |
| 16:40:23 | opendevmeet | Meeting ended Tue Feb 21 16:40:23 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:40:23 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-21-16.00.html | |
| 16:40:23 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-21-16.00.txt | |
| 16:40:23 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-21-16.00.log.html | |
| 16:40:33 | elodilles | thanks o/ | |
| 16:40:57 | dansmith | bauzas: so, gmann and I were running that memory usage patch in periodic on tempest jobs for a few days to make sure it didn't substantially worsen things | |
| 16:41:07 | dansmith | and my survey at the moment indicates that it looks good | |
| 16:41:41 | dansmith | so I'll propose to make it enabled for ceph-multistore (which will also impact glance) and we'll see if gmann is cool with that when he's around | |
| 16:41:44 | bauzas | nice to hear | |
| 16:41:52 | bauzas | ack, do it and I'll vote | |
| 16:45:08 | opendevreview | Dan Smith proposed openstack/nova master: Use mysql memory reduction flags for ceph job https://review.opendev.org/c/openstack/nova/+/874664 | |
| 16:45:11 | dansmith | bauzas: ^ | |
| 17:43:02 | bauzas | dansmith: I doubt that cells_v2 map_instances could work with https://bugs.launchpad.net/nova/+bug/2007922 (even I asked for it) | |
| 17:43:19 | bauzas | dansmith: tl;dr: the instance mapping exists but the cell value is None | |
| 17:43:30 | bauzas | and we know the instance is in cell0 DB | |
| 17:43:53 | dansmith | yeah, as I said, I initially missed that the person said they had reference in the mappings table | |
| 17:43:56 | bauzas | dansmith: I guess the simpliest thing is to hack the DB to add the cell0 uuid in the instancemapping record, nope ? | |
| 17:44:08 | dansmith | probably | |
| 17:44:14 | bauzas | or do we have a better nova-manage command ? | |
| 17:44:18 | bauzas | looking at the docs, nope | |
| 17:44:29 | dansmith | not that I know of | |
| 17:44:33 | bauzas | this instance is somehow sit in the middle | |
| 17:44:46 | bauzas | not fully migrated but in between | |
| 17:44:58 | dansmith | not fully ... mapped? | |
| 17:45:06 | bauzas | sorry, yeah mapped | |
| 17:45:23 | bauzas | I'll propose the ALTER to the reporter | |
| 17:47:42 | dansmith | don't we have a mapped flag on the instance (or something else)? | |
| 17:48:36 | bauzas | in the instances table you mean ? | |
| 17:48:57 | dansmith | I thought it was.. that's how we survey instances that need to be mapped right? | |
| 17:49:13 | dansmith | just wondering if that flag matches or not | |
| 17:52:44 | bauzas | so | |
| 17:52:55 | bauzas | https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L874 | |
| 17:53:12 | bauzas | we just iterate over a limit and a marker on the instances table from a cell that's given | |
| 17:54:34 | dansmith | ah right | |
| 17:54:44 | bauzas | and I think I understand how the cell ID was set to None | |
| 17:54:51 | bauzas | https://github.com/openstack/nova/blob/439c67254859485011e7fd2859051464e570d78b/nova/objects/instance_mapping.py#L73 | |
| 17:55:31 | dansmith | it only does that if it's not none though | |
| 17:55:34 | bauzas | anyway, map_instances *could* work with cell0 | |
| 17:56:18 | bauzas | if the reporter runs map_instances with cell0 attribute, it will loop over the contents of cell0's instances table and will create an instancemapping object | |