February 2024 - openstack-discuss

[ptl][election][keystone] PTL Candidacy for 2024.2
by Dave Wilde 28 Feb '24

28 Feb '24

Hello, I would like to continue my tenure as PTL of Keystone. Over the past cycle we have made some great progress especially around the cadence in getting patches reviewed and merged. I would like to focus this next cycle on seeing that [1] is implemented as well as some much needed backlog cleanup. I would also, finally, like to get a "known-issues" section added to the documentation as well as ensuring that our documentation is up to date. Thanks for your time and support and I'm looking forward to another great cycle. [1]: https://specs.openstack.org/openstack/keystone-specs/specs/keystone/2024.1/… /Dave

1 0

TC Candidacy
by Amy Marrich 28 Feb '24

28 Feb '24

I am declaring my candidacy for the Technical Committee. I currently serve on the TC and have contributed to multiple projects over the years within OpenStack as well as being an operator which I feel gives me a well rounded view of what makes OpenStack and how the pieces should work together and what the users need. I feel I represent all members of the community from the small private clouds to the teams running large public clouds. I also feel my experiences helping with OpenStack Upstream Institute, OpenStack OPS Meetup team, the OpenStack mentoring program, and the Git and Gerrit workshops help me to connect with contributors from those just starting out to those who have been here from the beginning. My main goal for rejoining the TC is to take my experiences with Operators and making sure they have a voice within the our decisions so that we can better meet the needs of our users. Thanks, Amy Marrich (spotz)

1 0

[cinder][kubernetes] pvc stuck in reserved state
by Eugen Block 28 Feb '24

28 Feb '24

Hi, we have a couple of k8s clusters in our openstack environment (Victoria) and are facing some problems when pods get moved to different worker nodes. The PVCs get stuck in "reserved" state, and they only get attached after resetting the volumes to "available" state. First I thought it was due to the missing multiattach volume type which seems to work fine in our customer's cluster. I also found the "duplicate connector" error messages in the nova-compute.log: > Unable to update attachment.(Invalid volume: duplicate connectors > detected on volume But after adding the multiattach volume type and retyping the affected volumes, the PVCs still get stuck in "reserved" state while I don't see any error messages on the hypervisors anymore. So it seems that something has changed/improved, but now I don't have a trace where to look next. Could this be a cinder-csi driver issue or something? Our cinder backend is ceph (Pacific). Not sure which information could help so please ask for anything I can provide. Any pointers are highly appreciated! Thanks! Eugen

1 1

[ptl][election][kuryr] PTL non-candidacy for 2024.2
by Roman Dobosz 28 Feb '24

28 Feb '24

Hello, I'm not going to run for PTL of Kuryr for Dalmation. I encourage Kuryr contributors to run for PTL and will offer any assistance needed for whoever is elected. Thanks, Roman Dobosz (gryf)

1 0

[election][tc] Candidacy for the TC
by James Page 28 Feb '24

28 Feb '24

Hi All, I'd like to announce my candidacy for the Technical Committee. For those of you who do not know me, I've been involved with OpenStack from the very early days of the project. I've attended many OpenStack summits and Project Teams Gatherings over the years and have been privileged to help the project grow from its small beginnings to the established cloud platform that it has now become. I was the main driver behind migration of the OpenStack Charms to its current home as an official OpenStack project which I then led for many cycles as PTL and I remain an active core developer on this project. I'm the current PTL of Sunbeam which was accepted into OpenStack last year as a new incubating project, providing a reboot of the charmed approach to deploying OpenStack utilising the many new projects that have appeared since we started the OpenStack Charms project back in 2011. I also work as part of the team responsible for the packaging and distribution of OpenStack as part of Ubuntu. I have been a member of the TC for the last year providing a voice from a deployment tooling and distribution perspective. I would like the opportunity to continue in this role providing what I believe is a valuable perspective to the technical governance of the OpenStack project. In particular I think we need to address some of the challenges around the general health of wider ecosystem dependencies of OpenStack to ensure that we move forward onto a stable base benefiting operators, distributors and developers. Thank you for taking the time to consider my candidacy for this role. Regards James Page (irc:jamespage)

1 0

[puppet][murano] Retiring puppet-murano
by Takashi Kajinami 28 Feb '24

28 Feb '24

