- Zuul-discuss - lists.opendev.org

Gerrit User Summit will be Colocated with OpenInfra Summit Europe 2025
by Clark Boylan 28 Apr '25

28 Apr '25

There are even more reasons to attend the OpenInfra Summit Europe 2025: Gerrit User Summit [0] will be colocated with OpenInfra Summit Europe 2025. Join us to participate in building the future of Zuul, Gerrit and Open Infrastrcuture. Many Zuul deployments are hooked up to at least one Gerrit server and provide CI test results to that code review system. Whether or not you already deploy Zuul alongside Gerrit, this will be a great opportunity to get connected to and get involved with both communities. There are other colocated events that may be of interest too. Find out more on the colocated events page [1]. [0] https://groups.google.com/g/repo-discuss/c/OzoBp2LPMYA [1] https://summit2025.openinfra.org/co-located-events/ Clark

1 0

Bitergia dashboard outage due to maintenance
by Ildiko Vancsa 24 Apr '25

24 Apr '25

Hi Zuul community, I’m reaching out to let you know that the Zuul Bitergia metrics dashboard[1] will be unavailable for a short period of time due to scheduled maintenance, where the underlying OpenSearch cluster will be updated. Details of the downtime: * Start Date: Monday, April 28th at 9:00 AM CEST (12:00 AM PDT) * End Date: Tuesday, April 29th at 4:00 PM CEST (7:00 AM PDT) __During this maintenance window, the dashboard will be inaccessible. Please also note that data updates will not resume until Wednesday.__ Thank you for your understanding. Best Regards, Ildikó [1] https://zuul.biterg.io/app/dashboards#/view/Overview ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation

1 0

Registration is live for the OpenInfra Summit Europe!
by Clark Boylan 17 Apr '25

17 Apr '25

Hi everyone, We’re excited to announce that registration is now open for the OpenInfra Summit Europe 2025! This is the official event for all things Zuul. Location: École Polytechnique Paris-Saclay, France Dates: October 17-19, 2025 Register now: https://summit2025.openinfra.org/ The OpenInfra Summit brings together the regional community building and running open source infrastructure across cloud, containers, edge, AI, and more. Whether you’re an upstream contributor, operator, or someone exploring how to integrate open source into your infrastructure strategy — this is the place to connect, learn, and collaborate. The CFP and Sponsorships are also now live! There are a number of tracks that may be relevant to your interests. In particular for Zuul related efforts, there is a CI/CD and Development Infrastructure track. If you've got something interesting to share about Zuul this is a great place to do it. The CFP closes June 13: https://cfp.openstack.org/app/2025summit/all-plans Become a sponsor: https://summit2025.openinfra.org/sponsor/ If you have any questions please reach out to summit(a)openinfra.dev Clark

1 0

OpenInfra Summit Europe Scheduled for October 2025
by Clark Boylan 08 Apr '25

08 Apr '25

Hello everyone, I am very excited to share that the OpenInfra Summit Europe has been officially scheduled for October 17-19, 2025, at École Polytechnique near Paris, France[1]! The OpenInfra Foundation is currently recruiting members of the CFP committee to join a kickoff call on Thursday. This call will be used to plan the CFP tracks for the OpenInfra Summit, and we would love to have representation from the various OpenInfra projects. If you would like to participate in the programming committee or any other committee, please email Helena Spease at helena(a)openinfra.dev. I am also happy to try and point people in the right direction if you have any questions and prefer to reach out to me. We’re excited to bring the community together in France, and we hope to have you there! [1] https://openinfra.dev/blog/openinfra-summit-2025 Clark

1 1

Important discussion about the OpenInfra Foundation's future
by Jeremy Stanley 12 Mar '25

12 Mar '25

The OpenInfra Foundation's board of directors is considering a significant organizational change, and your feedback is critical to assist them in their decision. Please read this announcement on the foundation mailing list: https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/th… You can follow up publicly on that list with any questions or input you have for the board and staff, or in one of the public feedback conference calls mentioned there, as well as privately to Jonathan Bryce, Clark Boylan or myself if you prefer to give feedback in confidence. Thanks as always for your interest in the future of our community! -- Jeremy Stanley

