October 2024 - openstack-discuss - lists.openstack.org

[kolla][neutron][ovn] High ovs-dbserver CPU Usage with OVN in Kolla-ansible Large-Scale Deployment
by 韩光宇 17 Oct '24

17 Oct '24

Hi, I have a Wallaby cluster with 5 controller and 130 compute node. Host OS: Rocky 8.7 Deploy tool: Kolla-ansbile kolla_base_distro(container images): centos Network Mode：**OVN** After completing the deployment, the functionality for creating a single instance works as expected, and instances are created successfully. However, the process is extremely slow. When attempting to create instances in bulk, the operation fails on a large scale. During this time, I observed that the ovsdb-server is consuming close to 100% CPU usage. Even without any tasks being processed, the CPU usage remains consistently around 90%, just from the cluster's regular operations. I redeployed the cluster and switched the network mode to Open vSwitch (OVS), and everything works as expected with normal performance. Could anyone offer guidance on what might be causing this issue? I’m aiming to use the OVN mode with Kolla in a large-scale OpenStack cluster (100+ nodes). What configuration or adjustments would I need to make? Thank you in advance for your help! Han Guangyu

2 2

[all][qa] Moving grenade to install things in venv: Enable GLOBAL_VENV
by Ghanshyam Mann 17 Oct '24

17 Oct '24

Hello Everyone, Since 2023.2 devstack by default, installs things in virtual env and due to the old node was not ready in the grenade job, we disabled that with the flag GLOBAL_VENV. Now it is time to enable it in greande also. This also fixes the failure we are getting in the grenade setup for the current master (upgrade testing from stable/2024.2 -> master) which is setuptool error for projects that have pyproject.toml[1]. I have proposed the changes in granade, but at least Octavia, Ironic, and heat jobs are failing. I have proposed some fixes for these projects. - https://review.opendev.org/q/topic:%22grenade-venv%22 I would like to request the project to test their grenade jobs with https://review.opendev.org/c/openstack/grenade/+/930507 and fix the failure if any. I would like to merge the grenade change as soon as its gate passes so that we can set up the grenade testing correctly for the current master. If any project requires a large change/more time to make their grenade jobs work in venv then you can disable the GLOBAL_VENV there for the time being and enable it once things work. [1] https://zuul.opendev.org/t/openstack/build/517b21fc57d6480f902273e58f9032b5 -gmann

1 1

[Glance] Cancelling weekly meetings Today and Next week
by Pranali Deore 17 Oct '24

17 Oct '24

Hello Team !! I won't be able to chair today's meeting, I will be out for some personal reason and also there is nothing much on agenda for this week, So cancelling the meeting for today. Sorry for the last minute update ! Next week's meeting is also cancelled because of the PTG session. So you all next week!! Thanks & Regards, Pranali Deore

1 0

[keystone] What does a multi-region service catalog look like?
by Stephen Finucane 16 Oct '24

16 Oct '24

o/ The question in $subject came up in a discussion earlier today and I neither knew the answer nor was able to discover it by looking at a service catalogs for a few production deployments I have access to (also, the multi-region feature is currently broken in DevStack and likely has been for some time). Crucially, in a "standard" multi-region deployment where there is one Keystone instances and N Nova/Cinder/Glance/Neutron/... deployments, would I have something like the below, where there is only one identity endpoint but multiple e.g. compute endpoints, or would I expect there always to be as many identity endpoints as there are e.g. compute endpoints? { "token": { ... "catalog": [ { "endpoints": [ { "id": "fb757b386a23430d8f4d636b8b45fa89", "interface": "public", "region_id": "RegionOne", "url": "http://10.0.110.125/identity", "region": "RegionOne" } ], "id": "50c4feff9d6149b898fce20ce23904a3", "type": "identity", "name": "keystone" }, { "endpoints": [ { "id": "2ed0cb59adb0415c948f8351b6546d3e", "interface": "public", "region_id": "RegionOne", "url": "http://10.0.110.125/compute/v2.1", "region": "RegionOne" }, { "id": "2ed0cb59adb0415c948f8351b6546d3e", "interface": "public", "region_id": "RegionTwo", "url": "http://10.0.112.232/compute/v2.1", "region": "RegionOne" } ], "id": "87322637c5ab4e7b90bea7a8c1eb9525", "type": "compute", "name": "nova" }, ... ] } } I'm guessing the latter, but I'd like to confirm this. Stephen

