March 2020 - Zuul-discuss - lists.opendev.org

[zuul-ci.org] SEO improvements
by Jimmy McArthur 14 Mar '20

14 Mar '20

Hi all - We've contracted a professional SEO firm to help improve search placement for all OSF projects. I'd like to crowd source this on each of the project mailing lists, so the community is able to be involved: “Wish List” of keywords: 8-12 big terms you think fit your domain (if you only have 4-5 to share, fewer is okay) - open source ci - ? At least 3 competitors - Jenkins - ? Any other input on positioning, offerings, etc. that you think will help best filter for relevance - ? Cheers, Jimmy

1 1

ensure-tox: install inside python3 by default
by Mohammed Naser 13 Mar '20

13 Mar '20

Hi everyone, The current behavior of the `ensure-tox` role is to install `tox` using Python 2. The following change will switch the default behavior to installing it via Python 3. The option of installing `tox` using Python 2 remains available. https://review.opendev.org/#/c/712804/ If you're using Python 2 for your jobs and you require that `tox` continues to be installed inside Python 2, please update your jobs to use the following in their vars: tox_prefer_python2: true This message serves as a heads-up for all Zuul operators that consume zuul/zuul-jobs, this change will be merging in 2 weeks, please feel free to bring up any concerns if we've missed anything. Thanks, Mohammed

2 1

[zuul-ci.org] Supporting Companies
by Jimmy McArthur 13 Mar '20

13 Mar '20

Hello All - One of the things the Foundation offers for our projects is the ability to show Supporting Companies on each of the project websites [1]. We also have a little blurb or button there for other companies that are looking to support the project in some way. This can be through infrastructure donation or helping to offset events costs, etc... We'd like to get such a page up on Zuul, but I want to check with the community first to see what thoughts are around the concept as well as placement on the site. Cheers, Jimmy [1] https://katacontainers.io/supporters/

2 1

[zuul-community] [OpenDev] We want your discussion ideas!
by Jimmy McArthur 13 Mar '20

13 Mar '20

Hi everyone, We still need your help shaping the discussion content for OpenDev + PTG, June 8-11, 2020 <https://www.openstack.org/events/opendev-ptg-2020/>! Our vision is for the content to be programmed by you-- the community. Programming Committees for each Track have begun meeting to discuss potential topics for the event, but they need your ideas and input to make sure all of the content is relevant and interesting to the community. The Programming Committee will also select moderators who will lead interactive discussions on a particular topic within the Track, so make sure to volunteer through the form below if you’re interestedin that as well. Check out this etherpad <https://etherpad.openstack.org/p/r.961497ec02b63da123fbda235a7ba02e>to see what topics the Committees are currently discussing. If you’re interested in volunteering as an OpenDev discussion moderator, or would like to suggest topics for moderated discussions within a particular Track, please read the details below, and then fill out this form <https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volun…>. We’re looking for discussion topics and Moderators for the following OpenDev Tracks: - Hardware Automation - Large-scale Usage of Open Source Infrastructure Software - Containers in Production - Key Challenges for Open Source in 2020 OpenDev Discussion Moderatorswill: - Be appointed by the Programming Committees - Facilitate discussions within a particular Track - Have adequate knowledge and experience to lead and moderate discussion around certain topics during the event - Work with Programming Committee to decide focal point of discussion Moderators need to be available to attend OpenDev, June 8 - 10, 2020. Volunteer to be a moderator or suggest discussion topics here *before March 20*: <https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volun…>https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volun… Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation _______________________________________________ Community mailing list Community(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/community

1 0

Request for Wiki Assistance
by Jimmy McArthur 11 Mar '20

11 Mar '20

Hi Zuul Community! We had our recent Zuul post denied by the wikipedia community. It's not a huge surprise and it's notoriously difficult to get a "first post" up. If any of you have some Zuul expertise you could espouse in a wiki-like way, and/or some wikipedia juice/advice you could offer us, it would be greatly appreciated. https://en.wikipedia.org/wiki/Draft:Zuul_(software) You can read the bits at the top of the page about what we're doing wrong. A few things could help: * More primary sources - by this they mean high value domains or qualified news sources in the industry * A variation on authors * I'm not sure how to address their contention that the entry reads like an advertisement, but I'm open to suggestions :) Having a wiki page is a really big step towards making Zuul a more high profile open source CI and project gating alternative, so please let me know how you can help! Cheers, Jimmy