2 1

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

19 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

April 2025 PTG Dates & Team Signup Kickoff
by Kendall Nelson 24 Jan '25

24 Jan '25

Hello Everyone, I am pleased to announce the next OpenInfra PTG[1] will be taking place April 7-11, 2025! Registration will open soon! To sign up your team, you must complete the survey[2] by February 21st at 7:00 UTC. We NEED accurate contact information (email and and IRC nickname ideally) for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[3] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[4] as well. If you have any questions, please reach out to ptg(a)openinfra.dev! Information about signing up for time slots will be sent to moderators after the team signup deadline. Continue to visit openinfra.org/ptg for updates. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.org/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/ptg_april_2025_survey [3] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [4] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

2024 OpenInfra Foundation Annual Report
by Clark Boylan 15 Jan '25

15 Jan '25

The OpenInfra Foundation staff have published 2024's annual report: https://openinfra.org/annual-report/2024 The report includes highlights from the Zuul project and other OpenInfra projects. Thank you to everyone who helped make 2024 a great year for Zuul and OpenInfra. Take a moment to appreciate what we have accomplished over the last year. I am looking forward to what we can get done in 2025. Please feel free to share these anywhere you think people may be interested in seeing our year in review, or that of our sibling communities and other activities supported by the foundation. Clark

1 0

Vote Now! OpenInfra Foundation Election
by Clark Boylan 14 Jan '25

14 Jan '25

Hi everyone, Voting is open now for the 2025 OpenInfra Foundation Individual Director Election. You must have joined the Open Infrastructure Foundation as an Individual Member by Sunday, July 14, 2024 to vote in this election, per the bylaws [1]. To vote, check your email (or your spam folder) for your personal link to vote. The subject line is: OpenInfra Foundation 2025 Individual Director Election You can review the candidates here [2] Voting will close this Friday, January 17th, 2025 at 1900 UTC. If you have any questions, please contact secretary(a)openinfra.dev. [1] https://openinfra.org/legal/bylaws [2] https://openinfra.dev/election/2025-individual-director-election/candidates Thanks, Clark

1 0

Project lead election
by James E. Blair 07 Jan '25

07 Jan '25

Hi, The position of Zuul Project Lead is an elected position described in our governance document[1]. I currently hold the position, and would be happy to continue in that position for another year. If elected, I plan to continue my current hands-off approach. I believe that all of the Zuul Maintainers are empowered to collectively decide on and execute our vision for the project. My purpose is to help articulate that vision when necessary, drive the process of attaining consensus, and be a point of contact and representative for the project in circumstances where a single person is needed (but in those cases, I promise to share as much of that work as possible with the rest of the team). I have uploaded a change[2] to update the expiration date of my term. If any other Zuul Maintainers would like to nominate themselves for the position, please upload a similar change and send a reply to this message to this list. The nomination period will close on January 15, 2025. If there are other candidates, we will hold a Condorcet election at that time. -Jim [1] https://zuul-ci.org/docs/zuul/governance.html#zuul-project-lead [2] https://review.opendev.org/938608

1 0

Zuul is Now on Bluesky!
by Helena Spease 05 Dec '24

05 Dec '24

Hello Everyone, We’re thrilled to announce that Zuul and the OpenInfra Foundation now have a presence on Bluesky! This is part of our continued effort to connect with our community and share updates in new and engaging ways. Here’s where you can now find us: - Zuul on Bluesky: https://bsky.app/profile/zuul-ci.org - OpenInfra Foundation on Bluesky: https://bsky.app/profile/openinfra.org Don’t forget, that Zuul is already active on these platforms: - Mastodon: https://social.openinfra.dev/@ZuulCI - Twitter: https://x.com/ZuulCI And, the OpenInfra Foundation is already active on these platforms: - Mastodon: https://social.openinfra.dev/@OpenInfra - Twitter: https://x.com/openinfradev - Facebook: https://www.facebook.com/openinfradev - LinkedIn: https://www.linkedin.com/company/openinfra-foundation Join the conversation and engage with the OpenInfra community wherever you are most active! Cheers, Helena helena(a)openinfra.dev Community Programs Coordinator The OpenInfra Foundation <https://openinfra.dev/>

