| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-02-21 | |||
| 16:09:36 | dansmith | (it's opt-in right now) | |
| 16:09:39 | bauzas | indeed, I'll double check later if we continue to have some OOM issues | |
| 16:09:48 | bauzas | ah my bad | |
| 16:09:58 | dansmith | we could remove it if it causes other problems, but.. might be good to try it | |
| 16:10:14 | bauzas | surely | |
| 16:10:20 | bauzas | dansmith: thanks for having worked on it | |
| 16:10:35 | bauzas | dansmith: I can write a zuul patch for novza | |
| 16:10:45 | dansmith | I can do it too, just wanted to socialize | |
| 16:10:57 | bauzas | dansmith: ack cool then, ping me for reviews | |
| 16:11:02 | dansmith | ack | |
| 16:11:25 | bauzas | ++ again | |
| 16:12:03 | bauzas | dansmith: I also need to look at all the Gerrit recheck comments I wrote last week | |
| 16:12:12 | bauzas | I maybe found some other races | |
| 16:12:18 | bauzas | but we'll see | |
| 16:13:11 | bauzas | we also have the OOM logger patch that was telling us a few things | |
| 16:13:46 | bauzas | https://paste.opendev.org/show/bfvZX0XeKsELzY54EGb8/ | |
| 16:13:54 | bauzas | but let's discuss this off-meeting | |
| 16:15:18 | bauzas | gibi: basically, each of the 6 failures having logs was having a different functest | |
| 16:15:37 | gibi | cool, that can serve as a basis for a local repor | |
| 16:15:50 | bauzas | anyway, moving on | |
| 16:15:52 | sean-k-mooney1 | bauzas: they are all in teh libvirt test suite | |
| 16:16:01 | sean-k-mooney1 | so likely all have the same common issue | |
| 16:16:11 | sean-k-mooney1 | but ya lets move on | |
| 16:16:14 | bauzas | maybe, I didn't had time yet to look at the code | |
| 16:16:23 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status | |
| 16:16:28 | bauzas | all of them are green ^ | |
| 16:16:35 | bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:16:40 | bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | |
| 16:16:44 | bauzas | that's it | |
| 16:16:50 | bauzas | #topic Release Planning | |
| 16:16:57 | bauzas | #link https://releases.openstack.org/antelope/schedule.html | |
| 16:17:05 | bauzas | so we're now on Feature Freeze | |
| 16:17:10 | bauzas | #link https://etherpad.opendev.org/p/nova-antelope-blueprint-status Blueprint status for 2023.1 | |
| 16:17:16 | bauzas | you can see what we merged | |
| 16:17:36 | bauzas | I also created two changes for my own series that were asked | |
| 16:17:46 | bauzas | but I'll ping folks tomorrow about them | |
| 16:17:56 | bauzas | #info Antelope-rc1 is in 1.5 weeks | |
| 16:18:18 | bauzas | now, we need to prepare for our RC1 where we branch master | |
| 16:18:31 | bauzas | #link https://etherpad.opendev.org/p/nova-antelope-rc-potential | |
| 16:18:40 | bauzas | as you see ^ I created an etherpad | |
| 16:18:54 | bauzas | thanks btw. again takashi for creating some changes that are needed | |
| 16:19:26 | bauzas | as a reminder, if people find some bugs, they can use a specific tag : | |
| 16:19:32 | bauzas | https://bugs.launchpad.net/nova/+bugs?field.tag=antelope-rc-potential | |
| 16:19:54 | bauzas | before RC1, any bug report can be using this tag, but we prefer to make sure they are regressions | |
| 16:20:04 | bauzas | after RC1, only regressions should use this tag | |
| 16:20:29 | bauzas | I created a cycle highlights change too : | |
| 16:20:43 | bauzas | #link https://review.opendev.org/c/openstack/releases/+/874483 Cycle highlights for Nova Antelope | |
| 16:20:48 | bauzas | please review it | |
| 16:21:25 | bauzas | at least gibi, dansmith, artom and other folks that were having merged changes | |
| 16:21:40 | gibi | ack | |
| 16:21:46 | bauzas | I'll +1 on Thursday | |
| 16:22:02 | bauzas | we need to merge this before this Thursday for the Foundation market folks | |
| 16:22:38 | bauzas | we also have https://review.opendev.org/c/openstack/releases/+/874450 to +1 | |
| 16:22:47 | bauzas | I guess we're done with our clients | |
| 16:23:20 | bauzas | so I'll branch os-vif, osc-placement and novaclient unless people have concerns | |
| 16:23:46 | bauzas | as you see in the commit msg, it will be merged eventually on Friday | |
| 16:24:10 | elodilles | or earlier if a release liaison +1s it | |
| 16:24:27 | bauzas | elodilles: yup, but I'm asking people if they have concerns | |
| 16:24:33 | sean-k-mooney1 | speaking of which im not sure if i ill have time to continue to do that | |
| 16:24:44 | bauzas | looks not, so I'll just verify the SHA1s before +1ing | |
| 16:24:54 | sean-k-mooney1 | i may leave my slef for this cycle if no on else want to take on that role | |
| 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 | |