April 2026 - openstack-discuss - lists.openstack.org

[horizon][plugins][requirements] propose-translation-update broken: enmerkar uses removed pkg_resources
by Jan Jasek 02 Apr '26

02 Apr '26

Hello everyone, Since pkg_resources deprecation, there is still failing job propose-translation-update: https://zuul.opendev.org/t/openstack/builds?job_name=propose-translation-up… The job is not in horizon repository, it is in project-config: https://github.com/openstack/project-config/blob/a980e2f7425e0cd805bae6670a… So the job execution flow is defined outside the horizon and it directly runs shell scripts so our local tox.ini fix is not applied for it: https://review.opendev.org/c/openstack/horizon/+/982432 The problem is that the pkg_resources module has been deprecated and removed from setuptools and enmerkar is using pkg_resources. Radomir created fix PR in the enmerkar repository more than month ago but it seems the library is being unmaintained: https://github.com/Zegocover/enmerkar/pull/8 If I understand the problem correctly, there are multiple possible ways to fix it and all are interfering beyond our team so I would like to discuss it here and maybe get ideas/recommendations from you. I see there two/three “hot-fixes” that seems to be quick/not very complicated but also not very clear and sustainable solutions: The first possible solution is to hardcode setuptools in job: add pip install 'setuptools<82' && to line: https://opendev.org/openstack/openstack-zuul-jobs/src/commit/3d5175f90e389f… Which is a quick workaround, one change in openstack-zuul-jobs repository, but hardcoding something like that is never an ideal fix. The second one is to fix enmerkar itself (replace deprecated pkg_resources and import importlib.metadata), this is what Radomir proposed in enmerkar repository: https://github.com/Zegocover/enmerkar/pull/8/changes but as the repository seems to be unmaintained, we would need to do it by ourself as a part of CI which seems to be the most terrible way. And if I understand this comment in global-requirements correctly, then upper-constraints/requirements fix is not a way: https://github.com/openstack/requirements/blob/2897d874a900d28bbeb8ed59a781… Another two/three options are probably the most clean but also the most fundamental. First one is to Fork enmerkar under OpenStack, apply the importlib.metadata fix and keep the same functionality under OpenStack control. Second one is to copy the enmerkar extraction logic directly into the horizon as a local babel extractor. I am not sure how complicated it can be, but it seems to me we already use this exact pattern here: https://github.com/openstack/horizon/blob/743bec1ff27933a7347ed4348681b94b7… . It seems that the extraction logic is single function (160 lines) It has no dependencies beyond Django itself enmerkar is BSD 3-Clause licensed The third one is to replace enmerkar entirely with an alternative library - but I did not find any except django-babel which has the same pkg_resource bug. Also in Horizon requirements.txt is explicitly mentioned: “Most horizon plugins do not have enmerkar in their requirements.txt and they depends on horizon requirements, so we keep it here.” This means whatever solution we choose needs to cover the plugins as well. If we copy the extraction logic into Horizon and register it as a babel extractor entry point, plugins would automatically benefit since they already depend on Horizon. I am not super familiar with all the things around requirements, dependencies and CI but I would like to be. So I would like to discuss it here and hear your opinions and ideas. Thank you, Jan

4 4

Re: [nova][bug triage] Test Run for OpenStack Bug Triage Meeting Wednesday 1st
by René Ribaud 02 Apr '26

02 Apr '26

Hi all, Thank you to everyone who joined this first bug triage session! I'm very happy with how it went. We managed to triage a few bugs, which is a great start. Based on this positive outcome, I plan to make this time slot a regular occurrence after the PTG. For those interested, the trend of "New" bugs can be followed on https://truc.uggla.fr/ I'd also like to welcome Melanie to the bug triage group. Thanks for joining! Following the session, I have assigned new bugs for triage. You can find them on the roster (newly assigned bugs are highlighted in bold): https://etherpad.opendev.org/p/nova-bug-triage-roster Please note there will be no triage meeting next week as I will be on PTO. The next session is planned for April 15th, the week before the PTG, on which I will prepare for it. However, since that week might be busy, I reserve the right to cancel if needed. As a reminder, this meeting is public and open to everyone. It's easy to join the roster. Feel free to add yourself! Here is the link to join: https://meet.google.com/qdy-uqte-apr If you'd like to be added to the calendar invite for this meeting, feel free to ping me. Best regards, René

1 1

OpenClaw as a service on OpenStack
by Nick Barcet 01 Apr '26

01 Apr '26

Hello Everyone, For our internal use Tensormesh (the company behind the LMCache project) has been working on a project to create OpenClaw instances on OpenStack on-demand. Very simple once the control plane (a VM on OpenStack) is configured: 1- User creates an account by authenticating with a valid OAuth source 2- User request the deployment of an OpenClaw instance 3- Instance is created on OpenStack 4. User can further configure their OpenClaw, connecting it to the LLM of their choice, a messaging app, and more We certainly want to make this project open source. I was wondering what the OpenStack community would think if we launched it as an OpenStack project? Looking forward to your feedback! Nick

1 0

[keystone] meeting canceled today 01-Apr-2026
by Dave Wilde 01 Apr '26

01 Apr '26

Hello folks, Sorry for the late notice but there will not be a Keystone meeting this week. Please reach out via IRC or the mailing list if you need anything. Thanks! /Dave

1 0

OpenStack 2026.1 "Gazpacho" is officially released!
by Elõd Illés 01 Apr '26

01 Apr '26

Hello OpenStack community, The official OpenStack 2026.1 "Gazpacho" release announcement has been sent out: https://lists.openstack.org/archives/list/openstack-announce@lists.openstac… Thanks to all who were a part of the 2026.1 "Gazpacho" development cycle! This marks the official opening of the openstack/releases repository for 2026.2 "Hibiscus" releases, and freezes are now lifted. stable/2026.1 is now a fully normal stable branch, and the normal stable policy applies from now on. Thanks, Előd Illés on behalf of the Release Management team

2 1

[cinder] no festival of reviews friday 2026-04-03
by Brian Rosmaita 01 Apr '26

01 Apr '26

Hello Argonauts, As discussed at today's cinder meeting, we are cancelling this week's festival in celebration of the Gazpacho release of OpenStack. A few notes: 1. The cancellation is for this week only, we will continue to have the festival on the first and third fridays of each month. 2. If your idea of celebration is to devote some time to cinder reviews, you are welcome to do so on your own! 3. This is not an April Fool joke ... seriously, no festival of reviews this week. cheers, brian

1 0