1 0

Zuul Log Upload Issue
by xuq.fnstxz＠fujitsu.com 25 Nov '24

25 Nov '24

Hi everyone, I am currently in the process of setting up Zuul, and I have encountered an issue during the final step of uploading logs. I have configured the following in the relevant script, where "log.server.com" refers to the log server and site_log refers to a secret. > - hosts: localhost > roles: > - role: add-fileserver > fileserver: "{{ site_log }}" > - hosts: "log.server.com" > gather_facts: false > tasks: > - block: > - import_role: name=upload-logs > - import_role: name=buildset-artifacts-location > vars: > zuul_log_compress: true > zuul_log_url: "http://log.server.com" > zuul_logserver_root: "{{ site_log.path }}" > zuul_log_verbose: true > environment: > SOCKS5_PASSWD: SOCKS5_PASSWD > - secret: > name: site_log > data: > fqdn: log.server.com > path: /srv/static/logs/ > ssh_username: myuser > ssh_known_hosts: | > host ecdsa-sha2-nistp256 host-key > ssh_private_key: !encrypted/pkcs1-oaep > - encrypted content > - encrypted content My Zuul server is able to SSH directly to the log server after configuring a SOCKS5 proxy in the ssh config. > Host log.server.com > ProxyCommand connect -S socks5-user@socks5.proxy.com:1080 %h %p However, when I attempt to run the upload-logs process, I encounter the following issue: > 2024-11-22 11:52:15.577255 | TASK [upload-logs : Create log directories] > 2024-11-22 11:56:24.439122 | log.server.com | ERROR > 2024-11-22 11:56:24.440537 | log.server.com | { > 2024-11-22 11:56:24.440670 | log.server.com | "msg": "Data could not be sent to remote host \"og.server.com\". Make sure this host can be reached over ssh: ssh: connect to host log.server.com port 22: Connection timed out\r\n", > 2024-11-22 11:56:24.440790 | log.server.com | "unreachable": true > 2024-11-22 11:56:24.440880 | log.server.com | } I would greatly appreciate your assistance in resolving this matter. If you need any additional information or access to specific configurations, please let me know. Thanks and Regards, Inori

2 3

2024 Zuul Fourth Quarter Project Update Blog Post
by Clark Boylan 23 Nov '24

23 Nov '24

Hello everyone, I wanted to call out that earlier this week I drafted a blog post [0] quickly covering the last several months of Zuul development. I think it is helpful to occasionally pause and recognize the work that we have accomplished as a community. I would like to make this a regular occurrence for the Zuul community, drafting at least one update blog post a quarter. If there is interesting in helping out with this process please let me know. [0] https://zuul-ci.org/blog/#20241118a Clark

1 0

Pipeline and job setting about zuul
by Qi Xu (Fujitsu) 08 Oct '24

08 Oct '24

Hi, I'm configuring Zuul to run CI tests on nodepool's fc and iscsi nodes for the "openstack/cinder" project hosted on "review.openstack.org". My goal is to trigger a pipeline and execute tests on these nodes whenever a patch is submitted to, or a "recheck" comment is added to a patch in the "openstack/cinder" repository on "review.openstack.org". Successful tests should result in a +1 vote. In my tenant file, I've configured "config-project" to "openstack/project-config" and "untrusted-project" to "openstack/cinder". However, after running the command of zuul, the pipeline and job details displayed on the Zuul webUI show configurations from openstack/project-config and openstack/cinder. The pipeline and job I configured are not displayed on it. I think this is related to my config-project setting, but I'm afriad about impacting the community's setup if directly modify the Zuul configurations in "openstack/project-config" and "openstack/cinder". Could you please help? Thanks and Regards, Inori.

