February 2025 - openstack-discuss

CLI clients and neutron QoS packet_rate_limit rules
by Nell Jerram 22 Feb '25

22 Feb '25

Is it just an oversight that the openstack client doesn't support packet_rate_limit rules? [1] Looking at the file names under [2], it looks like that might be true for the neutron client as well. [1] https://github.com/openstack/python-openstackclient/blob/master/openstackcl… [2] https://github.com/openstack/python-neutronclient/tree/master/neutronclient… Best wishes - Nell

2 1

[release] Release countdown for week R-5
by Thierry Carrez 21 Feb '25

21 Feb '25

Development Focus ----------------- We are getting close to the end of the 2025.1 Epoxy cycle! Next week on February 27th, 2025 is the Epoxy-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2025.2 Flamingo cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 27th, 2025. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2025.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 27th, 2025 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also a good time for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Epoxy-3 milestone (feature freeze): February 27th, 2025 (R-5 week) RC1 deadline: March 14th (R-3 week) Final RC deadline: March 28th (R-1 week) Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting canceled Friday, February 21st
by Brian Haley 20 Feb '25

20 Feb '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as I have a conflict. We can cover an RFEs added this week next Friday. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

OVN in latest OpenStack
by Jani Heikkinen 20 Feb '25

20 Feb '25

We have been installing openstack Dalmatian based on Debian packages on our institution. I am currently trying to configure OVN neutron metadata service, but it seems very hard to find how OVN actually currently does it. See [1.]. The documentation states first, that ovn-metadata-agent will run with a netns and haproxy instance on hypervisor. But there is also a reference to having metadata support in ovn-controller. In addition, I have seen hints suggesting that neutron-ovn-agent and neutron-ovn-metadata-agent would be exclusive to each other. What is the currently up-to-date way to configure OVN metadata agent? Especially, is there any up-to-date instructions how to properly configure neutron's related config files? We have following versions of ovn and ovs: openvswitch-common 3.1.0-2 (+deb12u1) ovn-common 23.03.1-1 (~deb12u2) ovn-host 23.03.1-1 (~deb12u2) neutron-ovn-metadata-agent 2:25.0.0 (-5~bpo12+1) neutron-ovn-agent 2:25.0.0 (-5~bpo12+1) Best Regards, Jani Heikkinen [1.] https://docs.openstack.org/networking-ovn/latest/contributor/design/metadat… -- Berner Fachhochschule / Bern University of Applied Sciences IT-Services / Team Linux & Infrastructure Services Jani Heikkinen IT Linux Engineer ___________________________________________________________ Dammweg 3, CH-3013 Bern Telefon direkt +41 31 848 68 14 Telefon Servicedesk +41 31 848 48 48 jani.heikkinen(a)bfh.ch

5 10

how to clear instance actions
by Jiatong Shen 20 Feb '25

20 Feb '25

Hello Experts, During operating an old deployment, we found that instance_action as well as instance_action_event stores many records. The instance with actions are still in use. I would like to ask if there is any tool to clear instance action & events? Thank you very much for your help. -- Best Regards, Jiatong Shen

2 1

[all][elections][tc] 2025.2 cycle TC Election Campaigning Kickoff
by Ian Y. Choi 19 Feb '25

19 Feb '25

Developers, The TC Election Campaigning Period has now started [1]. Although there are no polls that need to be held [2], during the next couple days, you are all encouraged to ask the candidates questions about their platforms [3], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. TC Candidates, Each of you has posted a platform [3], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. Ian Y. Choi, on behalf of the election officials. [1] https://governance.openstack.org/election/ [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://opendev.org/openstack/election/src/branch/master/candidates/2025.2/…

1 0

[all][elections][ptl][tc] Combined PTL/TC 2025.2 cycle Election Nominations End
by Ian Y. Choi 19 Feb '25

19 Feb '25

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 6 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Barbican, Ironic, Masakari, OpenStack_Charms, Oslo, Zaqar There are 0 projects that will have elections: . -- TC Election Details -- There are 5 candidates for 5 seats. The official candidate list is available on the election website[1]. Now begins the campaigning period where candidates and electorate may debate their statements. Given that there are no polls that need to be held, this concludes the election process. Congratulations to our new and returning leaders. Thank you, Ian Y. Choi, on behalf of the election officials. [0] https://governance.openstack.org/election/#ptl-candidates [1] https://governance.openstack.org/election/#tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[horizon] Automatic refresh of page elements/content
by Barros Frossard, Davi 19 Feb '25

19 Feb '25