3 4

[privsep][nova] howto enable privsep logs in nova
by Benedikt Trefzer 16 Oct '24

16 Oct '24

Hi List I'd like to enable log messages for privsep executions. Currently a log file is created (/var/log/nova/privsep.log) but no content is ever written to it. How do I enable the log (Warning/Info/debug) messages to be written into that file ? Thanks for any hint Benedikt

1 0

[largescale-sig] Next meeting: October 16, 9utc
by Thierry Carrez 16 Oct '24

16 Oct '24

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=20241016T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[manila] CephFS Driver Failing to Connect in Manila on OpenStack
by Shubham Kumar Yadav 16 Oct '24

16 Oct '24

Hi, im trying to install Manila (helm chart) in my Openstack cloud but getting some errors. If you could please help me with those. Im following this doc - https://docs.openstack.org/manila/latest/configuration/shared-file-systems/… 1 - my manila conf looks like conf: manila: DEFAULT: debug: true enabled_share_protocols: NFS,CIFS,CEPHFS enabled_share_backends: cephfsnative1 cephfsnative1: driver_handles_share_servers: False share_backend_name: CEPHFSNATIVE1 share_driver: manila.share.drivers.cephfs.driver.CephFSDriver cephfs_conf_path: /etc/ceph/ceph.conf cephfs_protocol_helper_type: CEPHFS cephfs_auth_id: manila cephfs_cluster_name: rook-ceph cephfs_filesystem_name: myfs 2 - So i created the auth using (according to document) ceph auth get-or-create client.manila -o manila.keyring \ mgr 'allow rw' \ mon 'allow r' 3 - when i try to use the maila keyring i get the error *[rook@cmp-2 ceph]$ ceph --key AQBip/9mCMf4N/jFNKFlwl/hA4j64esWuA== osd ls[errno 13] RADOS permission denied (error connecting to the cluster)*this is what i get after running that not sure what permissions any idea? -> i also tried with admin rights to the auth *[rook@cmp-2 ceph]$ ceph auth get client.manila[client.manila] key = AQBip/9mCMf4N/jFNKFlwl/hA4j64esWuA== caps mds = "allow *" caps mgr = "allow *" caps mon = "allow *" caps osd = "allow *"exported keyring for client.manila * 4 - and also in manila-share pod i see the error 2024-10-08 07:37:25.090 7 INFO manila.share.drivers.cephfs.driver [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] [CEPHFSNATIVE1] Ceph client found, connecting... 2024-10-08 07:37:25.104 7 ERROR manila.share.manager [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] Error encountered during initialization of driver CephFSDriver@lab-11053-26006-ceph-1@cephfsnative1: manila.exception.ShareBackendException: [%(be)s] Ceph client failed to connect. 2024-10-08 07:37:25.104 7 ERROR manila.share.manager Traceback (most recent call last): 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 421, in rados_client 2024-10-08 07:37:25.104 7 ERROR manila.share.manager self._rados_client.connect() 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "rados.pyx", line 690, in rados.Rados.connect 2024-10-08 07:37:25.104 7 ERROR manila.share.manager rados.IOError: [errno 5] RADOS I/O error (error connecting to the cluster) 2024-10-08 07:37:25.104 7 ERROR manila.share.manager 2024-10-08 07:37:25.104 7 ERROR manila.share.manager During handling of the above exception, another exception occurred: 2024-10-08 07:37:25.104 7 ERROR manila.share.manager 2024-10-08 07:37:25.104 7 ERROR manila.share.manager Traceback (most recent call last): 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/manager.py", line 371, in _driver_setup 2024-10-08 07:37:25.104 7 ERROR manila.share.manager self.driver.do_setup(ctxt) 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 274, in do_setup 2024-10-08 07:37:25.104 7 ERROR manila.share.manager rados_client=self.rados_client, 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 424, in rados_client 2024-10-08 07:37:25.104 7 ERROR manila.share.manager raise exception.ShareBackendException( 2024-10-08 07:37:25.104 7 ERROR manila.share.manager manila.exception.ShareBackendException: [%(be)s] Ceph client failed to connect. 2024-10-08 07:37:25.104 7 ERROR manila.share.manager 2024-10-08 07:37:25.105 7 DEBUG manila.utils [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] Finished call to 'manila.share.manager.ShareManager.init_host.<locals>._driver_setup' after 62.106(s), this was the 6th time calling it. log_it /var/lib/openstack/lib/python3.10/site-packages/tenacity/after.py:44 2024-10-08 07:37:25.105 7 DEBUG manila.utils [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] Retrying manila.share.manager.ShareManager.init_host.<locals>._driver_setup in 64.0 seconds as it raised ShareBackendException: [%(be)s] Ceph client failed to connect.. log_it /var/lib/openstack/lib/python3.10/site-packages/tenacity/before_sleep.py:65 any idea what could be wrong? or if there's a better guide available Hope to hear from you soon Thank you!