1 0

Error about Leaked Pipeline Cleanup
by xuq.fnstxz＠fujitsu.com 29 Sep '24

29 Sep '24

Hello everyone, I'm building zuul through 'pip install zuul' on my ubuntu22.04, and now I'm configuring the zuul service. After executing the command 'zuul-scheduler', I found the following error in the log every hour. > Traceback (most recent call last): > File "/home/stack/.local/lib/python3.10/site-packages/zuul/scheduler.py", line 717, in _runGeneralCleanup > self._runLeakedPipelineCleanup() > File "/home/stack/.local/lib/python3.10/site-packages/zuul/scheduler.py", line 784, in _runLeakedPipelineCleanup > self.zk_client.client.get_children(state_root)) > File "/home/stack/.local/lib/python3.10/site-packages/kazoo/client.py", line 1293, in get_children > ).get() > File "/home/stack/.local/lib/python3.10/site-packages/kazoo/handlers/utils.py", line 78, in get > raise self._exception > kazoo.exceptions.NoNodeError I checked scheduler.py and found it to be a non-existent path ‘/zuul/tenant/{safe_tenant}/pipeline’. And I also checked the zookeeper nodes and found that 'zuul' has no children named 'tenant'. > >>> zk.get_children('zuul') > ['components', 'cache', 'nodepool', 'locks', 'layout', 'scheduler', 'ltime', 'system', 'layout-data', 'cleanup', 'executor', 'config', 'events', 'merger'] I think it's my tenant's config that may have some issues, here's my config file, is there anything wrong or missing? And I'm wondering if this error will have an effect on zuul. > - tenant: > name: myCI > source: > gerrit: > untrusted-projects: > - openstack/cinder Thanks and Regards, Inori

1 0

OIDC Workload Identity Federation Spec
by James E. Blair 12 Sep '24

12 Sep '24

Hi, Tobias proposed a spec at https://review.opendev.org/922450 which describes a way to enrich Zuul's secrets engine with an OpenID Connect Identiy Provider which will enable Zuul to provide an identity to a job which can be trusted by federated third party services. The spec has seen some initial positive review already. Given that, I would like to merge it next Friday, Sept 20, if it looks like we have consensus then, or of course delay it if folks identify problems or need more time to review. Thanks, Jim

1 0

Need help with zuul and long running async jobs
by nitin chadha 08 Aug '24

08 Aug '24

Hello, I am working on evaluating zuul for CI workflows at my present company, and I need some guidance on modelling our CI using zuul. We use gerrit, and have some home grown tools which act on a review request before it is finally merged. The entire pipeline runs in jenkins, and I would like to slowly move to zuul. We have some build jobs which are triggered when a review request is opened, and then we run some integration tests on them. These build jobs are for different platforms, like x86 or arm and with variations, eg, debug build, testing build, slim build etc. These jobs take a long time, like 12-24 hours or more. Integration tests take even longer because of resource constraints. There are some quick jobs like linting, unit tests etc which can be completed quickly. Breaking down long running jobs is going to take a lot of time, and I was exploring if somehow I can trigger jenkins jobs using zuul, and have zuul schedule testing jobs once build jobs are done. This means zuul nodes would need to wait for a long time, and I don't want to tie down resources. Is there a way to trigger zuul jobs from an API trigger, like jenkins triggering some zuul jobs, or a way to make a zuul job pause ( give up resources ) and start later when some other condition is satisfied? I explored gerrit labels, but there would be a lot of labels to take care of. I also explored the timer trigger driver, but am unsure of how that would help me here. Thanks, Nitin

3 3

Nodepool and Untrusted projects specs
by James E. Blair 10 Jul '24

10 Jul '24

Hi, There are two specs which have received some initial positive review: An update to the nodepool-in-zuul spec: https://review.opendev.org/921521 A spec proposing a method for untrusted projects to configure the jobs run on other projects (useful for superproject-style configurations): https://review.opendev.org/922061 I would like to merge these next Tuesday, July 16, if it looks like we have consensus then, or of course delay it if folks identify problems or need more time to review. Thanks, Jim

