- Zuul-discuss - lists.opendev.org

October 2025 PTG Team Signup Kickoff
by Kendall Nelson 09 Jun '25

09 Jun '25

Hello Everyone! The next OpenInfra PTG[1] will take place October 27-31, 2025 and registration for the event is now open[2]! To sign your team up, you must complete the survey[3] by September 14th at 19:00 UTC. If your team is not interested in participating, there is no need to fill out the survey. The contact information (email and preferably also IRC nickname) in the form will be used to share important details with moderators about team signup and further logistics. To ensure you receive all communications please double check and submit *ACCURATE* information! If you are not on IRC, please get on the OFTC network[4] and join #openinfra-events as much of the coordination for the event will be done in the #openinfra-events channel. 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.org! Information about signing up for time slots will be sent to moderators after the team signup deadline. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.org/ptg/ [2] PTG Registration: http://ptg.openinfra.org/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2025_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

1 0

Submit Your OpenInfra Summit Talk This Week!
by Jeremy Stanley 09 Jun '25

09 Jun '25

Are you working on something exciting with Zuul? This is your last chance to share it with the global OpenInfra community at the OpenInfra Summit Europe in Paris[0]! The CFP[1] closes this Friday, June 13, and the Summit organizers are especially looking for talks related to Zuul. Whether you're operating production deployments, contributing upstream, or building new tools, this is the place to share your story. Sponsoring the Summit[2]? If you'd like to be part of the schedule launch marketing happening at the end of June, this Friday is also the deadline to confirm your sponsorship. Don’t miss the chance to highlight your work and connect with the global open source community. [0] My beloved French colleagues would want me to clarify that this is actually "Paris-Saclay" (but it's still very close to Paris!) [1] Sponsorship: https://summit2025.openinfra.org/sponsor [2] CFP: https://summit2025.openinfra.org/cfp -- Jeremy Stanley

1 0

October 2025 PTG Dates & Registration
by Kendall Nelson 04 Jun '25

04 Jun '25

Hello Everyone! The next PTG[1] will take place October 27-31, 2025! Registration is now open[2] and free for all to attend, as per usual. Shortly, I will send along the team sign up to collect groups interested in participating. -- Kendall Nelson *Senior Upstream Developer Advocate* OpenInfra Foundation <https://openinfra.org/> [1] https://openinfra.dev/ptg/ [2] https://ptg.openinfra.org/

1 0

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 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

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

23 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 04 Dec '24

04 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 22 Nov '24

22 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 28 Sep '24

28 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 11 Sep '24

11 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 09 Jul '24

09 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 01 Jul '24

01 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 19 Jun '24

19 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

New status page for the Zuul UI
by Felix.Edel＠bmw.de 06 Jun '24

06 Jun '24

Hi, I’ve been working on a stack of changes to rework the status view in the Zuul UI: https://review.opendev.org/c/zuul/zuul/+/916284 In our Zuul setup we have some tenants which are quite large and have a lot of pipelines and longer (gate) queues. For those tenants, the status page becomes more and more unusable as too much information is shown on this single page. This makes it hard for the “operators” of this tenant to get a clear picture of what’s going on and for the individual “developers” it’s hard to have a look at their individual changes (or queues). So, we have done surveys with some of our key users and tried to find out how the current status view could be improved and what they would expect from such a view (which information should be shown, which actions/options should be available). Based on this and our own experience with the Zuul UI we came up with some improvements which are implemented in the stack mentioned above. Basically, the idea behind those changes is to provide both a “operator-oriented” view and a “developer-oriented” view without mixing both into a single view (which is kind of what the current status view tries to do). Instead of showing all information on a single page, the new approach splits that information into different “scopes”: 1. Status / pipeline overview 2. Pipeline details 3. Individual change Based on those scopes, the pages that handle those focus only on the relevant information, but don’t show too many details about the other scopes. The stack currently covers 1. and 2., whereby 3. is already existing in form of the “single change panel/view”. I’m planning to do a rework of that as well later. Please note, that this is still an ongoing work and not yet finished, so there might be some flaws. If you are interested in this topic or have any questions, don’t hesitate to contact me, or reply to this email. I’d be happy to get some feedback/reviews on those changes. A preview of the new UI can be found here: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Br, Felix

2 2

Submit to the OpenInfra Summit CFP Before May 29, 2024
by Clark Boylan 09 May '24

09 May '24

Hi everyone, The OpenInfra Summit Asia is the first community-led Summit, hosted by the OpenInfra Korea User Group in collaboration with other OpenInfra user groups throughout Asia. I wanted to share that the CFP is currently open and accepting applications until May 29, 2024. The OpenInfra Summit Asia will be co-located with the OCP Regional Summit APAC and will showcase the latest advancements in open source infrastructure software and hardware. I want to encourage the Zuul community to represent the latest advancements with the software by submitting talks to the Summit CFP! If you want to attend and your employer cannot fund your travel, the OpenInfra Foundation is continuing the OpenInfra Travel Support program. You can apply for travel support until May 29. Submit to the CFP: https://openinfrafoundation.formstack.com/forms/openinfra_asia_summit_2024 Apply for the OpenInfra Travel Support Program: https://openinfrafoundation.formstack.com/forms/openinfra_tsp Register for the OpenInfra Summit Asia: https://2024.openinfraasia.org/ If you have any questions, please let me know. Clark

1 0

Gerrit driver and enqueuing items with open / unresolved comments
by Wade Carpenter 04 May '24

04 May '24

While it's not necessarily _required_ with gerrit, it does at least warn in the UI when trying to manually submit a change with open comments. I looked at the docs and could not find a way to have zuul require "no open comments" before enqueueing items into the (gate) pipeline. https://zuul-ci.org/docs/zuul/latest/drivers/gerrit.html#requirements-confi… Did I miss something here? If not, would this be a reasonable thing to request and / or submit a patch to implement?

3 3

"provides" and "requires" no longer supported in dependency cycle?
by A richist 03 May '24

03 May '24

Hello Zuul folk, I have an issue where with ~the following config: - queue: name: Topic allow-circular-dependencies: true dependencies-by-topic: true per-branch: true - job: name: A_build parent: base_build provides: A_build - job: name: B_build parent: base_build requires: - A_build - project: name: A queue: Topic gate: jobs: - A_build - project: name: B queue: Topic gate: jobs: - B_build Having a Gerrit change for both A and B projects, under the same branch and topic, and gate-ing them in the "correct" order, both A_build and B_build start running simultaneously, instead of B_build waiting for A_build's completion. This definitely worked as I expected before upgrading to Zuul 10.0.0 (occurs in 10.1.0 as well). I've also tried changing this to use: - job: name: B_build parent: base_build dependencies: - name: A_build soft: true But got a "job does not exist" error. I assume this is because the branch, where the jobs are defined, is under "always-dynamic-branches" (which is a must in my case). Is this intended behaviour under the new dependency cycle handling? Is there anything else I can try to have B wait for A_build's completion to be able to use A's build artifacts? Regards, Arichist

2 2

MySQL/MariaDB performance problems
by James E. Blair 18 Apr '24

18 Apr '24

Hi, In OpenDev we have noticed some performance problems with Zuul master running with MySQL. I believe we have a path for fixing those, but things may be unstable for the next week or so. If you're running Zuul with MySQL or MariaDB I recommend you avoid upgrading to Zuul master until this is resolved. I'll send an update when it is. -Jim

1 1

OpenInfra Day Sweden Event Schedule is Posted
by Clark Boylan 10 Apr '24

10 Apr '24

I wanted to point out that the OpenInfra Day Sweden [0] event schedule has been posted [1]. There are a number of Zuul talks on the schedule. The event occurs on May 7, 2024 in Gothenburg, Sweden. Registration is free, but required to attend the event. If you find yourself in the area, this is a great opportunity to learn more about Zuul and get in touch with others using Zuul. [0] https://oideurope2024.openinfra.dev/sweden/ [1] https://www.oidsweden2024.se/schedule Clark

1 0

[Diversity] PTG Schedule
by Amy Marrich 06 Apr '24

06 Apr '24

The Diversity and Inclusion working group will hold a session Tuesday, April 9th at 14:00 UTC in the Cactus room. Agenda is available[0], please add any topics. Amy 0 - https://etherpad.opendev.org/p/apr2024-ptg-diversity

1 0

Require correct regular expression for always-dynamic-branches tenant config
by Mithun Mistry 02 Apr '24

02 Apr '24

Hi , We want to apply the tenant configuration always-dynamic-branches for branch names starting with “Feature” and “Release” We have used the following regular expression : gerrit: config-projects: - zuul-config untrusted-projects: - CCB: exclude: - pipeline - project - job - semaphore - nodeset - secret - project-template include-branches: ^((Feature|Release)(\/))?(CCB\d+)(\/.*)?$ always-dynamic-branches: - "^Feature/.*" - "^Release/.*" shadow: zuul-config this does not seem to be working as zuul is still loading zuul configs from these branches. 2024-03-18 09:50:33,208 INFO zuul.TenantParser: Loading configuration from CCB_DTM/zuul.yaml@Release/CCB9/TCL_F8 2024-03-18 09:50:33,225 DEBUG zuul.TenantParser: Waiting for cat job <zuul.zk.event_queues.JobResultFuture object at 0x7f6bc7a326a0> 2024-03-18 09:50:34,007 DEBUG zuul.TenantParser: Cat job <zuul.zk.event_queues.JobResultFuture object at 0x7f6bc7a326a0> got files dict_keys(['.zuul.yaml', 'zuul.yaml']) 2024-03-18 09:50:34,008 INFO zuul.TenantParser: Loading configuration from CCB_DTM/zuul.yaml@Release/CCB9/TCL_F8_1 2024-03-18 09:50:34,024 DEBUG zuul.TenantParser: Waiting for cat job <zuul.zk.event_queues.JobResultFuture object at 0x7f6bc7a3d520> Can you please suggest the correct regular expression for this tenant configuration. We are using zuul version 8.3.1 Regards, Mithun Western Digital

1 0

[PTG] Less than One Month Reminders!
by Kendall Nelson 20 Mar '24

20 Mar '24

Hello Everyone, The April PTG is rapidly approaching and team moderators are signing up for time to meet via the PTGbot. The schedule is filling up and we are excited to see you all! If you have not yet registered, please do so! It's free![1]. Another note about this PTG in particular, Meetpad is the default video conferencing tool. TTeam moderators are able to override the meeting URL if they choose to do so in order to make use of other tools. We do have a few zoom rooms if needed. This is the first PTG we are doing this for, so please give us feedback[2] with as many details as possible if you run into any issues with Meetpad. Open source needs open tools after all! If you have any questions, please let us know via email to ptg(a)openinfra.dev . Thank you! -Kendall Nelson Senior Upstream Developer Advocate The OpenInfra Foundation [1] http://ptg2023.openinfra.dev/ [2] https://etherpad.opendev.org/p/April2024-PTG-Feedback

1 1

Removal of Tests for Older Distro Releases in zuul/zuul-jobs
by Clark Boylan 12 Mar '24

12 Mar '24

Hello, I wanted to give everyone a heads up that we have been removing test jobs for older Linux distro releases in zuul-jobs. So far we've removed testing for OpenSUSE Leap 15.2, Debian Buster, and CentOS 7. We will be removing testing for Ubuntu Xenial in the near future as well. Each of these distro releases is at or very near its end of life. Removing test jobs for these releases will make room for newer distro releases within the OpenDev Zuul deployment which will allow zuul-jobs to run tests against modern distro releases. These removals also mean that zuul-jobs cannot test for compatibility with those older releases. No intentional breakage is planned, but without testing to catch problems we may introduce incompatibilities over time. Clark

1 0

PTG April 2024 Teams List
by Kendall Nelson 23 Feb '24

23 Feb '24

Hello Everyone! The April 2024 Project Teams List is official! Projects + Teams - OpenInfra Foundation Teams - - Diversity & Inclusion Working Group - OpenInfra Edge Computing Group - Kata Containers - OpenDev - StarlingX - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Magnum - Manila - Neutron - Nova - Octavia - OpenStackAnsible - OpenStack-Helm - OpenStackSDK/CLI - Quality Assurance - Release Management - Tacker - Other OpenStack Teams - - OpenStack Security SIG - OpenStack Technical Committee - PublicCloud SIG - RBAC - VDI If your team was planning to meet and isn’t on this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon, I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — it's FREE! As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://ptg2024.openinfra.dev/ <http://ptg2023.openinfra.dev/>

1 1

AI generated contributions
by James E. Blair 20 Feb '24

20 Feb '24

Hi, AI generated code is kind of a hot topic. The Open Infrastructure Foundation is working on developing some recommendations around how projects should handle contributions that are wholly or in part machine generated. The goal is to be as welcoming as possible of such contributions while avoiding potential pitfalls. In the mean time, I think Zuul contributors and maintainers would be well served to read this statement from the Apache Software Foundation which covers some of the potential issues and makes recommendations about some responsibilities of contributors and how to identify such contributions to make everyone aware of them: https://www.apache.org/legal/generative-tooling.html I think we should consider this a loose framework for the Zuul project to follow until the OIF makes their own recommendations and we evaluate them. -Jim

3 3

PTG April 2024 Team Signup Deadline Approaching!
by Kendall Nelson 11 Feb '24

11 Feb '24

Hello Everyone, This is your *last call *to sign up your team up for the next Project Teams Gathering (PTG)[1], which will be held from Monday, April 8 to Friday, April 12 2024! If you haven't already done so and your team is interested in participating, *you need to complete the survey[2] by February 18, 2024 at 7:00 UTC*. Thanks! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_survey

1 0

Using Github checks API
by ldenny＠redhat.com 11 Feb '24

11 Feb '24

Hi, I notice in the documentation [1] that the Github Check API is the recommendation to use. I checked some other projects for an example of this in action but was unable to find one. When you have a PR that triggers multiple jobs and for example, 1 out of 5 fails, is using the Github Check API a way to be able to only retrigger the failed job? Or is there another way to achieve this? We are currently using Github Status. [1] https://zuul-ci.org/docs/zuul/latest/drivers/github.html#attr-pipeline.%3Cr…

1 0

Persist changes to job inventory
by James E. Blair 17 Jan '24

17 Jan '24

Hi, I'm looking into a use case that involves the Nodepool k8s namespace driver. The intent with this driver is to provide a job with a namespace in which it can create its own k8s resources. It might then use those resources directly, or call a nested Ansible to interact with k8s, or add them to the Zuul job's Ansible inventory using add_host. However, that last option doesn't persist across playbooks, and Zuul jobs are typically made up of multiple playbooks which can make some kinds of work difficult (for example, necessitating running add_host at the start of each playbook). The inventory file itself is mounted in bubblewrap read-only, so even direct manipulation of the file is not an option to address persistence. I think we could change that and allow updates to the Zuul job's Ansible inventory file (either through direct manipulation, or via a custom add_host or similar module). Though I don't see any issues now, there may be security implications that I'm not immediately seeing, so I wanted to circulate the idea and get feedback before proceeding. I believe that since any playbook can already use the add_host module to affect the running of that playbook, then any concerns about access to resources using Zuul's ssh keys are moot. Most installations drop the built-in nodepool ssh keys during an early pre-run playbook, so this change would offer no ability to circumvent that. Likewise, project ssh keys are always present at the project level, regardless of which playbook is running. The main potential avenue for mischief that I can see would be the ability to substitute one host for another before a later trusted playbook (eg, a post-run playbook) is run. However, if such a playbook is depending on an *existing* inventory host being present (as opposed to executing its own add_host to, say, add a log server to the inventory), then that is already subject to the ability of users to change the nodeset on jobs just as easily as they might change the playbook of a job. I think such a situation would only be possible in a system where users have no ability to create or edit jobs yet do have the ability to edit playbooks. That seems very unlikely, and even more unlikely that anyone would consider that completely secure from abuse. I'm inclined to think that adding the ability to persist inventory changes across Zuul job playbooks is safe to do. But please let me know if you think that could cause problems. Thanks, Jim

2 1

Is the Zuul Quickstart tutorial abandoned?
by anders.klint＠qamcom.se 10 Jan '24

10 Jan '24

Hi, Way back (several years ago) I worked in a team using Zuul as one of several tools for CI. Running through the quickstart tutorial was a great way to get started and get a feeling for Zuul. I am now looking at Zuul again a potential tool in another setting and planned to run a "refresher" by working through the tutorial again. Sadly i only got part of the way (no results on changes to test1 project) and a _little_ digging shows that both zuul-tutorial-executor-1 and zuul-tutorial-gerritconfig-1 containers fails directly on start. Looking at the bugs list in storyboard, I find at https://storyboard.openstack.org/#!/story/2007325 that was created almost 4 years(!) ago with basically the same symptom(s). I remember the tutorial as a great start and intro to Zuul, but it needs to be solid. With the tutorial as one of the first links on several Zuul-ci.org pages, having it broken (for years??) is not really a great starting experience for a tool with the slogan "Stop merging broken code". Is it abandoned?

2 1

Fwd: Team Signup for April 2024 OpenInfra PTG
by Kendall Nelson 09 Jan '24

09 Jan '24

Hello Everyone, Hopefully, you have seen by now, that the next OpenInfra PTG[1] will take place April 8-12, 2024 virtually! *To sign up your team, you must complete the survey[2] by February 18 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 sign ups which will be done via the PTGBot. If you are not on IRC, please get set up[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! Information about signing up for timeslots will be sent to moderators late February after the team sign up deadline. Continue to visit openinfra.dev/ptg for updates. Registration will open soon! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_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

Project lead election
by James E. Blair 08 Jan '24

08 Jan '24

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, 2024. 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/905001

1 0

Breaking change in Ansible 2.15.7 (Ansible 8)
by James E. Blair 05 Dec '23

05 Dec '23

Hi, I just noticed (via some unit test failures in Zuul) that the Ansible project just released an update of Ansible 8 (ansible-core 2.15.7) that includes a breaking change to address CVE-2023-5764. The release summary: https://github.com/ansible/ansible/blob/stable-2.15/changelogs/CHANGELOG-v2… The porting guide: https://docs.ansible.com/ansible-core/2.15/porting_guides/porting_guide_cor… In particular one of Zuul's unit tests had an assertion with a nested template: assert: that: - zuul.project.name == '{{ (zuul | zuul_legacy_vars).ZUUL_PROJECT }} As you can see from the porting guide, the fix is to remove the nested template since the assertion is already expected to be a jinja template: assert: that: - zuul.project.name == (zuul | zuul_legacy_vars).ZUUL_PROJECT This message is just an FYI for anyone who may encounter this and be surprised by a breaking change at this point. -Jim

1 0

[Diversity] Diversity and Inclusion WG November Meeting Change and New Time
by Amy Marrich 09 Nov '23

09 Nov '23

Due to travel next week we are bumping the D&I WG meeting to November 21st at our new winter time of 15:00 UTC. As always we welcome members of all the OpenInfra projects to join us to discuss diversity and WG related topics. Amy (spotz)

1 0

Call for Writers or OpenInfra Live Participants
by Kristin Barrientos 02 Nov '23

02 Nov '23

Hi everyone, Do you have a topic that you would like to discuss on OpenInfra Live or Superuser? We’d love to hear from you. Please reach out to me via email or IRC if you have any ideas and we can talk next steps. Thanks, Kristin Barrientos IRC: @kbarrientos:matrix.org Marketing Coordinator OpenInfra Foundation

1 0

D&I WG PTG Session - Leadership Shadowing
by Amy Marrich 20 Oct '23

20 Oct '23

The D&I WG will hold a session Monday at 13:00 UTC in the Diablo room. The subject of the session is a Leadership Shadowing program we have been brainstorming[0] to help generate the next generation of Leaders in the OpenInfra Projects. As this program can be used in all projects and at all levels of leadership we are hoping all projects will join us. Thanks, Amy (

1 0

Circular dependencies refactor spec
by James E. Blair 10 Oct '23

10 Oct '23

Hi, I have posted a spec for refactoring the internal implementation of circular dependencies. This should result in few user-visible changes, but I believe it is necessary in order to make the code more maintainable and to ensure Zuul operates correctly. The spec has seen some initial positive review already. Given that, I would like to merge it next Tuesday, October 17, if it looks like we have consensus then, or of course delay it if folks identify problems or need more time to review. Here is the spec: https://review.opendev.org/895988 Thanks, Jim

1 0

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 11 Sep '23

11 Sep '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we look at the progress on responses to the Foundation-wide diversity survey. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda

1 0

OpenInfra Live Zuul Deep Dive: Volvo - Sept. 7 at 1400 UTC
by Kristin Barrientos 06 Sep '23

06 Sep '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by the Zuul community! Episode: In this episode, a panel of Zuul operators invites special guests to talk about their deployment and discuss their operations. For this episode, our guests will be Johannes Foufas and Moiz Ahmed, from Volvo. Date and time: Sept. 7, 2023 at 9:00 AM CST (14:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=ZjY61I-8mpQ LinkedIn: https://www.linkedin.com/events/7094388406977265664/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Johannes Foufas, Moiz Ahmed, Clark Boylan, James Blair, Jeremy Stanley and Kristin Barrientos Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

Cyber Resilience Act: What Now? Aug 24 at 9 AM (CST) / 14:00 UTC
by Kristin Barrientos 23 Aug '23

23 Aug '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by open source community leaders. Episode: On this episode of OpenInfra Live, we will discuss the EU Cyber Resilience Act's impact on open source software. The OpenInfra Foundation and many other open source organizations have expressed concerns about the proposed text, urging the European lawmakers to take into account the specificity of open source open collaboration in the legislation. Join and engage live with our expert panelists as they discuss the current state of the proposal, its potential consequences, what we can still do about it, and what other pieces of upcoming legislation we should watch for. Date and time: Aug 24, 2023 at 9:00 AM CST (14:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=u6Dh0nXivqM LinkedIn: https://www.linkedin.com/events/7095407763538763776/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Thierry Carrez, Allison Randal, Mike Milinkovich, Ciarán O'Riordan Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

Fwd: vPTG October 2023 Team Signup Deadline Approaching!
by Kendall Nelson 17 Aug '23

17 Aug '23

Hello Everyone, Sign up your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 23 to Friday, October 27 2023! If you haven't already done so and your team is interested in participating, you need to complete the survey[1] by August 20, 2023 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2023_ptg_team_signup [2] PTG Registration: http://ptg2023.openinfra.dev/

1 1

[zuul-jobs] Replacing the haskell ensure-cabal and ensure-stack with ghcup
by Tristan Cacqueray 11 Aug '23

11 Aug '23

Dear Zuulers, I propose to use ghcup to ensure the haskell toolchain with this change: https://review.opendev.org/c/zuul/zuul-jobs/+/847111 This should be transparent for job users, however playbooks using the ensure-cabal or ensure-stack roles directly needs to be modified to use the common ensure-ghc role. Please reply to this mail and/or the cited change if you have objections. With regards, -Tristan

1 0

Issue with websocket authentication for builds log streaming
by Andrei Dmitriev (Nokia) 11 Aug '23

11 Aug '23

Hi Zuul community, At Nokia we are using internal fork of Zuul v2 in production, but we want to update to newer version of Zuul to have all new features and flexibility it gives. So, we are testing it and closing feature parity with fork of Zuul v2 for that. We have a security requirement to allow to reading builds only for developers, working on projects at configured tenant. So, we tested read access authentication feature and found out that log streaming is not working for running builds when authentication is enabled for tenant. After debugging we found that log streaming is using WebSocket protocol, but authentication mechanism is using Authentication header. But WebSocket protocol doesn’t support this header, so server is not receiving it and not allowing WebSocket connection. As a fast solution for that we implemented a fix that allows WebSocket connection but doing it still in a secure way. https://review.opendev.org/c/zuul/zuul/+/890780 Please check, we will be glad if this or similar solution will be accepted in community. Thanks, Andrei Dmitriev CI Engineer at Nokia

1 0

Exploring the Intersection of AI and Open Source: Aug. 10 at 15 UTC
by Kristin Barrientos 09 Aug '23

09 Aug '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by open source community leaders. Episode: If you stand at the intersection of AI and open source you’ll find a very active discussion around how each concept can apply to the other but you’ll find few definitive answers. This panel of open source community leaders will discuss the current state of AI & open source, the collaborative efforts underway to improve global understanding of this emerging use case and how open source community members can participate in solving today’s unanswered questions. Date and time: Aug 10, 2023 at 10:00 CST (15:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=LLujjvEIbPk LinkedIn: https://www.linkedin.com/events/7094342351971598337/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Mark Collier, Pamela Chestek, Stefano Maffulli, Armstrong Foundjem, Stephen O'Grady Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

Fwd: Call for Mentors & Projects - Boston University Students
by Kendall Nelson 08 Aug '23

08 Aug '23

Hello Everyone! As some of you might know, we have had a working relationship with Boston University once a year where students actively participate in our OpenInfra project communities. The semester in which the Fundamentals of Cloud Computing (the course where we collaborate with them)( is approaching. September 5 is when the course begins and it runs until December 21. The course is a senior/graduate-level class that includes a semester-long capstone-like project, with the projects being proposed and supervised by an industry mentor. The projects are completed in teams of 5-7 students, who are expected to spend 5-8 hours per week on the project over the 13-week term, with presentations to the class every two weeks to evaluate their progress. *So! If you know of a project you would like to propose, please let me know ASAP! The professor would like to have the finalized list of projects to offer students by the first week in September. * Let me know if you have any other questions! -Kendall Nelson

1 0

Fwd: vPTG October 2023 Team Signup Kickoff
by Kendall Nelson 23 Jul '23

23 Jul '23

Hi Everyone, Hopefully, you have seen by now that the next OpenInfra vPTG[1] which will take place October 23-27, 2023 virtually and registration is open[2]! *To sign up your team, you must complete the survey[3] by August 20th 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 sign ups 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! Information about signing up for time will be sent to moderators late August after the interest survey deadline on August 20. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] PTG Registration: http://ptg2023.openinfra.dev/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2023_ptg_team_signup [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

Zuul Python version support
by James E. Blair 19 Jul '23

19 Jul '23

Hi, Currently Zuul supports python 3.8 through 3.11 (with those two versions specifically tested). We're about to upgrade Ansible which requires at least version 3.9. But there are some performance improvements in 3.10. And finally, we build our container images on 3.11. I suspect that many folks are running container images at this point, so this seems like a good opportunity to simplify our support and testing matrix and declare support for a single version of Python: 3.11 -- the one we build our images with. If we do this, I anticipate that we may from time to time expand our support and testing, for example, to accommodate Python version upgrades (perhaps we will test 3.12 for a time before upgrading the container image to it). But in general, we might limit our expectations to a narrow range, just enough to cover our need to produce a working image. Please let me know if you object or if there's something else we should consider. Thanks, Jim

3 2

[zuul-jobs] Dropping upstream Ubuntu Bionic testing and support
by Radosław Piliszek 19 Jul '23

19 Jul '23

Dear Zuulers, Ubuntu Bionic is out of standard (aka free) support since June 2023. This is effectively EOL for the general community. I propose to remove upstream testing [1] and support [2] for Bionic to avoid the expected upcoming breakage, already observed with minikube [3]. Please reply to this mail and/or the cited changes [1] [2] if you have objections and are willing to help with remaining possible Bionic support. [1] https://review.opendev.org/c/zuul/zuul-jobs/+/888947 [2] https://review.opendev.org/c/zuul/zuul-jobs/+/888948 [3] https://review.opendev.org/c/zuul/zuul-jobs/+/885988 Kind regards, Radosław Piliszek -yoctozepto

1 0

Fwd: vPTG October 2023 Dates & Registration Kickoff
by Kendall Nelson 10 Jul '23

10 Jul '23

Hello Everyone! The next PTG[1] will take place October 23-27, 2023 virtually! Registration is now open[2] and free for all to attend. Keep an eye out in the coming weeks because I will send along the team sign up to collect groups interested in participating. Thanks! -Kendall Nelson(diablo_rojo) [1] https://openinfra.dev/ptg/ [2] http://ptg2023.openinfra.dev/

1 0

To drop support for Helm v2 or not to drop?
by Radosław Piliszek 10 Jun '23

10 Jun '23

Hello Zuulers, I have identified a minor bug in the way that the current helm-template role handles Helm v3 naming of releases: https://storyboard.openstack.org/#!/story/2010783 I would like to propose a fix but I am wondering whether we should strive to keep Helm v2 compatibility at this point as it's very outdated and not supporting modern Kubernetes either. If we can drop Helm v2 support then it makes it really simple to fix and avoids version parsing. Kind regards, Radek -yoctozepto

1 1

Zuul's job requires-provides confusing behaviour
by Radosław Piliszek 07 Jun '23

07 Jun '23

Dear Zuulers, I am confused about the behaviour of requires-provides and wonder whether this is on purpose (and then why?) or by accident. I noticed that the job which *requires* something from another job that *provides* it does **not** wait for this other job if it's run **on the same change** (i.e., in the same buildset), only on earlier changes/buildsets. While this works as explained in the docs [1], I find it confusing. For example, I have a Dockerfile and Helm chart in the same repo and I would like to check how changes to the image affect the chart deployment. Currently, only subsequent changes would consume the result. I.e., by this design, I am forced to artificially split the repo into a separate one for chart and a separate one for the image. [1] https://zuul-ci.org/docs/zuul/latest/config/job.html Kind regards, Radek -yoctozepto

2 5

RDO Ice Cream Social at OpenInfra Summit
by Amy Marrich 02 Jun '23

02 Jun '23

Join members of the community for ice cream after the Marketplace Mixer on Wednesday at Soft Peaks in Gastown! Soft Peaks is known for using organic milk and their unique topics! For those with dairy related dietary needs who register we will have an alternative for you so don't feel left out! https://eventyay.com/events/231a963f

1 1

Informal Summit Gathering for Zuul and OpenDev
by Clark Boylan 30 May '23

30 May '23

Hello everyone, I'd like to take advantage of the Summit to get together with those of us work on Zuul and OpenDev if possible. I think less formal is probably a good thing so that people can come and go as they are able. The beer garden in Berlin worked really well for this. Stanley Park Brewing [0] appears to be similar with outdoor patio seating in Stanley Park. This location is just under 3km from the convention center which makes it a long walk or a short ride in $vehicle. Looking at a schedule I think Thursday evening after the Summit is going to be the best time for most people. Let's meet there at 6pm on Thursday (June 15) and hang out. If you intend on being there can you throw your name onto this etherpad, https://etherpad.opendev.org/zuul-opendev-yvr-2023, so that we can get a rough idea for how large of a group we'll be? I don't expect we'll need reservations and instead try to grab one or more of their outdoor tables. You may want to bring sunscreen. If the weather turns out to be terrible I'll update this thread with any change of plans. [0] https://www.stanleyparkbrewing.com/ Thanks, Clark

1 0

apply-helm-charts + buildset registry
by Radosław Piliszek 26 May '23

26 May '23

Hello Zuulers, I am wondering if any of you has any experience with using `apply-helm-charts` job with a buildset registry. What I am looking for is testing the deployment of possibly-rebuilt images on Kubernetes with Helm chart(s), i.e., the apply-helm-charts would need to access the buildset registry and the chart(s) would need to point to the possibly-rebuilt versions of images from the buildset registry. So far, I have established that the `apply-helm-charts` job is *not* doing this automagically (sadly!) but maybe I am missing something. Kind regards, Radek -yoctozepto

1 0

New approach for project update presentations
by Clark Boylan 22 May '23

22 May '23

Hi, I'm reaching out to you about the video recordings that the OpenInfra Foundation has been collecting to capture project updates from each OpenInfra community. These videos were initially collected leading up to the OpenInfra Summits to showcase what each project has accomplished in the past year/release. This year we are implementing a change to the cadence of collecting this video content, to better fit with the communities' timeline, milestones and achievements. It will also help us better promote the new content, without it getting lost among the news and buzz around the OpenInfra Summit. Moving forward, the community will need to make decisions about items, such as the cadence and format of recording the project updates. Cadence: There are various options to pick from. The community can define a stable cadence, stick to bigger milestones, like major releases, project anniversaries, and more. Format: The community can produce pre-recorded content, which can include slide materials, and share that with us. If there is enough content and volunteers, the community also has the option to talk about the latest project news and updates during an OpenInfra Live episode. We will post all recordings on the OpenInfra Foundation YouTube channel and promote them in relevant social media channels. Timeline: The new process will start after this year's OpenInfra Summit, which will happen on June 13-15 in Vancouver, Canada. After the event, I will reach out to help the community decide on the above items and take next steps in the process. Please let me know if you have any questions in the meantime. Thanks, Clark on behalf of the OpenInfra Foundation Staff

1 0

Fwd: Extending the Forum
by Kendall Nelson 11 May '23

11 May '23

Hello Everyone, We received feedback that critical Forum conversations were not able to make the schedule due to the intentional work on our part to avoid PTG / Forum overlap which ended up restricting the number of Forum discussion proposals we were able to accept. To mitigate this, we have opened up the Forum room for a third day. We have created a form to collect critical Forum proposals. We will leave the form open for one week to give all timezones fair representation. The deadline to submit a proposal for a forum discussion is Thursday May, 18th at 7:00 UTC. Shortly after, the OpenInfra Foundation will make final decisions and program the Forum on Thursday. -Kendall Nelson [1] https://openinfrafoundation.formstack.com/forms/forum_expansion

1 0

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 08 May '23

08 May '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we review the Foundation-wide diversity survey questions for release at Summit. Thanks, Amy (spotz)

1 0

New container image location
by James E. Blair 27 Apr '23

27 Apr '23

Hi, The Zuul project has changed publishing locations for the container images it builds. The new location is "quay.io/zuul-ci". So if you were previously specifying, for example, the zuul-scheduler image as: zuul/zuul-scheduler:latest or docker.io/zuul/zuul-scheduler:latest You should instead use: quay.io/zuul-ci/zuul-scheduler:latest Do note that both the host and the organization part of the reference has changed. It is unfortunate that we were unable to use our preferred organization name, but it was not available. We are not changing the name of the project; it's still Zuul. All of the existing release tags have been copied over, so if you are running a release, you may switch that now as well. We will no longer be publishing any new images to Docker Hub. Existing images will remain in place until May 25, at which point they will be deleted. Please update your references as soon as possible, and certainly before that date. Thanks, James Blair on behalf of the Zuul team

1 0

Fwd: Reminder! In Person PTG 2023 Team Signup Deadline
by Kendall Nelson 31 Mar '23

31 Mar '23

Hello Everyone, This is the last call to sign your team up for the *in-person* Project Teams Gathering (PTG) happening in Vancouver at the OpenInfra Summit! If you haven't already done so and your team is interested in participating, please complete the survey[1] by April 2nd, 2023 at 7:00 UTC. Registration for the PTG is included as a part of registration for the OpenInfra Summit in Vancouver. Prices increase May 5th so register soon! Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/june2023_ptg_survey [2] Summit Registration: https://vancouver2023.openinfra.dev/ <https://vancouver2023.openinfra.dev/>

1 0

[Diversity] Diversity and Inclusion at the PTG
by Amy Marrich 24 Mar '23

24 Mar '23

I have blocked off three hours on Monday for the D&I WG to discuss the upcoming Diversity Survey(14:00 UTC) and then ongoing changes to the Code of Conduct(15:00- 16:00 UTC) and then the Summit if there is time. The agenda can be found here[0]. All projects are encouraged to attend these sessions as the WG is at the Foundation level. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/march2023-ptg-diversity

1 0

Container image location
by James E. Blair 22 Mar '23

22 Mar '23

Hi, Recently Docker, Inc. announced a policy change that affects the images currently hosted at docker.io/zuul. Some Zuul and OpenDev maintainers have been working together on a plan for how to proceed, and I believe we have a good one. For a summary of the situation, please see this etherpad: https://etherpad.opendev.org/p/MJTzrNTDMFyEUxi1ReSo We also had a meeting in IRC where we discussed options: https://meetings.opendev.org/meetings/infra/2023/infra.2023-03-16-19.02.log… The outcome of all of this is that I believe we should: 1) Move our images from Docker Hub to quay.io 2) Set up a static redirect server to redirect image pull requests to the new location Quay.io seems much more interested in hosting builds of open source projects than Docker Hub. By setting up a redirect server, we can have stable references for our images in case we move in the future (and it means that the organization name on quay.io becomes an implementation detail that isn't important to end users). To this end, I propose that we: 1) Set up registry.zuul-ci.org to redirect to our current images on Docker Hub. Image names would look like: registry.zuul-ci.org/zuul-scheduler:8.2.0 2) Once that is in place, announce that everyone using container images should update their references to those names immediately. 3) Switch our build jobs to publish images to quay.io. Work on the Ansible roles needed to accomplish this is currently in progress. 4) Switch registry.zuul-ci.org to redirect to quay.io instead of Docker Hub. 5) Around the first week of April, delete all of the images from Docker Hub. This is about a week before we will lose access to the "zuul" organization on Docker Hub. This will intentionally break any users who still have references to Docker Hub. Because we are going to lose access to the org, this is our only opportunity to exert any control over these images. If we don't delete them, then anyone not paying attention may forever have stale references to "zuul/zuul-scheduler:latest" and not realize it is not being updated anymore. If anything goes wrong with this process, we will still have an opportunity to roll back to Docker Hub, purchase continued access to the organization, and regroup while we figure out how to proceed. Due to the abbreviated timeline imposed, most of this work is already in progress and proceeding quickly based on both recent discussions and discussions we've had as a community in prior years. I think the general course is probably set at this point, but questions or feedback are welcome. Assuming no showstoppers come up, I expect steps #1 and #2 within the next few days. Thanks, Jim

1 1

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 13 Mar '23

13 Mar '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we look at the Code of Conduct, and continue working on planning for the OpenInfra Summit as well as Foundation-wide diversity surveys. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda

1 0

Zuul Leadership and Open Infra Foundation Board Meeting
by Clark Boylan 01 Mar '23

01 Mar '23

Hello everyone, I've managed to schedule another meeting between the Zuul Leadership and the Open Infra Foundation Board. We will meet March 1, 2023 at 17:00 UTC. I've put location details and some rough ideas for an agenda in https://etherpad.opendev.org/p/zuul-board-mtg-march-2023. Please feel free to update the rough agenda with topic ideas too. Everyone from our community is welcome to join, this isn't limited to the Zuul maintainers from our side. Hope to see you there. Apologies for getting this out late. Travel ended up being far more involved than I anticipated (I'm out of practice). Clark

2 4

Fwd: June 2023 PTG Team Signup Kickoff
by Kendall Nelson 01 Mar '23

01 Mar '23

Hello Everyone, As you may have seen, we are hosting an abbreviated PTG in conjunction with the Vancouver OpenInfra Summit[0]! To sign your team up, you must complete the survey[1] by April 2nd at 7:00 UTC. We NEED accurate contact information 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[2] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[3] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators shortly after the team signup deadline. Registration is open[4] and prices will increase May 5th! Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [0] OpenInfra Summit Site: [1] Team Survey: https://openinfra.dev/summit/vancouver-2023 https://openinfrafoundation.formstack.com/forms/june2023_ptg_survey [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst [4] OpenInfra Summit Registration: https://vancouver2023.openinfra.dev/

1 0

Docker-in-docker style workloads on Openshift/K8s
by zuul＠anonameow.com 24 Feb '23

24 Feb '23

Hi, We are looking into having docker-in-docker style workloads using the Openshift pods driver and noticed there is some support for that today using the privileged flag[1]. I assume are there some risks in exposing a privileged container towards the end-user, or is there some protection already in place? One alternative I see would be to have a docker-in-docker sidecar container (privileged) that the "primary" container (non-privileged) accesses via DOCKER_HOST=tcp://localhost:2375 for example. Such support doesn't exist today, but would be happy to contribute if that idea sounds good. 1. https://review.opendev.org/c/zuul/nodepool/+/871777

1 0

Fwd: PTG March 2023 Teams List
by Kendall Nelson 21 Feb '23

21 Feb '23

Hello Everyone! The March 2023 Project Teams List is official! *Projects + Teams* - OpenInfra Foundation Teams - Diversity and Inclusion WG - Edge Computing Group - Environmental Sustainability Working Group - Interop WG - StarlingX - OpenStack Teams - Service Teams - Barbican - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Kuryr - Magnum - Manila - Neutron - Nova - Octavia - OpenaStackSDK/CLI/Ansible-Collections - OpenStack-Ansible - OpenStackCharms - QA - Tacker - Other Teams - Scientific SIG - PublicCloud SIG OpenStack - Security SIG - OpenStack Technical Committee - RBAC - I18n SIG If your team was planning to meet and isn’t on this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign your team up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — *its FREE!* As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

The OpenInfra Summit Schedule is Live!
by Helena Spease 15 Feb '23

15 Feb '23

Hello everyone, I am really excited to let you know the Schedule [1] for the OpenInfra Summit 2023 is available! The schedule features keynotes and sessions from users like Bloomberg, LINE, Alibaba Cloud, Samsung and Volvo. The event will be held June 13-15, 2023, at the Vancouver Convention Centre overlooking Vancouver Harbor. Other notable speakers include Ant Group, the Australian Research Data Commons (ARDC), China Mobile, SAP, and Viettel, the largest public and private cloud infrastructure provider in Vietnam. Check out these Zuul session you can expect at the OpenInfra Summit! Using AWS and Azure with Zuul by Johannes Foufas, Moiz Ahmad Testing Complete System Deployments with Zuul by James Blair Debugging Zuul jobs – now easier than ever, with Autoholds feature by Szymon Datko, Ignacio Horcada Bernal Deploying a production Kubernetes platform on OpenStack Magnum with Zuul: An Open edX Case Study by Florian Haas, Namrata Sitlani The OpenInfra Summit [2] will be a limited-capacity, sellout event. Early bird sales for the OpenInfra Summit end February 15, 2023 at 11:59 PM PT. Register now [3] to save on your ticket and join us in Vancouver, June 13-15, 2023! The price increase will also apply to contributor discount codes, so if you received a contributor discount code last week, be sure to use it before February 15! Looking for other resources for the OpenInfra Summit? Sponsorship, Travel Support, visa requests, info on the PTG at the OpenInfra Summit, and Forum session details can be found at openinfra.dev/summit <http://openinfra.dev/summit>! Cheers, Helena [1] http://openinfra.dev/summit-schedule <http://openinfra.dev/summit-schedule> [2] http://openinfra.dev/summit <http://openinfra.dev/summit> [3] https://openinfra.dev/summit/registration <https://openinfra.dev/summit/registration> Cheers, Helena helena(a)openinfra.dev Marketing & Community Associate The OpenInfra Foundation

1 1

Fwd: Virtual PTG March 2023 Team Signup Deadline - LAST CALL!
by Kendall Nelson 13 Feb '23

13 Feb '23

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, March 27th to Friday, March 31st 2023! NOTE: Since we have had the feedback that the Europe+Africa/Americas timeslot is overbooked, we will be extending it beyond the ‘normal’ size of 4 hour blocks to 5 hour blocks. If you haven't already done so and your team is interested in participating, please complete the survey[1] by February 19th, 2023 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

OpenInfra Summit Forum Selection Committee Call for Volunteers
by Kendall Nelson 02 Feb '23

02 Feb '23

Hello Everyone! The Forum at the OpenInfra Summit Vancouver is coming up! We would love 1 volunteer from Zuul for the Forum Selection Committee. Ideally, the volunteer would: - already be serving in some capacity in a governance role for your project - not be planning to submit to the Forum CFP or be willing to abstain from voting on your proposals For information on the OpenInfra Summit in Vancouver: https://openinfra.dev/summit/vancouver-2023/ For more information on the Forum, please see: https://openinfra.dev/summit/vancouver-2023/forum/ Please reach out to me, knelson@open <http://goog_1840023357/>infra.dev, or reply on this thread if you're interested. Volunteers should respond on or before March 5th, 2023 @ 7:00 UTC. This role does not require you to travel to the OpenInfra Summit, but can get you a discounted ticket if you choose to volunteer and then attend (we would love to have you there!). Thanks! Kendall Nelson

1 0

Re: Environment variables passed to a tox job from encrypted secrets leak into the build log, how do I suppress this?
by Florian Haas 01 Feb '23

01 Feb '23

On 26/01/2023 19:26, Clark Boylan wrote: >> I have been unable to pinpoint exactly where and how that specific >> log is generated by the job. If somebody could point me to it, and >> let me know what overrides I need to add to the job to suppress >> this log altogether, or to remove the env variables from it, or >> better still configure it to replace the values of env variables >> matching a glob or regex with "<redacted>" or "*********" or some >> such, I'd be most grateful. > > Tox itself produces these log files and writes them to > .tox/$envname/log then the fetch-tox-output role [0] collects them > for you. Looking at this role there doesn't appear to be a flag to > disable it, just flags to modify its behavior. It also doesn't look > like there is a way to stop Tox from logging these files [1]. You > might just want to drop the fetch-tox-output role from your jobs and > not copy the files. Or maybe you can get away with a job task that > truncates the files before they are copied. Thanks for the pointer; that helped a lot. It turns out that {work_dir}/{env_name}/log did already exist in tox 3. However, the logs it contained did *not* dump all the environment variables, and so those never ended up in the Zuul web interface. As of tox 4, they do.[1] This might have security implications for anyone that runs tox from Zuul, hasn't locked down their Zuul web interface, uses sensitive information that is passed into a tox environment via environment variables, and just upgraded from tox 3 to tox 4. They might not be aware that their secrets are now accessible via the web interface, when with tox 3 they were not. Since the fetch-tox-output role looks explicitly in {work_dir}/{env_name}/log to find those logs, an applicable workaround to make those logs not show up in the Zuul build log (though, of course, they still get generated) would be to put envlogdir = {toxinidir}/dummylog into the testenv definition in tox.ini (for any testenvs that might pass sensitive information to tox via environment variables). Then, Zuul's fetch-tox-output role can't find anything in the directory it looks into, and it can only produce the job-output.txt log which — as far as I've been able to tell — does not contain a dump of environment variables. tox will generate envlogdir if it does not exist. It it NOT advisable to use some random existing directory; tox 4 will remove all files contained therein at the start of the run (tox 3 didn't do *that,* either). Again, thanks for the pointer! Cheers, Florian [1] More precisely, I see the new log format when testing with tox 4.4.2; I see the old one with 3.28.0. So the format would have changed at some point between those releases, though I haven't looked into exactly when.

2 1

Environment variables passed to a tox job from encrypted secrets leak into the build log, how do I suppress this?
by Florian Haas 26 Jan '23

26 Jan '23

Hi everyone, first post to list, though I know a few folks who are subscribed personally — to those of you, no long time no see! Here's my issue: I want to keep Zuul from leaking secrets into the build logs, and in this specific instance I don't know where to look for the fix. In more detail: I am running a tox job from Zuul that uploads some generated files to a Ceph radosgw service via its S3 API. This is my "upload" testenv as defined in my tox.ini: [testenv:upload] deps = awscli passenv = AWS_* setenv = file|build.env commands = aws --endpoint-url={env:S3_ENDPOINT} \ s3 sync \ {toxinidir}/build/ \ s3://{env:S3_BUCKET}/ I set S3_ENDPOINT and S3_BUCKET in my build.env file, and I want to pass AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from the environment through to the aws s3 sync command, hence the passenv entry. Since I would prefer to not have to maintain a separate job definition in a config project for this, I have the following secret and job definition in my repo's .zuul.yaml: - secret: name: tox_environment_secret data: AWS_ACCESS_KEY_ID: !encrypted/pkcs1-oaep - # encrypted secret redacted AWS_SECRET_ACCESS_KEY: !encrypted/pkcs1-oaep - # encrypted secret redacted - job: name: tox-upload parent: tox secrets: - name: tox_environment secret: tox_environment_secret pass-to-parent: true vars: tox_envlist: "upload" As described in https://zuul-ci.org/docs/zuul/latest/config/job.html#attr-job.secrets, this results in the environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY being passed into the tox run managed by the tox-upload job (or rather by its parent, the upstream tox job), as environment variables, with their values set to the decrypted secrets. Now, when I check the build log at log/job-output.txt (relative to my build URL), I see no trace of the secrets. So far, so good. But there is another job log at log/tox/upload/1-commands[0].log, which contains *all* the environment variables passed into the tox job, including the decrypted values for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY: name: upload run_id: commands[0] env LANG: C.UTF-8 env AWS_ACCESS_KEY_ID: <redacted> env AWS_SECRET_ACCESS_KEY: <redacted> [etc.] I'd obviously prefer for those to not leak into the build logs. I have been unable to pinpoint exactly where and how that specific log is generated by the job. If somebody could point me to it, and let me know what overrides I need to add to the job to suppress this log altogether, or to remove the env variables from it, or better still configure it to replace the values of env variables matching a glob or regex with "<redacted>" or "*********" or some such, I'd be most grateful. Thanks! Cheers, Florian

2 1

Feedback on Changes to Supported Python Version in Zuul
by Clark Boylan 24 Jan '23

24 Jan '23

Hello everyone, Eventually (hopefully soon), Zuul will add Ansible 7 (Ansible Core 2.14 support). According to the Ansible docs [0] this new version of Ansible drops support for Python 3.8. Currently Zuul is tested on Python 3.8 and 3.11 with the intent of supporting Zuul across Python 3.8, 3.9, 3.10, and 3.11. Unfortunately, Ansible's dropping of Python 3.8 support means that Zuul will also need to drop support for Python 3.8 when Ansible 7 support is added to Zuul. On top of that, Zuul test suite runs in CI are approximately 30 minutes quicker running on python 3.10+ than on older Pythons. Unfortunately, I don't have the best data to illustrate this since we currently only run jobs for 3.8 and 3.11, but the major performance improvements appear to have shown up with 3.10. You can get a sense for this difference comparing the 3.8 runtimes [1] to the 3.11 runtimes [2]. As a developer I selfishly think that this improvement is worth considering, and we might also take this opportunity to drop Python 3.9 support (and testing). For anyone running on Python 3.8 today now is probably a good time to start looking at updated platforms. Is there anyone out there running Zuul on Python 3.9 today? If you are running Zuul on Python < 3.10 we'd love to hear from you to ensure we understand the potential impact of changes like this. [0] https://docs.ansible.com/ansible/latest/installation_guide/intro_installati… [1] https://zuul.opendev.org/t/zuul/builds?job_name=zuul-nox-py38&pipeline=gate… [2] https://zuul.opendev.org/t/zuul/builds?job_name=zuul-nox-py311&pipeline=gat… Clark

5 10

The OpenInfra Summit 2023 CFP is closing soon!
by Helena Spease 10 Jan '23

10 Jan '23

Hi Everyone! The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is closing in just a few days[1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. The CFP closes January 10, 2023, at 11:59 p.m. PT. See what that is in your timezone [3] We are also now accepting submissions for Forum sessions [4]! Looking for other resources? Find information on registration, sponsorships, travel support and visa requests at https://openinfra.dev/summit/ <https://openinfra.dev/summit/vancouver-2023> If you have any questions feel free to reach out :) Cheers, Helena [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations <https://cfp.openinfra.dev/app/vancouver-2023/19/presentations> [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/> [3] https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Su… <https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Su…> [4] https://cfp.openinfra.dev/app/vancouver-2023/20/ <https://cfp.openinfra.dev/app/vancouver-2023/20/>

1 1

Future of the ensure-kubernetes role
by Ian Wienand 09 Jan '23

09 Jan '23

Hello, The ensure-kubernetes role in zuul-jobs sets up a k8s environment on the test node so we can do some API testing against, and run, small containers. I think it's fair to say this isn't aimed at being a production installation, but rather the minimal parts of k8s that basic functional testing can validate against. Currently the ensure-kubernetes role deploys k8s via minikube bionic/focal/jammy with a choice of two backends; cri-o and docker. I worry about this whole toolchain. It took some effort to get it working on Jammy, and it's not very elegant. Some of the problems - kubectl installs from a repo called "https://apt.kubernetes.io/ kubernetes-xenial main" [1]. It seems to get updates; and maybe it refers to the lowest version. I don't know, but it's not reassuring. - minikube isn't packaged and we download a blob directly. This is probably neither here-nor-there; but it is less appealing than using something from a distro. - everything is written to use the minikube "none" driver, which avoids having to worry about nesting VM's. - minikube with the "none" driver only supports a CRI compatible backend and has a lot of caveats [2] - cri-o is CRI compatible, but is not upstream packaged for Ubuntu. We rely on packaging of the tools from the SUSE kubic program, which has now been retired and is in a sort of best-effort community maintenance [3]. What prompted me looking at this was an expired GPG key in this project which broke testing. This was fixed, of course bugs happen to everyone. But we are 100% dependent on this repo (I could not get the docker back-end to work without some of the runtime tools from it, so it is not completely independent). - docker is packaged externally, but widely used (by OpenDev in production even). But to use it with minikube, we need to run a CRI api -> dockerd shim that we download as a binary blob [4] - With all these disparate parts, we get conflicts. For example, bits of podman are packaged on Jammy, so now "containernetworking-plugins" comes from the distro. Which of course installs things in a different location to the kubic versions. Which means we have to monkey-patch over the top of patching that minikube does [5]. - I don't think we actually got any of this working for Focal; we just had jobs on bionic and skipped straight to jammy [6]. So we're not keeping up. I think that's probably evidence enough that setting up a test k8s environment with minikube + <cri-o|docker> on Ubuntu is not very compelling. I've personally spent much more time debugging all this than anything to do with actual k8s support in tools. minikube seems to have a docker driver now [7], which I'm sure did not exist when any of this was written and might suit us as it says it does not need nested virt. However, I would propose that we are not making good use of our limited resources by continuing along this path. Ubuntu's preferred method for deploying k8s is via microk8s which they package as snap images [8]. I am not a huge fan of snap images for distribution, but I am a fan of not trying to maintain a bunch of parts that don't really want to work together. I have written changes in https://review.opendev.org/q/topic:ensure-kubernetes-microk8s to setup microk8s in ensure-kubernetes, and to make it so when using use-buildset-repository with microk8s, k8s will pull through the buildset repository. I have converted the nodepool job to use this. What I would propose is that we deprecate the other paths in ensure-kubernetes and focus our efforts on microk8s on jammy (and future distros going forward). This role is not heavily used, I don't see our time well spent supporting multiple installation methods across multiple releases (and it's never been cross-distro -- which I also think is fine). I see this having a greater role in the future as part of the work such as the nodepool->zuul conversion, where it may get a lot more exposure. Thoughts are welcome :) -i [1] https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/insta… [2] https://minikube.sigs.k8s.io/docs/drivers/none/ [3] https://kubic.opensuse.org/blog/2022-06-10-kubic-retired/ [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-kubernete… [5] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-kubernete… [6] https://review.opendev.org/c/zuul/zuul-operator/+/863948/3/.zuul.yaml [7] https://minikube.sigs.k8s.io/docs/drivers/docker/ [8] https://ubuntu.com/tutorials/install-a-local-kubernetes-with-microk8s#1-ove…

2 1

Project lead election
by James E. Blair 09 Jan '23

09 Jan '23

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 16, 2023. 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/869609

1 0

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 09 Jan '23

09 Jan '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we continue working on planning for the OpenInfra Summit as well as Foundation-wide surveys. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda

1 0

Fwd: 2023 PTGs + Virtual Team Signup
by Kendall Nelson 03 Jan '23

03 Jan '23

Hello Everyone! The next PTG on the calendar will be our usual virtual format and it will take place March 27 -31. The project signup survey is already ready to go! If your team is interested in participating, sign them up here[1]! Registration is also open now[2] We have also heard many requests from the contributor community to bring back in person events and also heard that with global travel reduction, it would be better travel wise for the community at large to combine it with the OpenInfra Summit[3]. So, an in-person PTG will take place Wednesday and Thursday! June 14 -15th. OpenInfra Summit registration will be required to participate, and contributor pricing and travel support[4] will be available. We will also be planning another virtual PTG in the latter half of the year. The exact date is still being finalized. This will give you three opportunities to get your team together in 2023: two virtual and one in-person. - Virtual: March 27-31 - In- Person: June 14-15 collocated with the OpenInfra Summit - Virtual: TBD, but second half of the year As any project in our community, you are free to take advantage of all or some of the PTGs this coming year. I, for one, hope to see you and your project at as many as make sense for your team! To make sure we are as inclusive as possible I will continue to encourage team moderators to write summaries of their discussions to gather and promote after the events as well. Stay tuned for more info as we get closer, but the team signup survey[1] has opened for the first virtual PTG and is ready for you! -Kendall (diablo_rojo) [1] https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] https://openinfra-ptg.eventbrite.com [3]https://openinfra.dev/summit/vancouver-2023 [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp

1 1

2022 Zuul Foundation Annual Report
by Clark Boylan 19 Dec '22

19 Dec '22

Hello, At the end of every year the Foundation puts together an Annual Report. Included in this report is a section for each of the Foundation's top level projects. I have been asked to ensure the Zuul portion of the report gets written. I have started with a draft here: https://etherpad.opendev.org/p/2022-zuul-annual-report and would love your input/feedback/content if you have time to help. I want to make sure that this document reflects the Zuul project as a whole and not just my personal involvement with Zuul. In the etherpad I've put the 2022 report draft at the top, then included ideas for content below that as well as the 2021 report for some historical context. Please feel free to add ideas to the content list or edit the report text directly. Clark

1 0

Mailing list update and Zuul user survey
by James E. Blair 06 Dec '22

06 Dec '22

Hi! The OpenDev team has upgraded the software running on lists.zuul-ci.org. I'm sending this email partly to let folks know about that if they aren't aware. There's a new interface for managing options and interacting with the list, and if you create an account, that account will work for all of the OpenDev lists (once the rest are moved over). You can read more about it here: https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/… Here's a link to the site: https://lists.zuul-ci.org/ I'm also sending this email just to make sure everything is still working. ;) Finally, this seems like a great time to remind folks about the Zuul user survey -- please fill it out if you haven't already! https://www.surveymonkey.com/r/K2B2MWL Thanks, Jim

1 0

Video about Zuul/Gerrit simultaneous dependencies
by James E. Blair 28 Nov '22

28 Nov '22

Hi, I just wanted to share a short video I made showing some of the new features in Zuul that work with Gerrit's submitWholeTopic setting to support testing and merging simultaneous dependencies. Take a look if you haven't seen the new features. https://www.youtube.com/watch?v=B64RbNwkIa4 -Jim

1 0

Zuul German becomes unresponsive
by Mithun Mistry 03 Nov '22

03 Nov '22

Hi Team, We at Western digital IT team , is using Zuul version R4.1.0 . We have come across an issue whereby the gearman becomes unresponsive without any issues with scheduler service . We are using default gearman that comes bundles with zuul scheduler. We have scheduler and executer/merger services running on separate vms. We have come across the issue twice in 3 month’s time. Restarting zuul-scheduler service fixes the issue and zuul works as usual. Please let us know if it is a known issue and if you have any solution for the same. We will be happy to provide additional information if required. Gearman log : 2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146fb860 type: UNKNOWN> 2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146d87b8 type: UNKNOWN> 2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146fb860 type: UNKNOWN> 2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146d87b8 type: UNKNOWN> We were able to telnet to the gearman port on the scheduler host during this time of issue occurrence. [root@uls-op-zuul4 zuul]# telnet 127.0.0.1<http://127.0.0.1> 4730 Trying 127.0.0.1<http://127.0.0.1>... Connected to 127.0.0.1<http://127.0.0.1>. The zuul webservice becomes unresponsive with the following error in log : 2022-10-27 05:27:22,387 DEBUG zuul.RPCClient: Submitting job zuul:tenant_list with data {} 2022-10-27 05:32:22,388 ERROR gear.Client.b'Zuul Web Server': Connection <gear.Connection 0x7f9f9a14be80 host: uls-op-zuul4.wdc.com<http://uls-op-zuul4.wdc.com> port: 4730> timed out waiting for a response to a submit job request: <gear.Job 0x7f9f88730fd0 handle: None name: zuul:tenant_list unique: 1666848442.3878057> We can see the following error in scheduler log even though the scheduler service is up and running 2022-10-27 06:35:16,589 ERROR gear.Client.b'Zuul Merge Client': Connection <gear.Connection 0x7f58104de128 host: uls-op-zuul4.wdc.com<http://uls-op-zuul4.wdc.com> port: 4730> timed out waiting for a response to a submit job request: <gear.Job 0x7f578d950e80 handle: None name: merger:merge unique: 29be9ce958ef4d19b0e75e274c6dd741> Regards, Mithun Mistry IT engineering , Western digital

3 6

Fwd: Help us plan the next PTG!
by Kendall Nelson 25 Oct '22

25 Oct '22

Hello Everyone! Congratulations on a great virtual PTG last week :) The OpenInfra Foundation is hosting the OpenInfra Summit in Vancouver [1], June 13 -15, 2023. We are trying to determine the level of interest among contributors to OpenInfra projects on attending a co-located PTG in Vancouver. *The exact format and dates are still being determined.* At this time, we are evaluating the level of interest from an attendee and employer perspective. Please complete the following poll so we can measure the level of interest and plan accordingly. Future updates will be distributed to the project mailing lists as well as previous PTG attendees. Poll: https://openinfrafoundation.formstack.com/forms/openinfra_ptg_2023 As a reminder, we are also gathering feedback for the virtual PTG here: https://etherpad.opendev.org/p/Oct2022_PTGFeedback -Kendall Nelson (diablo_rojo) [1] https://openinfra.dev/summit/

1 0

Intermittent bug(?) with dependencies-by-topic Queue
by A richist 25 Oct '22

25 Oct '22

Hello Zuul folk, We have 2 projects using the same Queue defined as: - queue: name: Topic allow-circular-dependencies: true dependencies-by-topic: true per-branch: true With this job and project setup: - job: name: project1-build runs: ... - job: name: project2-build runs: ... dependencies: project1-build - project: name: project1 queue: Topic gate: jobs: - project1-build - project: name: project2 queue: Topic gate: jobs: - project2-build A developer gates a Gerrit change for project1, followed closely by a change for project2. Both changes share the same value in the Topic field, and the same branch. When checking the web status page, the changes appear to enqueue in the right order, under the same Queue. The issue is that job project2-build is immediately started without waiting for the completion project1-build, leading to incorrect testing. What's more, the change for project1 is merged on successful testing despite failures in the jobs for project2. It seems Zuul simply does not treat these two changes as a set of circular dependencies, though, to my understanding, it should. We've tried checking the <tenant>/status API endpoint while this is happening, and noticed no "bundle_id" field is shown for either of the "items" in the queue - which we assume is a symptom of the same underlying issue. Stranger still, we have a Zuul Staging environment where this issue does not reproduce, project2-build waits for project-build and a "bundle_id" does exist in the status JSON object every time. Both the Staging and the Production environments use the same version of Zuul (6.4.0), the only difference between the environments we can think of is that the Staging environment runs a single instance of scheduler/executor/web (on the same machine), while the Production environment uses multiple instances of scheduler / executor / merger (but only 1 web) spread across multiple hosts. Is it possible we're hitting some race-condition, or some kind of cache (Gerrit / Zookeeper / Zuul itself)? Are we missing something here? Is there anything else we can try and do to figure this out? Regards, Arichist

2 2

Track Chair Nominations Close in One Week!
by Helena Spease 21 Oct '22

21 Oct '22

Hey everyone! Track Chair nominations <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>> for the 2023 OpenInfra Summit in Vancouver (June 13-15, 2023) are closing soon! Please submit your nominations before they close on October 28, 2022 Track Chairs for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: - Help the Summit team put together the best possible content based on your subject matter expertise - Promote the individual Tracks within your networks - Review the submissions and Community voting results in your particular Track - Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit - Ensure diversity of speakers and companies represented in your Track - Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences 2023 Summit Tracks: - 5G/NFV & Edge - AI/Machine Learning/HPC - CI/CD - Container Infrastructure - Getting Started - Hardware Enablement - Open Development - Private & Hybrid Cloud - Public Cloud - Security - Hands On Workshops Full track descriptions are available here <https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/>>. If you’re interested in nominating yourself or someone else to be a member of the Summit Track Chairs for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>. Nominations will close on October 28th, 2022. Track Chairs selections will occur before we close the Call for Presentations (CFP) so that the Chairs can host office hours to consult on submissions, and help promote the event. CFP will be opening in November, registration <https://openinfrasummit2023.eventbrite.com/> and sponsorship <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/> information are already available. Please email speakersupport(a)openinfra.dev with any questions or feedback. Cheers, Helena Spease

1 0

[Diversity][PTG] Diversity and Inclusion WG session at PTG and meeting changes
by Amy Marrich 14 Oct '22

14 Oct '22

The Diversity and Inclusion WG will be holding its session on Monday at 14:00UTC in the Folsom room. On the agenda[0] are holding a Diversity Survey for the Foundation in 2023 which includes all projects and Community Leadership Mentorship. We have also moved our regular monthly meetings to the Second Tuesday of the month at 14:00UTC and we have also moved back from video to IRC with the meetings taking place in #openinfra-diversity on OFTC. Amy (spotz) 0 - https://etherpad.opendev.org/p/oct2022-ptg-diversity

1 0

Updating the Zuul User Survey
by Clark Boylan 10 Oct '22

10 Oct '22

Hello everyone, We've been asked if we have any feedback for updating the Zuul User Survey. The current survey can be found at https://www.surveymonkey.com/r/K2B2MWL and is linked to from https://zuul-ci.org/users.html. I think the rough high level plan is to move this survey to another platform, and when we do that add an alias redirect under https://zuul-ci.org to make platforms more portable in the future without needing to change URLs. This is a great opportunity to edit the content of the survey as everything needs to be ported anyway. I've started collecting feedback on this etherpad: https://etherpad.opendev.org/p/qubhH2rvz2m-JlSaLTUX please feel free to add your feedback there as well. We will be collecting this feedback until November 7, 2022. Then the feedback will be used to port into the new survey system at that time. Clark

1 0