- openstack-discuss - lists.openstack.org

[openstack-helm] Vasyl Saienko as new core reviewer
by Vladimir Kozhukalov 18 Feb '25

18 Feb '25

Hi dear helmers, I would like to suggest a new member of the Openstack-Helm core team. Vasyl Saienko from Mirantis has been actively contributing to the project recently. He prepared lots of improvements for Mariadb, Memcached, Libvirt, Rabbitmq and other charts. He also made plenty of valuable code reviews (28 reviews for the last 90 days). Please share you opinion on this. -- Best regards, Kozhukalov Vladimir

4 4

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-6)
by Goutham Pacha Ravi 18 Feb '25

18 Feb '25

Hello Stackers, We're six weeks away from the coordinated 2025.1 ("Epoxy") release [1]. The next couple of weeks are chock-full of release deadlines. We're closing the nomination period for the OpenStack PTL+TC elections on 2025-02-19 at 23:45 UTC [2]. If you're looking to lead a project team or join the OpenStack TC, do nominate yourself at the earliest. Election officials will also be generating electoral rolls at this deadline. To ensure you are able to vote, please confirm that you've signed up for emails from the CIVS voting platform before that deadline: https://civs1.civs.us/cgi-bin/opt_in.pl In the past week, the OpenStack Technical Committee defined an Upstream Investment Opportunity for the year [3]. The community is actively looking for organizations to sponsor a Quality Assurance developer to augment the OpenStack QA team. Since the team has a far-reaching impact on the quality and maintainability of all OpenStack software, support would be most appreciated. The TC also defined the Tested Runtimes for the 2025.2 ("Flamingo") release cycle. This will be a non-SLURP release and we are expanding testing with Python 3.13 while simultaneously dropping support for Python 3.9 [4]. A number of other governance proposals remain under community review. Finally, the TC expressed support for the proposal to move the OpenInfra Foundation under the Linux Foundation. This conversation is ongoing, and several important concerns have been raised and answered [5]. === Weekly Meeting === The TC meeting last week was held over IRC, and it was well attended [6]. We followed up on several long-running tasks, including the maintenance of the "openstackdocstheme" and "os-api-ref" repositories. Both of these are widely used across OpenStack documentation; however, we need more code reviewer attention to get some critical maintenance patches in. We discussed fixes to the election roll generation scripts to expand the list of repositories used to collate contributors. We'll follow up on this before the electoral roll generation deadline [2]. Dr. Jens Harbott (frickler) discussed the effort to transition "unmaintained/wallaby" branches across OpenStack repositories to "end-of-life." He proposed the change this week [7], and we have until 2025-03-14 to make any modifications to the patch. The final topic was a strategic consideration regarding the OpenInfra Foundation potentially joining the Linux Foundation. Several important concerns were raised during the meeting. One key concern was the LF's recommendations to limit contributions from certain countries. These restrictions currently exist within the OpenInfra Foundation as well. By joining forces with LF, Jonathan Bryce (jbryce) mentioned that he was "hopeful we can have a bigger impact on getting these regulations to view open source properly." The next meeting of the OpenStack TC is today, 2025-02-18. It will be held via IRC on OFTC's #openstack-tc channel at 18:00 UTC. Please find the agenda in the meeting wiki [8]. I hope you'll be able to join us! === Governance Proposals === ==== Merged ==== - Define 2025 upstream investment opportunities | https://review.opendev.org/c/openstack/governance/+/939507 - Define testing runtime for 2025.2 release | https://review.opendev.org/c/openstack/governance/+/941141 - Propose Extra-ACs from I18n SIG (2025.1) | https://review.opendev.org/c/openstack/governance/+/941743 ==== Open for Review ==== - Deprecate ironic-lib | https://review.opendev.org/c/openstack/governance/+/939278 - Cleanup policy popup leads list | https://review.opendev.org/c/openstack/governance/+/941148 - Switch Ironic to Distributed Leadership | https://review.opendev.org/c/openstack/governance/+/941935 - Add Watcher project update liaison | https://review.opendev.org/c/openstack/governance/+/940168 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === - 2025-02-19: Nominations submission deadline for 2025.2 TC/PTL Elections: https://governance.openstack.org/election/ - 2025-02-28: 2025.1 ("Epoxy") Feature Freeze and release milestone 3 [1] - 2025-03-06: SCALE 2025 + OpenInfra Days NA (https://www.socallinuxexpo.org/scale/22x) - 2025-03-11: OpenInfra Board Meeting: https://board.openinfra.org/ - 2025-04-07: OpenInfra PTG Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] OpenStack Election Website: https://governance.openstack.org/election/ [3] QA Developers Needed: https://governance.openstack.org/tc/reference/upstream-investment-opportuni… [4] Tested runtimes for 2025.2: https://governance.openstack.org/tc/reference/runtimes/2025.2.html [5] Help us shape the OpenInfra Foundation's next chapter: https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/th… [6] TC Meeting IRC Log 2025-02-11: https://meetings.opendev.org/meetings/tc/2025/tc.2025-02-04-18.00.log.html [7] Transition unmaintained/wallaby to EOL: https://review.opendev.org/c/openstack/releases/+/941458 [8] TC Meeting Agenda, 2025-02-18: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[manila][election] Carlos da Silva candidacy for 2025.2 Manila PTL
by Carlos Silva 18 Feb '25