1 0

[octavia] cancelling weekly meetings today and next week
by Gregory Thiemonge 15 Oct '24

15 Oct '24

Hi Folks, Many contributors have a conflict today with the Octavia weekly meeting, so we are cancelling it. Next week's meeting is also cancelled because of the PTG session on the same day. Thanks, Greg

1 0

Invitation: [openstack-ansible][ptg] Epoxy Team Gathering @ Tue Oct 22, 2024 6pm - 8pm (CEST) (openstack-discuss@lists.openstack.org)
by Hosam Al Ali 15 Oct '24

15 Oct '24

[openstack-ansible][ptg] Epoxy Team Gathering Tuesday Oct 22, 2024 ⋅ 6pm – 8pm Central European Time - Stockholm Join with Google Meet https://meet.google.com/jjg-hwhi-vqg?hs=224 Hey folks! I have booked a relatively short session for next Tuesday, October 22 2024 from 16:00 to 18:00 UTC. The session will happen in a meetpad [1]. Topics for the discussion are held in etherpad [2]. We're having quite a scarce agenda this time, which mostly consist of things which were planned for previous cycles but were never accomplished. So I think we should be good with this 2 hour session for the discussion. If not, or smth will raise during the discussion, we can arrange another discussion during the PTG week. Thankfully, plenty of slots are available this time as well. Hope to see everyone interested in the project there! [1] https://meetpad.opendev.org/osa-epoxy-ptg [2] https://etherpad.opendev.org/p/osa-epoxy-ptg Organizer Hosam Al Ali a.hosam(a)gmail.com Guests Hosam Al Ali - organizer openstack-discuss(a)lists.openstack.org noonedeadpunk(a)gmail.com View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=MHI1YzRhcTNzbTI1… Reply for openstack-discuss(a)lists.openstack.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=MHI1YzRhcTNzbTI1… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

[tc] Weekly IRC meeting on October 22, 2024 is cancelled
by Dmitriy Rabotyagov 15 Oct '24

15 Oct '24

Hi everyone, Due to the PTG [1] which is taking place next week (October 21-25) and TC has already planned to have 2 sessions (you can check on agenda [2] and join us there), it was agreed to skip our regular IRC meeting on October 22. Next TC meeting in IRC channel #openstack-tc on OFTC network is planned on October 29, 2024. [1] https://openinfra.dev/ptg/ [2] https://etherpad.opendev.org/p/oct2024-ptg-os-tc

1 0

[kuryr][tc] Final call for Kuryr PTL/DPL liaisons
by Ghanshyam Mann 15 Oct '24

15 Oct '24