Hi everyone, I would like to query about implementing a feature: Automatic refresh of page elements/content on openstack dashboard (horizon). I'm a developer working on starlingx dashboard (gui) project, which is based on openstack dashboard. We noticed that all content on starlingx dashboard doesn't get updated if a change occurs. So, as a workaround, a full page reload is required. We have added a patch to customize horizon package and enable automatic refresh in some of the content. But this is not a definitive solution, since it doesn't solve auto refresh for all page elements/content: https://review.opendev.org/c/starlingx/upstream/+/941145 We also noticed errors on browser's console related to mutation events, although I'm not sure this is relevant for the discussion: https://bugs.launchpad.net/horizon/+bug/2098785 Do you have any plans to add such a feature? Or should we submit a blueprint? Thank you for your time. Regards, Davi Frossard

2 1

[largescale-sig] Next meeting: February 19, 9utc
by Thierry Carrez 19 Feb '25

19 Feb '25

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250219T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 2

[election][cloudkitty] PTL candidacy for the 2025.2 release cycle
by Rafael Weingärtner 19 Feb '25

19 Feb '25

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the 2025.2 release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/942176 -- Rafael Weingärtner

1 0

[cinder][nova] NVMe over RMDA
by holger.bielefeld＠uponu.com 19 Feb '25

19 Feb '25

Hi all, does anyone know if NVMe over RDMA is supported to attach it with Cinder/Nova to a QemuKVM Hypervisor? In addition to our ceph, we would also like to connect a block storage and in order to be able to retrieve the full performance, this must be done with the above-mentioned connection. Thanks in advance. Holger

4 3

LAST CALL: PTG April 2025 Team Signup Deadline!
by Kendall Nelson 18 Feb '25

18 Feb '25

Hello Everyone, This is your *LAST CALL* to sign your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, April 7th to Friday, April 11th 2025! If you haven't already done so and your team is interested in participating, you need to complete the team-signup survey[1] by Feb 21st, 2025 at 7:00 UTC. Then make sure to register[2] - it’s free :) Individual registrations help us coordinate details of the event to attendees. Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/ptg_april_2025_survey [2] PTG Registration: http://ptg.openinfra.dev/

1 0

Cinder volume service and high availability question
by Jim Kilborn 18 Feb '25

18 Feb '25

Hello, I am trying to figure out how to get cinder volume service to use a virtual name for the cinder volume host. We have three controllers that are setup with keepalived and haproxy with a virtualized servername that is used in the various openstack .conf files. This allows either server to shutdown and we can still access the web interface, create vms and volumes, etc. because the virtual hostname is used in all the configurations. However, for cinder volumes, it puts the hostname of the server in os-vol-host-attr:host rather than my virtual name. This causes issues if the controller that was used to create the volume is down, we can't easily manage the volume without modifying that field in the cinder database. If the virtual name could be used, either server could manage the volume with the backend, with no manual changes to the db. The only server related setting in my cinder.conf is my_ip, and that is the ip of the actual server, not the virtual ip Is active/active cluster not supported with cinder?

2 1

[horizon] Automatic refresh of page elements/content
by dbarrosf＠windriver.com 18 Feb '25

18 Feb '25

Hi everyone, I would like to query about implementing a feature: Automatic refresh of page elements/content on openstack dashboard (horizon). I'm a developer working on starlingx dashboard (gui) project, which is based on openstack dashboard. We noticed that all content on starlingx dashboard doesn't get updated if a change occurs. So, as a workaround, a full page reload is required. We have added a patch to customize horizon package and enable automatic refresh in some of the content. But this is not a definitive solution, since it doesn't solve auto refresh for all page elements/content: https://review.opendev.org/c/starlingx/upstream/+/941145 We also noticed errors on browser's console related to mutation events, although I'm not sure this is relevant for the discussion: https://bugs.launchpad.net/horizon/+bug/2098785 Do you have any plans to add such a feature? Or should we submit a blueprint? Thank you for your time. Regards, Davi Frossard

1 0

[horizon] Automatic refresh of page elements/content
by Barros Frossard, Davi 18 Feb '25

18 Feb '25

Hi everyone, I would like to query about implementing a feature: Automatic refresh of page elements/content on openstack dashboard (horizon). I'm a developer working on starlingx dashboard (gui) project, which is based on openstack dashboard. We noticed that all content on starlingx dashboard doesn't get updated if a change occurs. So, as a workaround, a full page reload is required. We have added a patch to customize horizon package and enable automatic refresh in some of the content. But this is not a definitive solution, since it doesn't solve auto refresh for all page elements/content: https://review.opendev.org/c/starlingx/upstream/+/941145 We also noticed errors on browser's console related to mutation events, although I'm not sure this is relevant for the discussion: https://bugs.launchpad.net/horizon/+bug/2098785 Do you have any plans to add such a feature? Or should we submit a blueprint? Thank you for your time. Regards, Davi Frossard

1 0

BaaS
by Odil Yusupov 18 Feb '25

18 Feb '25

As I researched there is no solution for backing up openstack virtual machines. What is the best way to organize BaaS on openstack environment? I have used snapshots and converted them to images, but this is not production solution. Thank you for your support

6 6