18 Feb '25

Hello zorillas and interested stackers, I would like to announce my candidacy to be Manila PTL over the 2025.2 (Flamingo) cycle. I have been working with these amazing contributors and community members for many cycles. If elected, this will be my 6th cycle as a PTL. We shared a lot of accomplishments and faced lots of challenges together. We have continuously been delivering features, fixes, and enhancements requested by operators. We are making solid progress on enhancing the review bandwidth by actively adding more people to the core team and promoting engaging activities around reviews, to get more traction. We have also been closing the gap on the Manila UI features, implementing OpenAPI schemas, integrating manila with OpenStack SDK and enhancing our documentation. For the next cycle, I would like to continue what we have been doing, but also focus on: * Tech debt: continue the efforts to get parity between Manila APIs and Manila UI, complete the rootwrap->privsep migration. * Eventlet: python-manilaclient is successfully migrated, and we will continue the process for all other manila repositories. * Ensuring we are making progress on the integration Barbican and the implementation of share encryption. * Work with the contributors to ensure we have healthy testing jobs for first party CI drivers. Thank you for your consideration. Carlos da Silva IRC: carloss

1 0

[tc][election] gouthamr's TC Candidacy for 2025.2
by Goutham Pacha Ravi 18 Feb '25

18 Feb '25

Hello Stackers, I am submitting my candidacy for another term on the OpenStack Technical Committee. Over the past year, I had a rare privilege of being a first-time TC member, and its Chair. I was lucky to have enormous support from the team and past chairs to be effective. Over this time, I fostered open, consensus-driven discussions, making my best effort to let every voice be heard and ensure that governance is accessible to all contributors. I worked to bridge the gap between the community and the TC through weekly summary emails, and engagement with contributors at PTGs, in-person events and online meetings. TC decisions are more transparent and inclusive in the process. I advocated for contributor initiatives, conducted onboarding workshops, promoted internships, and helped connect contributors and project leadership. I assisted in the revival of project teams, improving election processes, securing project trackers, and OpenStack’s presence on PyPI and Launchpad. This ensured that our community was a reliable and well-maintained ecosystem for its users and contributors. Beyond community engagement, the TC I was part of collectively made meaningful governance changes to direct our limited resources to high-impact areas, things that were more important to the community, than any single contributing organization. I will continue pushing for this, with a bias toward strengthening the community. Looking ahead, my priorities for the next year include grooming the next set of OpenStack leaders, furthering cross-community collaboration, driving work that ensure OpenStack’s continued relevance, including a sustained focus on critical community goals and improvements. I'm excited to support the OpenInfra community as a project leader should OpenStack and OpenInfra projects move under the Linux Foundation. I believe OpenStack thrives because we've created a welcoming, productive environment for all contributors, new and experienced alike. If re-elected, I'll ensure that OpenStack remains an inclusive, innovative, and technically strong open-source community. Thank you for your consideration. Sincerely, Goutham Pacha Ravi (gouthamr) [1] https://review.opendev.org/c/openstack/election/+/942001

1 0

Understanding update in Heat orchestration templates
by Uday Dikshit 18 Feb '25

18 Feb '25