1 0

Merge templates with jobs containing dependencies
by Guillaume Vincent 02 Jul '24

02 Jul '24

Hello Zuul memo list, This is the first time I'm posting here, I hope this is the right place to suggest an improvement to the tool. Or learn a new solution. I'm trying to improve the definition of my jobs and templates on Zuul. Imagine the following context with these 3 jobs: - build-el8-rpm-job: a job that builds a rpm for el8 - build-el9-rpm-job: a job that builds a rpm for el9 - rpm-publish-job: a job which publishes the rpms of the jobs it has as a dependency The definition of a Job on zuul could look like this ```yml - project: name: project_1 check: jobs: - build-el8-rpm-job - build-el9-rpm-job gate: jobs: - build-el8-rpm-job - build-el9-rpm-job post: jobs: - build-el8-rpm-job - build-el9-rpm-job - rpm-publish-job: dependencies: - build-el8-rpm-job - build-el9-rpm-job ``` On this job we produce the 2 rpms (el8 and el9) and we publish everything in a post job. But there are projects that don't need to be built for el9 for example. the job definition would look like this: ```yml - project: name: project_2 check: jobs: - build-el8-rpm-job gate: jobs: - build-el8-rpm-job post: jobs: - build-el8-rpm-job - rpm-publish-job: dependencies: - build-el8-rpm-job ``` As I have a lot of projects I will use templates. ## 1st solution: One template per environment TLDR: This doesn't work. Dependencies in templates are not merged. ```yml - project-template: name: build-and-publish-el8-template check: jobs: - build-el8-rpm-job gate: jobs: - build-el8-rpm-job post: jobs: - build-el8-rpm-job - rpm-publish-job: dependencies: - build-el8-rpm-job - project-template: name: build-and-publish-el9-template check: jobs: - build-el9-rpm-job gate: jobs: - build-el9-rpm-job post: jobs: - build-el9-rpm-job - rpm-publish-job: dependencies: - build-el9-rpm-job ``` If I use these 2 templates: ```yml - project: name: project_3 templates: - build-and-publish-el8-template - build-and-publish-el9-template ``` The resulting project definition is: ```yml - project: name: project_3 check: jobs: - build-el8-rpm-job - build-el9-rpm-job gate: jobs: - build-el8-rpm-job - build-el9-rpm-job post: jobs: - build-el8-rpm-job - build-el9-rpm-job - rpm-publish-job: dependencies: # missing build-el8-rpm-job here - build-el9-rpm-job ``` The el8 rpm is not published because the definition of `rpm-publish-job` of the last template overwrites that of the previous template. ## 2nd solution: The only solution I found, create templates by combination TLDR: The number of templates grows exponentially. The solution I use is to create one template per publish definition: ```yml - project-template: name: build-el8-template check: jobs: - build-el8-rpm-job gate: jobs: - build-el8-rpm-job - project-template: name: publish-el8-template post: jobs: - build-el8-rpm-job - rpm-publish-job: dependencies: - build-el8-rpm-job - project-template: name: build-el9-template check: jobs: - build-el9-rpm-job gate: jobs: - build-el9-rpm-job - project-template: name: publish-el9-template post: jobs: - build-el9-rpm-job - rpm-publish-job: dependencies: - build-el9-rpm-job - project-template: name: publish-el8-and-el9-template post: jobs: - build-el8-rpm-job - build-el9-rpm-job - rpm-publish-job: dependencies: - build-el8-rpm-job - build-el9-rpm-job ``` And now I can do ```yml - project: name: project_3 templates: - build-el8-template - build-el9-template - publish-el8-and-el9-template - project: name: project_4 templates: - build-el8-template - publish-el8-template - project: name: project_5 templates: - build-el9-template - publish-el9-template ``` But we realize that I will have to create too many templates. The number of dependencies grows exponentially. ## Improvement proposal A more elegant way to do this would be to merge the dependencies array: ```js merge_templates([ { post: { jobs: { "rpm-publish-job": { dependencies: ["build-el8-rpm-job"], }, }, }, }, { post: { jobs: { "rpm-publish-job": { dependencies: ["build-el9-rpm-job"], }, }, }, }, ]) == { post: { jobs: { "rpm-publish-job": { dependencies: ["build-el8-rpm-job", "build-el9-rpm-job"], }, }, }, }; ``` And duplications are removed: ```js merge_templates([ { post: { jobs: { "rpm-publish-job": { dependencies: ["build-el8-rpm-job", "build-el9-rpm-job"], }, }, }, }, { post: { jobs: { "rpm-publish-job": { dependencies: ["build-el9-rpm-job"], }, }, }, }, ]) == { post: { jobs: { "rpm-publish-job": { dependencies: ["build-el8-rpm-job", "build-el9-rpm-job"], }, }, }, }; ``` We will be able to use the first solution and compose our templates together. Maybe I'm using the tool in the wrong way. Maybe there is a way to merge the dependencies array? Thank you Guillaume