Hello, As you may know, TC decided to exclude Murano from 2024.1 release because of its health status[1]. Based on this fact, and also another fact that puppet-murano has had no real development activities for long, I'd propose retiring puppet-murano now. It may be too late to make release deliverable decision. However our puppet modules are tightly coupled with openstack release cycles and we can't assure compatibility between our modules and inactive components, which are no longer aligned with the consistent release cycle. Please let me know if you have any concerns. Thank you, Takashi [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[ptl][election][sunbeam] PTL candidacy for 2024.2
by Hemanth N 28 Feb '24

28 Feb '24

Hello OpenStack Community, I am nominating myself for the Sunbeam PTL position during the 2024.2 cycle. I am a core team member of the Sunbeam project from the incubation stage and contributed to most of the charms that are part of the sunbeam project. In the last cycle we focussed on moving the 20+ charm repo's to a mono repo which helped reduce the codebase and easy maintenance of all the sunbeam charms. In the 2024.2 cycle, my priorities will be * Adding new features or charms and filling gaps to enable charms to be production ready * Stabilise the existing charms or libraries * Bug smashing * CI stability Thank you for your support. Best Regards, Hemanth Nakkina (hemanth, hemanth.nakkina(a)canonical.com)

1 0

Tim Burke candidacy for Swift PTL
by Tim Burke 28 Feb '24

28 Feb '24

I'm pleased to announce my candidacy for Swift PTL for the Dalmation cycle. As usual, we have a great many projects currently in flight: - Supporting Python 3.12 - Adding more fine-grained metrics, while keeping it configurable to not break existing metrics pipelines nor overwhelm them - Improving S3 compatibility, enabling a broader community of tools to work out of the box - More operator tooling for expiring objects - Better process management for WSGI servers - Backend ratelimiting to improve per-node load shedding I'm excited to see how each of these will move forward over the next cycle. Tim Burke

2 1

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Nominations Last Days
by Ian Y. Choi 28 Feb '24

28 Feb '24

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 28, 2024 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 @ 2024-02-14 23:45:00 UTC Nominations end @ 2024-02-28 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 23:49:45 Nominations progress : 92.91% --------------------------------------------------- Projects[1] : 47 Projects with candidates : 30 ( 63.83%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 17 (Barbican Cloudkitty Ec2_Api Freezer Glance Keystone Kuryr Magnum Murano OpenStackAnsible OpenStack_Charms Sahara Senlin Skyline Solum Trove Watcher) --------------------------------------------------- TC Candidates : 7 (5 Required) =================================================== Stats gathered @ 2024-02-27 23:55:15 UTC This means that with approximately 2 days left, 17 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…

1 0

[ptl][election][cinder] PTL candidacy for 2024.2
by Jon Bernard 27 Feb '24

27 Feb '24

Hi All, I would like to announce my candidacy for PTL of the Cinder project for the 2024.2 cycle. I think Rajat has done an excellent job serving the project and I would like to carry existing efforts forward while continuing to focus maintaining a healthy and productive community around the Cinder project. I've been contributing to the Cinder project in varying capacity for close to 10 years. I've worked on migration and replication at the driver layer, mentored new contributors from the outreachy project, and provided bug fixes and reviews wherever possible. I'm a core reviewer and also a stable core. I have served as the release liaison for the last 2 cycles and run a weekly bug squashing meeting to help maintain our launchpad backog. We continue to face review bandwidth pressure. Emphasis should be placed on encouraging contributors to do code reviews and to recognize the efforts of those currently participating. There are several potential core reviewers and I feel that empowering the community is one way to increase engagement and the quality of our releases. 3rd party CI continues to be crucial resource for evaluating driver-specific changes. Maintaining good 3rd party CI for the drivers supported in Cinder by providing clear documentation and requirements will be a focus. Additionally, we have room for improvement in our backup and restore use case. My goal is to improve the entire backup/restore situation so that it can be leveraged by users in production environments. Our customers are using 3rd party backup products to backup workloads and volumes and I think this is one are where improvements here can directly benefit users. In summary, I would like to continue the efforts made by Rajat and continue to focus the areas most in need of attention for the 2024.2 cycle. I will do my best to make a positive contribution to both the technical and community aspects of Cinder during my time as PTL. Thank you for your consideration. -- Jon Bernard (jbernard)

1 0