2 3

Run a job if a directory or a file exist in the source tree
by Fabien Boucher 11 Mar '20

11 Mar '20

Hi, What do you think about a job attribute a bit similar to "files", but for telling Zuul to execute the job only if one of the listed file or directory exist in the project source tree ? Use case is where I have a common set of jobs attached to a large number of repositories. But some of the repositories don't have a specific directory that contains the data used by a job. So instead of spawning a VM and run the job playbook to discover the directory is missing and skip the rest of the playbook's task, I'd like to tell Zuul to simply skip the job at all and not waste nodepool resources. Thus this new job's attribute. Another solution is to run small parent job, in a container, to discover if the directory exist and let run or not the child job. Any thoughts ? Is that new job attribute could be valuable ? Fabien

3 3

feature: display branch in zuul dashboard
by Sorin Sbarnea 07 Mar '20

07 Mar '20

Wes asked me few days ago if we could make the branch visible in zuul ui. To me it makes sense as long we do not display the master branch, mainly because I prefer an uncluttered interface. What do you think about it? Should I propose a patch or not? Cheers Sorin ---------- Forwarded message --------- From: Wesley Hayutin <whayutin(a)redhat.com> Date: Mon, 2 Mar 2020 at 15:45 Subject: future zuul ui enhancement. To: Sorin Sbarnea <ssbarnea(a)redhat.com> I would be cool to see the branch in the header for each review in check and gate. Currently we have... openstack/tripleo-quickstart-extras 710230,2 <https://review.opendev.org/710230> 1 hr 55 min 1 hr 10 min Would be nice to add branch info there too. Let me know if that makes sense. Thanks -- -- /sorin

2 1

zuul roles bindep and epel enablement issue
by Sorin Sbarnea 07 Mar '20

07 Mar '20

Background: As you probably know on centos there is the EPEL additional repository which provides some extra packages which are not part of the distribution, so not covered by support. Enabling EPEL is easy, usually just by installing epel-release, unless someone already installed it and disabled it (this is what rdo does in order to have the mirrors configured). Recently I discovered that some linters do need re2-devel, which comes from epel on centos-8. So far we used bindep succesfully but we cannot tell bindep role to install epel-release package before installing the the other rpms. Another approach would be to use test-setup.sh to enable this repo but last time I checked this runs after bindep, so too late. How can we address this issue? Do we have a more generic issue to install dependencies on nodes? I would not want to patch nodeset images because these makes the job not portable between different zuul instances. Another reason for not patching images is that what could be good idea to install for my use case, could prove bad for another one. Cheers, Sorin -- -- /sorin

2 1

Zuul v4/v5 planning
by corvus＠inaugust.com 05 Mar '20

05 Mar '20

Hi, Some folks in IRC recently brainstormed how to sequence the changes needed to implement the scale-out-scheduler spec. This is the plan we came up with, including a description of the changes at a high level, along with the major version numbers for important releases. Our current plan is to perform all of this development on the master branch, continue other unrelated development at the same time, and release interim releases as appropriate in the usual manner. We believe this sequence is constructed in a way that will enable everyone to continue to deploy the latest releases (or commits) of Zuul in the usual way with minimal disruption. At the end of the process, you'll be able to deploy more than one scheduler. :) There will be a couple of points in the timeline where we will ask you to make forward-compatible changes to your configuration or deployment. As long as you make those changes before the upcoming release which requires them, we don't expect any issues. Here is the current plan: * Add support for Zookeeper auth * Ask users to configure Zookeeper auth, ensure all Zuul components can reach the Zookeeper cluster, and define an SQL connection * Release last 3.x series * Require Zookeeper auth * Have all components connect to Zookeeper, even if they just idle for now * SQL reporters are required (an implied SQL reporter is added to every pipeline, explicit SQL reporters are ignored) * Release 4.0.0 * Warn on explicit SQL reporters in pipelines * Start adding in more Zookeeper stuff, removing equivalent gearman as appropriate * Release 4.1.0 * Error on explicit sql reporters in pipelines * Complete HA scheduler work * Release 5.0.0 -Jim

1 0