2 1

OpenInfra Foundation Diversity and Inclusion Working Group Survey
by Clark Boylan 01 Jul '24

01 Jul '24

Hello, The OpenInfra Foundation Diversity and Inclusion working group recently moved their information about the working group to a new page [0][1]. This update is a good reminder that there is a Diversity and Inclusion Survey [2], hosted by the working group, that all participants in OpenInfra Foundation projects (including Zuul) are encouraged to take. This working group is tasked with ensuring that our project collaboration spaces are welcoming and inclusive. Feedback given on the survey is one of the ways that the working group ensures it has the information necessary to aid the projects in this endeavor. The responses to this survey are anonymous and kept confidential. Non-sanitized results are not shared outside OpenInfra Foundation staff and board delegates in the D&I Working Group. If you have time please take the survey. [0] https://lists.openinfra.dev/archives/list/foundation@lists.openinfra.dev/th… [1] https://openinfra.dev/about/diversity [2] https://openinfrafoundation.formstack.com/forms/openinfra_diversity_inclusi… Clark

1 0

Superproject subscription to submodules updates managed by Zuul
by Fredrik Medley 01 Jul '24

01 Jul '24

Hi, I'm working on better support for submodules in Zuul. The basic idea is to support something like Gerrit's super project subscription, https://gerrit-review.googlesource.com/Documentation/user-submodules.html, but not just for Gerrit. 1. Let Zuul know about project subscriptions. 2. Start jobs for the super projects, now when Zuul knows about the update in the submodule. 3. Teach the Zuul mergers about bumping submodules. 4. Let Zuul create bump commits in the super projects when the submodules get submitted. This allows for cross server functionality and makes the feature function for any Git server. The plan is to implement things in the following way: 1. Extend the project configuration with "project-subscriptions": [ { "name": "(Canonical) name of the submodule project", "branch": "'.' or another branch name", "path": "Optional path in the repository to update", }, ... ] While doing this, also let Zuul read the .gitmodules file and generate such configuration automatically, according to speculative merging. 2. Extend QueueItem with extra BumpChanges for each super project. This can be done recursively. Zuul already today support dependency cycles, i.e. having multiple changes in a single QueueItem. Changes ahead can affect what super projects are subscribing, so the list of BumpChanges need to be reset when a QueueItem is dequeued and calculated every time it is enqueued. 3. Let the Zuul merger process the projects and branches in order. When a merge commit has been created for a submodule, the commit hash can be used in further merges of super projects, recursively. 4. To create a super project bump commit with the submitted submodule commits, Zuul need to know resulting commit hashes. One way is to submit the projects in order, but what happens if there is a problem with submitting some of them? To solve this, I would like to make the merger deterministic, i.e. let the commit date be the enqueue time of the QueueItem. When the gate has finished, push the tested commits to `refs/zuul/gate/<target-branch>`. When the commits have been pushed to all the projects, we know that uploading has succeeded and a second step of pushing to the actual target ref can be done "for free". Hopefully this will can be done much quicker and might also close existing changes or pull requests on the server. Questions: Shall reading .gitmodules be feature gated per tenant and overridden per super project? What is the best way to handle the submit process? If Zuul owns the merging, then the commit hash tested in gate will also end up in the repository, which is a great benefit. Maybe there is a possibility to discuss these things on the OpenInfra Day Sweden on Tuesday (7th May, 2024). Best regards, Fredrik