Hello Everyone, Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945 If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945. [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… -gmann

4 10

PTG October 2024 Registration & Schedule
by Kendall Nelson 15 Oct '24

15 Oct '24

Hello Everyone! The October 2024 Project Teams Gathering is right around the corner (October 21-25) and the schedule is being set up by your team leads! Slots are going fast, so make sure to get your time booked ASAP! As a reminder, you can find the team list on the registration page here[4]. You can find the schedule and available slots on the PTGbot website [1]. The PTGbot site is the during-event website to keep track of what's being discussed and any last-minute schedule changes. It is driven via commands in the #openinfra-events IRC channel (on the OFTC network) where the PTGbot listens. If you have questions about the commands that you can give the bot, check out the documentation here[2]. Also, if you haven’t connected to IRC before, here are some docs on how to get setup![3] Lastly, please don't forget to register[4] - It’s FREE. Please let us know if you have any questions via email to ptg(a)openinfra.dev. Thanks! -Kendall (diablo_rojo) [1] PTGbot Site: https://ptg.opendev.org/ptg.html [2] PTGbot Documentation: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [3] Setup IRC: https://docs.openstack.org/contrib <https://docs.openstack.org/contributors/common/irc.html> [4] PTG Registration: http://ptg.openinfra.dev/

1 0

Proposal to resume weekly upstream Oslo IRC meetings.
by Daniel Bengtsson 15 Oct '24

15 Oct '24

Hi everyone, I hope you’re all doing well. I was thinking it might be a good idea to resume the weekly upstream Oslo IRC meetings, especially with the removal of eventlet, which makes it even more relevant. What do you think? Do you have any preferences for the day and time? Looking forward to your feedback! -- Daniel Bengtsson Software engineer

4 4

[openstack-ansible][ptg] Epoxy Team Gathering
by Dmitriy Rabotyagov 15 Oct '24

15 Oct '24

Hey folks! I have booked a relatively short session for next Tuesday, October 22 2024 from 16:00 to 18:00 UTC. The session will happen in a meetpad [1]. Topics for the discussion are held in etherpad [2]. We're having quite a scarce agenda this time, which mostly consist of things which were planned for previous cycles but were never accomplished. So I think we should be good with this 2 hour session for the discussion. If not, or smth will raise during the discussion, we can arrange another discussion during the PTG week. Thankfully, plenty of slots are available this time as well. Hope to see everyone interested in the project there! [1] https://meetpad.opendev.org/osa-epoxy-ptg [2] https://etherpad.opendev.org/p/osa-epoxy-ptg

1 0

RDO Dalmatian 2024.2 Released
by Amy Marrich 15 Oct '24

15 Oct '24

The RDO community is pleased to announce the general availability of the RDO build for OpenStack 2024.2 Dalmatian for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Dalmatian is the 30th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-dalmat… The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud SIG. The Cloud SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/dalmatian/highlights.html but here are some highlights: New Cinder driver features were added, notably, Dell PowerStore active-active support, Dell PowerStore QoS support, NetApp added support to active/active mode in ISCSI/FC drivers, HPE Nimble replication, and StorPool added support clone-across-pools capability. Added Glance support of new add/get location APIs which replaces the image-update (old location-add) mechanism for consumers like cinder and nova to address OSSN-0090 and OSSN-0065. Ironic has enhanced multiple security aspects, for example it now requires rescue passwords to be hashed, it has reduced the logged nodes information during the cleaning phase to avoid showing sensitive data, and it has hardened the communication between the ironic services and the ironic agent requiring an HTTPS url by default. All Neutron supported mechanism drivers (ML2/OVS, ML2/OVN) can now use the WSGI API module, completing the first phase of eventlet library deprecation. Nova Instances with UEFI firmware can now be launched with stateless firmware if their image has the hw_firmware_statelessproperty and if the compute services have libvirt 8.6.0 or later. OpenStack Dalmatian is not marked as Skip Level Upgrade Release Process or SLURP. According to this model (https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…) this means that upgrades will only be supported from the Caracal 2024.1 release. RDO Dalmatian 2024.2 has been built and tested with the recently released Ceph 18.2.0 Reef version (https://docs.ceph.com/en/latest/releases/reef/) which has been published by the CentOS Storage SIG in the official CentOS repositories. *Note:* Follow the instructions in [RDO documentation](https://www.rdoproject.org/install/install-with-ceph/) to install OpenStack and Ceph services in the same host. During the Dalmatian cycle, some projects have been retired or declared inactive upstream. As such, the following packages for some projects are not present in the RDO Dalmatian 2024.2 release: python-saharaclient (https://review.rdoproject.org/r/c/rdoinfo/+/54360) puppet-corosync (https://review.rdoproject.org/r/c/rdoinfo/+/53127) During the next release we will continue working on retiring inactive packages in order to ensure RDO content quality and security. Contributors: During the Dalmatian cycle, we saw the following new RDO contributors: Roman Safronov Archana Singh pkomarov komarov Sergii Golovatiuk Milana Levy Liron Kuchlani Jaromír Wysoglad Arnau Verdaguer Andre Aranha Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 51 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and rdo-website repositories: Alfredo Moralejo Alonso Amy Marrich Ananya Banerjee Andre Aranha Archana Singh Arnau Verdaguer Artom Lifshitz Arx Cruz Bhagyashri Shewale Bohdan Dobrelia Cédric Jeanneret Chandan Kumar Daniel Pawlik Douglas Viroel Fabien Boucher Fiorella Yanac Francesco Pantano Goutham Pacha Ravi Gregory Thiemonge Grzegorz Grasza Harald Jensås Jaromír Wysoglad Joan Francesc Gilabert Joel Capitao Jon Schlueter Karolina Kula Karthik Sundaravel Lewis Denny Liron Kuchlani Lon Hohberger Luigi Toscano Maor Blaustein Marihan Girgis Marios Andreou Martin Kopec Martin Magr Michael Johnson Milana Levy Nicolas Hicher Pini Komarov Roman Safronov Ronelle Landy Sergii Golovatiuk Shreshtha Joshi Soniya Vyas Steve Baker Takashi Kajinami Tobias Urdin Tristan De Cacqueray Yadnesh Kulkarni Yatin Karel The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Epoxy. Get Started To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For those that do not have any hardware or physical resources, there is the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://www.rdoproject.org/community/mailing-lists/. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS IRC channels (#centos, #centos-cloud, #centos-devel in Libera.Chat network), however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[ironic] weekly meeting canceled on Monday October 21
by Riccardo Pittau 15 Oct '24

15 Oct '24

Hello everyone! As per subject, next weekly ironic community meeting won't happen as it conflicts with the PTG See you all at the PTG instead! Ciao Riccardo

1 0

[Glance][PTG] Glance Epoxy/2025.1 vPTG Schedule
by Pranali Deore 14 Oct '24

14 Oct '24

Hello All, Epoxy (2025.1) virtual PTG is going to start next week and we have created our PTG etherpad [1] and also added day wise topics along with timings we are going to discuss. Kindly let me know if you have any concerns with allotted time slots especially for the cross project sessions. Friday is reserved for any unplanned discussions. So please feel free to add your topics if you haven't added yet. NOTE: At the moment we don't have any sessions scheduled on Friday, if there are any last moment request(s)/topic(s) we will discuss that on Friday else we will conclude our PTG on Thursday 24th OCT. The meeting URL is mentioned in etherpad [1] and will be the same throughout the PTG. [1]: https://etherpad.opendev.org/p/oct2024-ptg-glance Hope to see you there!! Thanks & Regards, Pranali Deore

1 0

[neutron] Bug Deputy report week 41 (October 7-13)
by Lajos Katona 14 Oct '24

14 Oct '24

Hi Neutrinos, Here is the bug deputy report of the last week (week 41, October 7-13). It was a really lightweight week from the incoming bug number perspective. * https://bugs.launchpad.net/neutron/+bug/2083832 ([OVN] Host_id value on lsp for router gateway is not updated on failover ) ** In Progress: https://review.opendev.org/c/openstack/neutron/+/931632 Best Wishes Lajos Katona (lajoskatona)

1 0

#eventlet-removal - Progress & Update
by Herve Beraud 14 Oct '24

14 Oct '24

We’re excited to share the latest updates on our ongoing efforts to phase out Eventlet across our various OpenStack projects. Below you’ll find a summary of our progress, key milestones, and important dates to keep in mind as we move forward with this critical initiative. ## Current Status We’ve completed the initial analysis phase across more than 120 OpenStack projects. This includes identifying the various patterns where Eventlet is currently in use and evaluating where it can be safely removed or disabled. Here are some highlights: - Completed Analysis: Projects where Eventlet is used include (but are not limited to): Aodh, Barbican, Nova, Neutron, Tacker, Taskflow, Trove, Venus, Watcher, and Zun. - Eventlet Optional: Several projects have been identified where Eventlet seems to be optional and can be disabled with minimal impact. For these projects, we will move forward the discussion with teams to try deactivating Eventlet in upcoming updates. Once done, projects of this kind would be able to start their migration with more serenity. - Eventlet Required: Some projects still rely heavily on Eventlet for core functionality. For these, we are going to develop specific migration plans. ## Migration Plans in Progress - oslo.db: Preparing its Asyncio based engine facade; - oslo.service: Refactoring plans being discussed to minimize disruption during the migration; - glance: Refactoring code to use native thread model rather than Eventlet More details can be found here: https://review.opendev.org/q/topic:%22eventlet-removal%22 ## Latest Updates - Community Goal Transition: The ongoing community goal for removing Eventlet is now in the process of becoming an official "selected" goal, https://review.opendev.org/c/openstack/governance/+/931254. - Pattern Identification Completed: We’ve identified key patterns related to Eventlet usage, including its common integration with monkey_patch(), eventlet.Timeout, eventlet.GreenPool, and eventlet.wsgi.server(). Visit the official wiki to get more details https://wiki.openstack.org/wiki/Eventlet-removal#Identifying_Common_Pattern ## Important Dates - October 21st: cross PTG session. - October 23rd: cross PTG session (Q&A session and Open Discussion session) ## Call to Action We need your involvement to accelerate the progress of this initiative! If your project is affected by Eventlet, now is the time to start planning your migration. Teams are encouraged to take immediate steps in assessing how to deactivate Eventlet or to transition to alternative solutions. We defined key roles and responsibilities. Those will help us to lower the cost of the migration for our community. Teams are invited to assign them now. Being ready as soon as possible will allow you to better take advantage of the coming PTG sessions. Please find more details about these roles and their short terms tasks: https://wiki.openstack.org/wiki/Eventlet-removal#Roles_and_Responsibilities ## Final Thoughts This is a significant step forward for improving the stability, scalability, and maintainability of our projects. With your continued support, we’re confident that this migration will bring substantial benefits to the OpenStack community. If there are any questions or if you need assistance with your project’s transition away from Eventlet, please join the discussion on the #eventlet-removal channels (OpenStack irc, RedHat slack, mailing list). Thank you for your dedication and hard work! -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

7 8

[all] Runtime dependency on setuptools
by Thomas Goirand 14 Oct '24

14 Oct '24

Hi, A large number of OpenStack projects have a requirement on setuptools. In most cases, this is just a mistake, and it can be removed. This is currently a huge pain for downstream distributions that have to patch this out from requirements.txt, as we're trying to remove python3-pkg-resources which is currently deprecated, and that is added when setuptools is there. Example affected projects: - freezerclient - placement - magnum - oslotest - ... Sending the patches upstream will be too much effort, so I'll write Debian specific patches in the mean time. Please fix your project if you can. Cheers, Thomas Goirand (zigo)

1 0

[neutron] Cancelling CI Meeting for today
by Yatin Karel 14 Oct '24

14 Oct '24

Hello Neutron Team !! I will not be able to chair the CI meeting today as I will be out. Sorry for the late notice. We have some known issues in CI where jobs fail randomly, all are known ones and are being looked upon. A consistent issue in stable/2023.2 openstacksdk periodic job for which i reported[1] [1] https://bugs.launchpad.net/openstacksdk/+bug/2084427 -- Thanks and Regards Yatin Karel

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-24)
by Goutham Pacha Ravi 13 Oct '24

13 Oct '24

Hello Stackers, The Virtual Project Team Gathering (PTG) is next week [1][2]. There are 32 discussion tracks planned throughout the week, along with ad-hoc virtual hallway/water cooler discussions. As a result, many regular weekly IRC meetings will be canceled. Please take a moment to review the PTG Etherpad for the Technical Committee [3]. We encourage community-wide participation on topics such as: - Community Leaders Meeting (2024-10-21 / 1400 UTC): This event is open to all project maintainers, especially PTLs and DPLs. We'll cover several topics of community-wide importance. - Eventlet Removal (2024-10-21 / 1500 UTC): This session will kick off discussions around addressing the technical debt associated with OpenStack services migrating away from the eventlet library. - ...and many more! There may be some minor changes to the schedule based on other cross-project topics being planned. The best way to stay up-to-date is to join OFTC's #openinfra-events channel or watch the event stream on the PTG website [2]. This week, Indiana University will be hosting the OpenInfra community for OpenInfra Days, North America (15-16 Oct 2024). This is a hybrid event, and both in-person and online registrations are still open. If you're attending in person, I’d love to catch up and discuss how the OpenStack TC can assist you. Please don’t hesitate to say hello! === Weekly Meeting === The OpenStack Technical Committee held its weekly meeting on 2024-10-08 [5]. The meeting was well attended. During the meeting, we approved a change to mark the "kuryr-kubernetes" and "kuryr-tempest-plugin" projects as "inactive." This means we won’t be producing any releases from these projects during the 2025.1 "Epoxy" release cycle, and the repositories may soon be retired. If you depend on these projects, please let us know. It’s worth noting that there have been no releases since the 2024.1 "Caracal" cycle. The TC also spent time brainstorming PTG topics and scheduling. We discussed a regression in python-openstackclient that necessitates an update to the recently released 2024.2 "Dalmatian" release. We took action to strengthen the CI jobs for python-openstackclient, adding more scenarios such as upgrade testing with "trunk." The next weekly IRC meeting of the OpenStack Technical Committee is on 2024-10-15, chaired by Dmitriy Rabotyagov (noonedeadpunk). The agenda is available on the meeting wiki page [6]. I hope you can join us. Please remember that you can propose topics by editing the wiki page, and if you do, please include your IRC nick so we can call on you during the meeting. === Governance Proposals === ==== Merged ==== - Mark kuryr-kubernetes and kuryr-tempest-plugin inactive: https://review.opendev.org/c/openstack/governance/+/929698 ==== Open for Review ==== - Propose to select the eventlet-removal community goal: https://review.opendev.org/c/openstack/governance/+/931254 - Propose a pop-up team for eventlet-removal: https://review.opendev.org/c/openstack/governance/+/931978 - Adding Axel Vanzaghi as PTL for Mistral: https://review.opendev.org/c/openstack/governance/+/927962 === How to Contact the TC === You can reach the TC in several ways: 1. Email: Send an email with the tag [tc] on this mailing list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel. 3. Join us at our weekly meeting: The Technical Committee meets every Tuesday at 1800 UTC [6]. --- === Upcoming Events === - 2024-10-15: OpenInfra Days NA, Indianapolis [4] - 2024-10-21: OpenInfra Project Teams Gathering: https://openinfra.dev/ptg/ Thank you 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] "Epoxy" PTG Schedule: https://ptg.opendev.org/ptg.html [3] OpenStack TC PTG Etherpad: https://etherpad.opendev.org/p/oct2024-ptg-os-tc [4] OpenInfra Days North America: https://ittraining.iu.edu/explore-topics/titles/oid-iu/ [5] TC Meeting IRC Log, 2024-10-08: https://meetings.opendev.org/meetings/tc/2024/tc.2024-10-08-18.00.log.html [6] TC Meeting Agenda, 2024-10-15: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[manila] how to connect ceph backend with manila
by Shubham Kumar Yadav 12 Oct '24

12 Oct '24

hello, I'm trying to install manila in my openstack cloud (deployed on k8s cluster) but having problem. 1 -> i created the auth using ceph auth get-or-create client.manila -o manila.keyring \ mgr 'allow rw' \ mon 'allow r' source - https://docs.openstack.org/manila/latest/configuration/shared-file-systems/… 2 -> in manila-share pod i see the error 2024-10-08 07:37:25.090 7 INFO manila.share.drivers.cephfs.driver [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] [CEPHFSNATIVE1] Ceph client found, connecting... 2024-10-08 07:37:25.104 7 ERROR manila.share.manager [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] Error encountered during initialization of driver CephFSDriver@lab-11053-26006-ceph-1@cephfsnative1: manila.exception.ShareBackendException: [%(be)s] Ceph client failed to connect. 2024-10-08 07:37:25.104 7 ERROR manila.share.manager Traceback (most recent call last): 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 421, in rados_client 2024-10-08 07:37:25.104 7 ERROR manila.share.manager self._rados_client.connect() 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "rados.pyx", line 690, in rados.Rados.connect 2024-10-08 07:37:25.104 7 ERROR manila.share.manager rados.IOError: [errno 5] RADOS I/O error (error connecting to the cluster) 2024-10-08 07:37:25.104 7 ERROR manila.share.manager 2024-10-08 07:37:25.104 7 ERROR manila.share.manager During handling of the above exception, another exception occurred: 2024-10-08 07:37:25.104 7 ERROR manila.share.manager 2024-10-08 07:37:25.104 7 ERROR manila.share.manager Traceback (most recent call last): 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/manager.py", line 371, in _driver_setup 2024-10-08 07:37:25.104 7 ERROR manila.share.manager self.driver.do_setup(ctxt) 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 274, in do_setup 2024-10-08 07:37:25.104 7 ERROR manila.share.manager rados_client=self.rados_client, 2024-10-08 07:37:25.104 7 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 424, in rados_client 2024-10-08 07:37:25.104 7 ERROR manila.share.manager raise exception.ShareBackendException( 2024-10-08 07:37:25.104 7 ERROR manila.share.manager manila.exception.ShareBackendException: [%(be)s] Ceph client failed to connect. 2024-10-08 07:37:25.104 7 ERROR manila.share.manager 2024-10-08 07:37:25.105 7 DEBUG manila.utils [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] Finished call to 'manila.share.manager.ShareManager.init_host.<locals>._driver_setup' after 62.106(s), this was the 6th time calling it. log_it /var/lib/openstack/lib/python3.10/site-packages/tenacity/after.py:44 2024-10-08 07:37:25.105 7 DEBUG manila.utils [None req-fffe12f7-c7aa-42dc-aea1-bed6f918b278 - - - - - -] Retrying manila.share.manager.ShareManager.init_host.<locals>._driver_setup in 64.0 seconds as it raised ShareBackendException: [%(be)s] Ceph client failed to connect.. log_it /var/lib/openstack/lib/python3.10/site-packages/tenacity/before_sleep.py:65 3 -> when i try to use the maila keyring i get the error *[rook@cmp-2 ceph]$ ceph --key AQBip/9mCMf4N/jFNKFlwl/hA4j64esWuA== osd ls[errno 13] RADOS permission denied (error connecting to the cluster)*this is what i get after running that not sure what permissions any idea? -> i also tried with admin rights to the auth *[rook@cmp-2 ceph]$ ceph auth get client.manila[client.manila] key = AQBip/9mCMf4N/jFNKFlwl/hA4j64esWuA== caps mds = "allow *" caps mgr = "allow *" caps mon = "allow *" caps osd = "allow *"exported keyring for client.manila * 4-> my manila conf looks like conf: manila: DEFAULT: debug: true enabled_share_protocols: NFS,CIFS,CEPHFS enabled_share_backends: cephfsnative1 cephfsnative1: driver_handles_share_servers: False share_backend_name: CEPHFSNATIVE1 share_driver: manila.share.drivers.cephfs.driver.CephFSDriver cephfs_conf_path: /etc/ceph/ceph.conf cephfs_protocol_helper_type: CEPHFS cephfs_auth_id: manila cephfs_cluster_name: rook-ceph cephfs_filesystem_name: myfs any idea what could be wrong? Hope to hear from you soon Thank you!

2 1

[manila] Oct 17th and 24th weekly meeting canceled
by Carlos Silva 11 Oct '24

11 Oct '24

Hello Zorillas! As mentioned in the previous Manila weekly meeting, the Oct 17th meeting is being cancelled, as a couple of people from the audience won't be able to join. The Oct 24th weekly meeting is being cancelled because it is the PTG week, and we will be meeting on several time slots during that week [1]. [1] https://ptg.opendev.org/ptg.html Thank you! Regards, carloss

1 0

[all] Looking for low hanging fruits bugs for first time contributors
by Carlos Silva 11 Oct '24

11 Oct '24

Hello, stackers! Next week, Goutham and I will be hosting a workshop at the OpenInfra Days North America for new contributors, where we are focusing on getting people to submit code to OpenStack projects for the first time. For that, we would like to create a pool of low-hanging-fruit bugs from multiple projects that the attendees could choose what bug they would like to spend some time on fixing. We would like to extend this to all projects, so we would like to ask for your much needed help: If you are aware of an unassigned low hanging fruit bug in the project you are maintaining that could be easily fixed, it would be of much help if you please add it to this etherpad [1], alongside a comment mentioning how you imagine the fix for it. If we don't get assignees this time, no worries, we are always trying to get similar types of bugs for onboarding in our internship initiatives, so it can be picked up later. [1] https://etherpad.opendev.org/p/lhf-bugs-openinfra-days-na Thank you very much for your help! carloss

4 4