September 2025 - openstack-discuss

[freezer] Activity on this project?
by Jimmy McArthur 09 Sep '25

09 Sep '25

Are there orgs or individuals that are working on Freezer and/or have interest in working on Freezer? Cheers, Jimmy

4 3

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-3)
by Goutham Pacha Ravi 08 Sep '25

08 Sep '25

Hello Stackers, We're three weeks away from the coordinated 2025.2 "Flamingo" release [1]. This week, project teams are testing code changes and merging bug fixes to deliver release candidates for deliverables that follow a "cycle-with-rc" release model [2]. Polls for electing a PTL for the OpenStack Dashboard ("Horizon") project team, as well as for four members to the OpenStack Technical Committee, are still open. They will close on September 17th, 2025, at 23:45 UTC [3]. In the past week, election officials reached out to a section of the electorate that hadn't opted in to emails on the election system: CIVS. Please do contact the election officials [3] if you are having trouble finding your ballot. Besides this, governance updates included marking the conclusion of the goal to migrate WSGI scripts across all OpenStack services [4] and adding new metadata to project tracking to highlight inactive OpenStack projects. This will help us make release and documentation updates to clearly flag deliverables that need help from new (or existing) contributors, as well as serve as a health indicator to operators and users. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee occurred on September 2nd, 2025, simultaneously over Meetpad [5] and IRC [6]. The "Migrate from WSGI scripts to module paths" goal was completed [4]. A significant portion of the meeting was spent discussing the proposed retirement of the Monasca project team. The TC considered whether to recommend forking the project into a new namespace on opendev.org under the aegis of the volunteer who wants to maintain it. We also discussed the need to update documentation and README files to reflect the project's maintenance status and to implement automated updates for this process. We discussed the ongoing elections, where an early retrospective item was to urge existing members to renew their OpenInfra Foundation memberships and to opt in to CIVS emails. The team reviewed "leaderless teams" and the status of projects like Vitrage, Venus and OpenStack Charms, noting that a PTL candidate is still needed. We took an action item to tag retired packages on PyPi as part of the repository retirement process. Finally, the group briefly touched on gate health issues related to Debian Trixie nodes and a new discussion point about default MySQL/MariaDB charset/collations that will be addressed in the next meeting. The next meeting of the OpenStack TC is on September 9th, 2025, at 1700 UTC. This meeting will be hosted in the #openstack-tc channel on OFTC. Please find the meeting's agenda on its wiki page [7]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== - Show inactive project status in project.yaml | https://review.opendev.org/c/openstack/governance/+/958229 - Mark "Migrate from WSGI scripts" goal as completed | https://review.opendev.org/c/openstack/governance/+/958817 ==== Open For Review ==== - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 === Upcoming Events === - 2025-09-09: OIF Board Monthly meeting: https://board.openinfra.org/ - 2025-09-17: OpenStack TC and Horizon project elections conclude: https://governance.openstack.org/election/ - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ === How to Contact the TC === You can reach the TC in several ways: - Email: send an email with the tag [tc] on this mailing list. - Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. - Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1700 UTC [7]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] OpenStack Elections: https://governance.openstack.org/election/ [4] Community Goal to update WSGI configuration: https://governance.openstack.org/tc/goals/proposed/migrate-from-wsgi-script… [5] TC Meeting Video Recording, Sep 2nd, 2025: https://youtu.be/K_tdk4mkxT0 [6] TC Meeting IRC Log, Sep 2nd, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-02-17.01.html [7] TC Meeting Agenda, Sep 9th, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[watcher] Core team updates - removals, reminders, and new addition
by Sean Mooney 08 Sep '25

08 Sep '25

Hi everyone, I'm writing to propose some updates to the Watcher core team membership to ensure we maintain an active and engaged core review team. ## Proposed Removals (Immediate) The following core reviewers have been inactive for an extended period and I propose to remove them from all Watcher core groups: * Alexander Chadin (joker946(a)gmail.com) - last contribution: 26 Feb 2019 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=joker… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=joker…> * Vincent Françoise (Vincent.FRANCOISE(a)b-com.com) - last contribution: 15 Mar 2019 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=vince… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=vince…> * YumengBao (yumeng_bao(a)yahoo.com) - last contribution: 09 Apr 2020 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=yumen… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=yumen…> * aditi sharma (adi.sky17(a)gmail.com) - last contribution: 22 Nov 2018 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=adi-s… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=adi-s…> * licanwei (li.canwei2(a)zte.com.cn) - last contribution: 21 Jan 2021 https://www.stackalytics.io/?release=all&user_id=li-canwei2&module=watcher-… <https://www.stackalytics.io/?release=all&user_id=li-canwei2&module=watcher-…> * suzhengwei (sugar-2008(a)163.com) - last contribution: 13 Sep 2022 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=sue.s… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=sue.s…> We want to thank all these contributors for their valuable work and contributions to the Watcher project over the years for there time and effort. ## Core Activity Notice (Removal planned for 2026.2) The following core reviewers are currently showing low activity levels. We're providing advance notice that they will be removed from the core group at the start of the 2026.2 cycle unless they become active again during the 2026.1 cycle: * chenker (chen.ke14(a)zte.com.cn) * Dan Smith (dms(a)danplanet.com) * Marios Andreou (marios.andreou(a)gmail.com) * Slawek Kaplonski (skaplons(a)redhat.com) We recognize that over time priorities change, if you wish to maintain their core status and can re-engage or wish to be be removed before we review the core composition again at the start of 2026.2 just let us know. ## New Core Proposal I would also like to propose adding jgilaber (jgilaber(a)redhat.com) as a new member of the watcher-core group, based on their recent contributions and engagement with the project. ## Timeline These changes will take effect if there are no objections by our next Watcher IRC meeting on Thursday, September 11th, 2025. Please share any feedback or concerns about these proposed changes. Regards sean