3 6

PTG October 2024 Team Signup
by Kendall Nelson 24 Jun '24

24 Jun '24

Hello Everyone, Hopefully you have seen by now, the next OpenInfra PTG[1] which will take place October 21-25, 2024 virtually! Registration is now open[2]! To sign up your team, you must complete the survey[3] by August 30th at 7:00 UTC. We NEED accurate contact information (email and IRC nickname ideally) for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[4] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out to ptg(a)openinfra.dev! Information about signing up for time slots will be sent to moderators after the team signup deadline. Continue to visit openinfra.dev/ptg for updates. [1] PTG Site: https://openinfra.dev/ptg/ [2] PTG Registration: http://ptg.openinfra.dev/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2024_ptg_survey [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst -- Kendall Nelson *Senior Upstream Developer Advocate* The OpenInfra Foundation <https://openinfra.dev/>

1 0

Elasticsearch driver
by James E. Blair 20 Jun '24

20 Jun '24

Hi, In reviewing our current dependency caps, I noticed that we have pinned the python elasticsearch client as "elasticsearch<8.0.0". I looked into removing that cap, and found that we have no test coverage of the elasticsearch library itself. Typically, we try to have some kind of fake or mock that exercises at least some library code, if not all of it. But in this case, there is none. Version 8 of the library is known to break Zuul in the initializer for the library, but our tests won't catch that. If I were to propose to remove the cap, we won't have any feedback that it's broken until someone tries it in production. The compatibility page for the Python ES client has this to say: "Elasticsearch language clients are only backwards compatible with default distributions and without guarantees made." [1] That is a little confusing to me. But I read it as "You might be able to use the python elasticsearch client version 8 with an elasticsearch version 7 server, but we won't promise it will work. If you really want guarantees, you should install two versions simultaneously." I think it's worth asking the following questions: * Should we continue to have an ES driver in Zuul, or does the tight coupling of client library to server version make it more appropriate to offload this to an external service that moves MQTT messages into ES? * If we want to keep the ES driver, can we support multiple server versions with a single client library? * If we can not, should we switch to installing both elasticsearch7 and elasticsearch8 in Zuul and switch between the two at runtime? Is there a volunteer that will do this work? * If we can support both with version 8 of the elasticsearch library, is there a volunteer to do this work? * Can we update the testing to exercise more of the client library (via a mock or fake elasticsearch)? Is there a volunteer for this work? Thanks, Jim [1] https://elasticsearch-py.readthedocs.io/en/v8.14.0/#compatibility

2 2

Status page spec
by James E. Blair 17 Jun '24

17 Jun '24

Hi, Felix has posted a spec which aims to collect user stories related to the status page, for aid in review of his changes to the status page. The spec has seen some initial positive review already. Given that, I would like to merge it next Monday, June 24, if it looks like we have consensus then, or of course delay it if folks identify problems or need more time to review. It is located here: https://review.opendev.org/918505 Thanks, Jim

1 0

Spec for allowing untrusted projects to configure other projects
by James E. Blair 15 Jun '24

15 Jun '24

Hi, I have proposed a spec at https://review.opendev.org/922061 which describes a system where we can selectively allow certain untrusted-projects to configure the project-pipeline config for certain other untrusted-projects. This has some relevance to work involving superprojects, in that it will allow superprojects to configure the jobs that run on subprojects. But it is also useful outside that context, in that it will allow for centralized control of what jobs run on certain projects without all the permissions (and restrictions) that come with a config-project. Please take a look and provide any feedback. Thanks, Jim

1 0