Hello Team we are using Heat to automate orchestration of our application nodes. So please consider a case: I am running 3 nodes in the heat stack. And let's say I have made some updates in the the application code over these 3 nodes. So when I scale up the stack orchestrates and add another node but with the original image. To deal with this if I update the stack template heat rebuilds the original 3 nodes as well with the new snapshot image which makes my application to be unavailable during the update process. It would be really helpful if anybody could put in some ideas around this on how work this case around? Thanks in advance Uday Dikshit

1 0

[elections][ptl][keystone] Stepping down as PTL
by Dave Wilde 18 Feb '25

18 Feb '25

Hello, Due to a recent change in my career path I’ve come to the difficult decision that I need to step down as the Keystone PTL. Over the past 4 years as the PTL the Keystone project has really come a long way, from the establishment of reviewathons and an engaged team of core reviewers to the implementation of some long sought after features and a clean up and modernization of the codebase. This is all due to some very dedicated folks and I’ld like to pass on my personal thanks to them for all of the hard work. Keystone is at a very interesting point in it’s history and I think the future holds bright things for the project, I would like to still be involved but due to the time constraints of my new position I no longer have the bandwidth to manage the day to day aspects of such a large project. I’m looking forward to helping whoever takes the reins in whatever ways that I can. Thanks again, it’s been a pleasure. /Dave

1 0

[blazar][elections][ptl] Leaving the PTL role
by Pierre Riteau 17 Feb '25

17 Feb '25

Hello Blazar community, Having been Blazar PTL since the Stein cycle, it is time to pass the torch to someone else. I would be happy to help the new PTL with their duties, especially during their first cycle. I will stay involved in the community anyway. Cheers, Pierre Riteau (priteau)

1 0

[neutron] Bug deputy report (week starting on February 10)
by Elvira Garcia Ruiz 17 Feb '25

17 Feb '25

Hi folks! Here you have the list of bugs reported for Neutron during last week (10 Feb - 16 Feb). There is one Undecided bug because I'm unsure on how to prioritize it, so we can discuss it at tomorrow's meeting if that is ok. Critical --------- - https://review.opendev.org/c/openstack/neutron/+/941511 Regular user can modify router SNAT flag Fix proposed by Rodolfo: https://review.opendev.org/c/openstack/neutron/+/941511. Rodolfo noted this might need more than just this patch. High ------ - https://bugs.launchpad.net/neutron/+bug/2098085 SRIOV mechanism driver may attach to the wrong segment where a host has access to multiple segments of the same network Assigned to Andrew Bonney Incomplete --------------- - https://bugs.launchpad.net/neutron/+bug/2097747 neutron not update ovn routers Undecided --------------- - https://bugs.launchpad.net/neutron/+bug/2098621 ports can attempt to bind to the wrong segment Best regards, Elvira

1 0

[all][elections][ptl][tc] Combined PTL/TC 2025.2 cycle Election Nominations Last Days
by Sławek Kapłoński 17 Feb '25

17 Feb '25

Hi, A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 19, 2025 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2025-02-05 23:45:00 UTC Nominations end @ 2025-02-19 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 2 days, 13:41:25 Nominations progress : 81.64% --------------------------------------------------- Projects[1] : 40 Projects with candidates : 15 ( 37.50%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 25 (Barbican Blazar Cinder Cloudkitty Glance Heat Ironic Keystone Manila Masakari Monasca Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Oslo Puppet_OpenStack Quality_Assurance Storlet s Sunbeam Swift Tacker Telemetry Vitrage Zaqar) --------------------------------------------------- TC Candidates : 1 (5 Required) =================================================== Stats gathered @ 2025-02-17 10:03:35 UTC This means that with approximately 2 days left, 25 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] Support for Portworx
by Waines, Greg 17 Feb '25

17 Feb '25

Does anyone know how to use a https://portworx.com/ kubernetes-based storage solution as the storage backend for Cinder ? There is a Pure Storage driver listed in https://docs.openstack.org/cinder/latest/configuration/block-storage/volume… . https://docs.openstack.org/cinder/latest/configuration/block-storage/driver… BUT I do NOT believe this is the correct driver for interfacing with an https://portworx.com/ storage cluster. AND Neither the portworx documentation site ( https://docs.portworx.com/ ) nor the portworx github ( https://github.com/portworx ) have any information about integration with Cinder or OpenStack. ( ... although I believe it used to ... ) any info would be appreciated, Greg.

2 2