[octavia] Blocking a specific network for the VIP of LBs
by Thomas Goirand 18 Feb '25

18 Feb '25

Hi there! In our setup, we offer to our customers, on top of floating IPS, access to an OpenStack internal network that contains public IPs. The idea is that they can, using this network, spawn VMs with a public IP directly on the NIC of their VMs. The issue is, some customers also use this network for the VIP of their LBs. While this seems to work, actually, instead of reserving a single public IP address, it reserves 3 IPs. Not a big deal for us, as they are billed internally, though it's rather bad for our customers. On top of that, whenever one of the subnet of this network becomes full, it becomes impossible to failover amphoras spawned in this subnet. Each time one runs into ERROR, it's kind of a bad situation where we have no way to fix, except contacting the customer and ask them to fix their setup. So we advise our customers to spawn a port first, use that port for the LB, and associate a floating IP address to the original port. This is described in our doc here: https://docs.infomaniak.cloud/network/loadbalancer_usecase_simple_http/ However, as you may know, customers never read the docs. And therefore, we'd like to forbid the use of that shared OpenStack internal network for the VIP of LBs. But as much as possible, this isn't a feature of Octavia. Is it? I'd like to implement the feature. What's the best way to do so? Would a new "forbidden_networks" directive would do, and then have a check at the API level? Or is there a better way using the API policy? Also, wouldn't it be possible that Octavia just reuse the ports that it currently hold, rather than asking new ports for the failover? If so, any clue where the code that does that could be fixed? I'd love to have this fixed AND the forbid network feature too... Cheers, Thomas Goirand (zigo)

4 3

[tc][election] mnasiadka TC candidacy for 2025.2
by Michał Nasiadka 18 Feb '25

18 Feb '25

Hello, I'd like to announce my candidacy for the Technical Committee. This is would be my first TC term (I have never applied for a TC seat). My relations with OpenStack started around Liberty release as a user and Ocata as a Kolla developer. Since Yoga release I became PTL for Kolla (that also includes Kolla-Ansible and Kayobe). I'm also a core reviewer for the Magnum project and diskimage-builder. Throughout my commercial career I've been working with OpenStack clouds in service provider (including VMware and Microsoft hypervisors managed by OpenStack), telco and HPC environments - which give me a broad view of the different use cases for running a cloud. Due to my PTLship of a deployment project - I will probably be focused on operators' perspective and cloud managability aspects - which if possible I'd like to improve - and by that also improve the overall experience of using OpenStack. Thank you for considering my candidacy, Regards, Michal Nasiadka

1 0

Issues with installing Zun on Compute node
by Milan M 18 Feb '25

18 Feb '25

I was trying to install openstack 2024.2 zun on compute node. and following the page https://docs.openstack.org/zun/2024.2/install/compute-install.html for installation. I am facing the issue of docker "--cluster-store" support. I am using Docker 27.5 version. Reading the documentation online, i am confused. Some places it is, mentioned that it is fixed. and some places it suggest to uses docker 22. At few places in your mail you have mentioned to stop using kuryr and use CNI. And official documentation still says to use --cluster store. What is the current state and the correct solution. Please guide me.

1 0

[openstack-helm] [Ceilomter] Image docker.io/kolla/ubuntu-source-ceilometer-api:wallby does not exist
by daniel890723＠gmail.com 18 Feb '25

18 Feb '25

Hello daniel here Recently we somehow has to test the telementry for Openstack right now we have the promethues Openstack-exporter set up and works pretty well but when installing ceilometer it shows the image does not exist search the repository and seems like the ubuntu-source-ceilometer-api image only support up to ocata and the ceilometer Chart for openstack-helm hasn't been up date for a while Do you guys still support ceilometer? or it's better to just stick with promethues? Daniel

2 2

vm migration
by engineer2024 17 Feb '25

17 Feb '25

I am testing vm migration manually using virsh from one compute node to another: --- nova@ccompute:~$ virsh migrate instance-0003457f0 qemu+ssh://<remote-ip>/system --live --verbose --unsafe error: Unable to open file: /var/lib/nova/instances/f4d4r423r4d/console.log: No such file or directory nova@ccompute:~$ ll /var/lib/nova/instances/f4d4r423r4d/ drwxr-xr-x 2 nova nova 4096 Feb 17 15:43 ./ drwxr-xr-x 14 nova nova 4096 Dec 16 22:31 ../ -rw------- 1 nova root 56864 Feb 17 15:43 console.log -rw-r--r-- 1 libvirt-qemu kvm 1154624 Feb 17 15:35 disk -rw-r--r-- 1 nova nova 79 Dec 16 22:30 disk.info ------ I am doing the above as 'nova' user. Why is it failing even though it has r/w access to the console file ? Thanks elinux

5 7

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

17 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 17 Feb '25

17 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 17 Feb '25

17 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 17 Feb '25

17 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