4 3

October 2025 PTG Team Signup Final Call
by Kendall Nelson 08 Sep '25

08 Sep '25

Hello Everyone, Make sure to sign your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 27th to Friday, October 31st 2025! If you haven't already done so and your team is interested in participating, you need to complete the survey[1] by September 14th, 2025 at 7:00 UTC. Please also make sure to register[2] for the event - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2025_ptg_survey [2] PTG Registration: http://ptg.openinfra.dev/

1 0

[neutron] Bug deputy - week of September 1st
by Sławek Kapłoński 08 Sep '25

08 Sep '25

Hi, It was pretty quiet week. Here are details about what happened: ### High - https://bugs.launchpad.net/neutron/+bug/2122065 - ovs agent missing openflow rules due to python error - assigned to Brian, fix proposed https://bugs.launchpad.net/neutron/+bug/2122065 ### Medium - https://bugs.launchpad.net/neutron/+bug/2122110 - [FT] Random errors in OVN ``TestMetadataAgent`` tests - assigned to Rodolfo, fix already proposed, - https://bugs.launchpad.net/neutron/+bug/2122079 - DHCP agent incorrectly releasing leases due to missing client_id - unassigned, Brian already commented there but solution for this may not be that easy to figure out according to the bug report and Brian's comment, ### Low - https://bugs.launchpad.net/neutron/+bug/2121935 - [FT] Random ``DBReferenceError`` errors in the functional tests Edit - assigned to Rodolfo, fix already proposed - https://bugs.launchpad.net/neutron/+bug/2122107 - [FT] Test ``test_initialize_network_segment_range_support_parallel_execution`` failing in the eventlet-removal patch - assigned to Rodolfo, ### To triage - https://bugs.launchpad.net/neutron/+bug/2121961 - Duplicate packet logs with openvswitch driver Edit - I asked Elvira to take a look at it. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Making WIP patch Active (without owner)
by Nimesh Desai 08 Sep '25

08 Sep '25

After the resolving the merge conflict, the following IBM Cinder driver patch is now in ‘Work in Progress’ state. We want to now make it Active, but the owner of the patch is no longer working with the organisation. Thus, the Gerrit UI is not showing option to publish. How to make this patch Active again? The patch was reviewed and had multiple +1 votes earlier. Patch: https://review.opendev.org/c/openstack/cinder/+/879839

6 8

[qa] PTL/Tempest core on PTO
by Ghanshyam Maan 06 Sep '25

06 Sep '25

Hi All, I would like to let you know that I will be on PTO and will return after the 2025.2 release. I will try to check IRC occasionally for any urgent changes that require merging, particularly in Tempest (as there is no other active core). -gmaan

1 0

[release] Release countdown for week R-3
by Thierry Carrez 05 Sep '25

05 Sep '25

Development Focus ----------------- The Release Candidate (RC) deadline is next Friday, September 12th, 2025. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2025.2 branch will be cut. This branch will track the 2025.2 "Flamingo" release. Once stable/2025.2 has been created, the master branch will be ready to switch to 2026.1 "Gazpacho" development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2025.2 "Flamingo" plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2025.2 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2025.2 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2026.1 "Gazpacho") to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2025.2 "Flamingo" release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 12th, 2025 (R-3 week) Final RC deadline: September 26th, 2025 (R-1 week) Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 -- Thierry Carrez (ttx)

1 0

[qa][ptg] Call for 2026.1 vPTG QA topic
by Ghanshyam Maan 04 Sep '25

04 Sep '25

Hi All, I have created the etherpad to collect the QA topics for the coming vPTG (2026.1 cycle). Based on the topics, we will decide if we need any slot in PTG. Feel free to add your topics before Sept 12th. - https://etherpad.opendev.org/p/qa-2026.1-ptg -gmann

1 0

[oslo] status of eventlet removal for oslo.service?
by Chris Friesen 04 Sep '25

04 Sep '25

Hi everyone, Looking at the "epoxy" spec for removing Eventlet from oslo.service (https://specs.openstack.org/openstack/oslo-specs/specs/epoxy/remove-eventle…) the very top line is a link to search blueprints.launchpad.net. Following that link it seems like there is no blueprint for removing eventlet from oslo.service, so does the spec itself (with the proposed milestones) represent the current plan? Separately, is there somewhere that shows the progress on the threading backend for oslo.service? I see it exists, are there any limitations on the current implementation? Thanks, Chris

2 1