- Zuul-discuss - lists.opendev.org

swift upload jobs + ara-report
by Mohammed Naser 26 Aug '19

26 Aug '19

Hi everyone, The ara-report role combined with swift upload is causing a huge amount of objects generated, which I think need to be optimized in order for the role to be more usable. So, given that we're one of the clouds that OpenDev uses to publish job results, I've managed to pull some general information from that object storage cluster.. for yesterday (a sunday), there was 180k PUTs for *static* ARA assets .. and that's on a quiet day. Let's take a more busy day, Thursday, that resulted in 375,000 PUTs for static ARA assets. I think over the long time, this won't be sustainable, given an average of 200k, we're storing millions of objects per week that are being duplicated. While storage is cheap, the large number of objects starts presenting challenges (as an operator). Sure, we can decide to solve the server-side bits, but I think Zuul being a bit nicer against the clouds they talk to is a good thing (given there is actual costs that come from storage). I would like to propose that we somehow stop pushing static assets of ARA into object storage and keep them stored in some common location that ARA references to. I think this would *massively* decrease the load that is put when using Swift to publish logs. I'm open to other ideas as well. Thanks, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

4 3

Tristan is a Zuul Maintainer
by corvus＠inaugust.com 22 Aug '19

22 Aug '19

Hi, I'm pleased to announce that Tristan Cacqueray (tristanC) has been added[1] to the ranks of Zuul Maintainers. Congratulations Tristan, and thank you for all your hard work! For more information about the process and the qualifications and responsibilities of maintainers, please see [2]. -Jim [1] https://review.opendev.org/677308 [2] https://zuul-ci.org/docs/zuul/governance.html#zuul-maintainers

1 0

Shanghai Forum Selection Committee
by Jimmy McArthur 21 Aug '19

21 Aug '19

Hello Zuul! The Forum in Shanghai is rapidly approaching. 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. For information on the Summit in Shanghai: https://www.openstack.org/summit/shanghai-2019/ For more information on the Forum, please see:https://wiki.openstack.org/wiki/Forum Please reach out to myself orknelson(a)openstack.org if you're interested. Volunteers should respond on or before September 2, 2019. Cheers, Jimmy

1 0

Proposed behavior change on tags feature (passing it to Ansible)
by Sorin Sbarnea 13 Aug '19

13 Aug '19

It raised to my concern that sometimes we need to pass some tags (or skip-tags) to ansible playbooks or roles. At this moment there is no support for this in zuul but there is an older CR that would add it: https://review.opendev.org/#/c/575672/ (will need few changes) Since that review was created we already got a "tags" feature in zuul, which was initially purposed for categorization on jobs. I would like to redefine the meaning of current "tags" feature and document the fact that these would also be passed to ansible. I do not think that categorization conflicts with passing tags to ansible but is better to ask. If we do this we will be able to use "tags" and "skip-tags" just the same way we do in Ansible and avoid the case where our params are different than ansible ones. Cheers Sorin Sbarnea

3 2

Enabling new log features
by corvus＠inaugust.com 13 Aug '19

13 Aug '19

Hi, We recently made a release of Zuul with a bunch of new functionality for handling logs in-browser. The idea is that when Zuul reports the completion of a job, the URL it uses will be a link to the Zuul web application. There is a page for each build where a summary of information about the build is displayed, a tree-view of all the log files stored for the build, along with inline rendering of any text files therein, and a complete structured rendering of the tasks in the job. Note that in all cases these features require an existing SQL reporter configuration. Here's an example in use: https://review.opendev.org/#/c/675413/ There are a few steps you may need to take to upgrade existing installations to use these new features (and they may vary depending on your log storage). Here's a brief outline: Set up CORS: static log server ------------------------------ If you are simply uploading your logs with the "upload-logs" role, then you will need to make sure that the webserver which serves these logs adds an Access-Control-Allow-Origin header. If you are using Apache, you should make sure there is a line like this in the VirtualHost section: Header set Access-Control-Allow-Origin "*" If you are using nginx, make sure this appears in the location section: add_header 'Access-Control-Allow-Origin' '*'; Set up CORS: Swift ------------------ If you are using the upload-logs-swift role, it will create containers with the necessary settings automatically. However, some of these settings were only recently added to the role, so if you have a container which was created before August 1, you will need to make some updates. Run this script in an environment with openstacksdk installed, and a valid clouds.yaml: http://paste.openstack.org/raw/755695/ That will cause the Access-Control-Allow-Origin header to be set on responses which arrive with an Origin header. Test CORS --------- You can check whether the settings above are working correctly by visiting the build page for any build. Below the summary table, you should see a header that says "Results" and below that, one or more rows for the hosts used in the build with some icons and numbers. If that shows up, then the log server CORS setup is correct. Add the generate-zuul-manifest role ----------------------------------- Many of the new features require a new manifest file be uploading along with the logs. Add the generate-zuul-manifest[1] role to your base post playbook. This should run on localhost immediately before the log upload role. Once that is in place, you should begin to see "Zuul Manifest" appear under the "Artifacts" header in the build page. Remove obsolete static generation roles --------------------------------------- If you are using swift for log storage, you may already be using the htmlify-logs role[2]. This is obsoleted by the inline text log viewer, so now is a good time to remove it. Enable build page reporting --------------------------- Once that is all working, you can update your tenant configuration to set: report-build-page: true This will cause Zuul to report its internal build page URL rather than the log url (or the success- or failure-url of the job)[3]. I think that about covers it. Let me know if you have any questions. -Jim [1] https://zuul-ci.org/docs/zuul-jobs/log-roles.html#role-generate-zuul-manife… [2] https://zuul-ci.org/docs/zuul-jobs/log-roles.html#role-htmlify-logs [3] https://zuul-ci.org/docs/zuul/admin/tenants.html#attr-tenant.report-build-p…

1 0

Shanghai Summit Schedule is Live!
by Jimmy McArthur 07 Aug '19

07 Aug '19

Hi everyone, The agenda for the Open Infrastructure Summit <https://www.openstack.org/summit/shanghai-2019/summit-schedule> (formerly the OpenStack Summit) is now live! If you need a reason to join the Summit in Shanghai, November 4-6, here’s what you can expect: * Breakout sessions spanning 30+ open source projects from technical community leaders and organizations including ARM, WalmartLabs, China Mobile, China Railway, Shanghai Electric Power Company, China UnionPay, Haitong Securities Company, CERN, and more. * Project updates and onboarding from OSF projects: Airship, Kata Containers, OpenStack, StarlingX, and Zuul. * Join collaborative sessions at the Forum <https://wiki.openstack.org/wiki/Forum>, where open infrastructure operators and upstream developers will gather to jointly chart the future of open source infrastructure, discussing topics ranging from upgrades to networking models and how to get started contributing. * Get hands on training around open source technologies directly from the developers and operators building the software. Now what? * Register before prices increase <https://www.openstack.org/summit/shanghai-2019> on August 14 at 11:59pm PT (August 15 at 2:59pm China Standard Time). * Recruiting new talent? Pitching a new product? Enhance the visibility of your organization by sponsoring the Summit <https://t.e2ma.net/click/aq0kpb/ygpkur/q287bl>! Questions? Reach out to summit(a)openstack.org Cheers, Jimmy

1 0

Switch to ansible 2.8 for default version
by Paul Belanger 29 Jul '19

29 Jul '19

Greetings, For the last month[1] zuul.ansible.com has been using ansible 2.8 as the default version of ansible for jobs run by Zuul. Today we've upgraded to ansible 2.8.3 which reminded me to send this post. So far, we've yet to see any jobs failures related to ansible 2.8 however our job are not that complex. I'd ask if any zuul operators are using ansible 2.8 for jobs, and experiences so far? I would be great if we could bump the default for Zuul to 2.8, but would like a larger sample size. I've also proposed a change to opendev base-test job[2] to allow us to start doing some testing using the zuul tenant on opendev.org. [1] https://github.com/ansible/ansible-zuul-jobs/pull/155 [2] https://review.opendev.org/673012/ Paul

1 1

July 21 Deadline: Join OSF to Vote in the 2020 Foundation Board Elections
by Jeremy Stanley 17 Jul '19

17 Jul '19

As contributors to Zuul, a confirmed project supported by the OpenStack Foundation (OSF), we want to remind everyone of a benefit of joining the Foundation as an individual member: participating in the annual Foundation Board of Directors election. The OSF board represents all of the projects[1], not just OpenStack, and so it’s important for every community to actively participate, as both voters and candidates, in this election process. If you are not already an OpenStack Foundation member, please consider joining by July 21 to have a voice in the 2020 election. It’s free to join and only takes a few minutes to complete the form. Join here: https://www.openstack.org/join/register/?membership-type=foundation Time sensitive! In order to be eligible to vote in the January 2020 Individual Board of Directors election you must join as an Individual Foundation Member no later than this Sunday, July 21, 2019 at 11:59pm PT: https://www.openstack.org/election/2020-individual-director-election/ The OpenStack Foundation Board of Directors provides strategic and financial oversight of Foundation resources and staff. The 24 person Board is composed of directors elected by the Individual Foundation Members (8), directors elected by the Gold Members (8) and directors appointed by the Platinum Members (8). Individual Member Directors are there to represent the Individual Members of the Foundation. These Directors act as the link between the thousands of members of the Foundation and the Board, and are not representing the companies for which they work. Meet the current Board of Directors, and learn more here: https://www.openstack.org/foundation/board-of-directors/ https://www.openstack.org/foundation/ For further OpenStack Foundation updates and news, please sign up for the Foundation mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation You can also select the type of content you receive from the OpenStack Foundation here: https://www.openstack.org/community/email-signup [1] We’re aware that some of the language about the election on openstack.org is still “openstack project” specific, and we’ll be updating that prior to the 2020 elections to more accurately reflect that the OSF Board represents all OSF projects. Please don’t let this dissuade you from joining, if you’re interested in voting! -- Jeremy Stanley on behalf of the OSF staff

1 0

Community Voting is now Open!
by Jimmy McArthur 16 Jul '19

16 Jul '19

Community voting for the Open Infrastructure Summit Shanghai sessions is open! You can VOTE HERE <https://www.openstack.org/summit/shanghai-2019/vote-for-speakers>, but what does that mean? Now that the Call for Presentations has closed, all submissions are available for community vote and input. After community voting closes, the volunteer Programming Committee members will receive the results to review to help them determine the final selections for Summit schedule. While community votes are meant to help inform the decision, Programming Committee members are expected to exercise judgment in their area of expertise and help ensure diversity of sessions and speakers. View full details of the session selection process <https://cfp.openstack.org/#selection-process>. In order to vote, you need an OSF community membership. If you do not have an account, please create one by going to openstack.org/join <https://www.openstack.org/join>. If you need to reset your password, you can do that here <https://www.openstack.org/Security/lostpassword>. Hurry, voting closes Monday, July 22 at 11:59pmPacific Time (Tuesday, July 23 at 6:59 UTC). Continue to visit https://www.openstack.org/summit/shanghai-2019 for all Summit-related information. REGISTER Register for the Summit <https://www.openstack.org/summit/shanghai-2019> before prices increase on August 7th! VISA APPLICATION PROCESS Make sure to secure your Visa soon. More information <https://www.openstack.org/summit/shanghai-2019/travel/#travel-support> about the Visa application process. TRAVEL SUPPORT PROGRAM August 8th is the last day to submit applications. Please submit your applications <https://openstackfoundation.formstack.com/forms/travelsupportshanghai> by 11:59pm Pacific Time (August 9th at 6:59am UTC). If you have any questions, please email summit(a)openstack.org <mailto:summit@openstack.org>. Cheers, Jimmy

1 0

Testing in zuul-jobs
by corvus＠inaugust.com 16 Jul '19

16 Jul '19

Hi, I've been working on the testing situation in Zuul jobs, and I think it's getting to a good place. The overall goal is to make it easier to have test jobs that exercise roles in the zuul-jobs repo. In turn, I think that will make it easier for reviewers to accept new roles and patches. The first change to support this is that we now have in-repo configuration of what jobs run on changes to zuul-jobs. We couldn't have this before because we don't want to impose any special requirements on systems that use zuul-jobs. Jobs that test zuul-jobs may need to specify nodesets, secrets, etc., not to mention the actual project stanza to indicate what jobs run. To solve this, the "zuul" tenant of the OpenDev Zuul loads *extra* configuration from the zuul-jobs repo which no other Zuul system or tenant should do. In the extra configuration, we can add jobs for the repo itself. This is in the zuul-tests.d/ directory of the repo: https://opendev.org/zuul/zuul-jobs/src/branch/master/zuul-tests.d In that directory, I have organized the test jobs in the same way I have organized them in the documentation. I think we should continue that as we add new jobs. Next, I've added a playbook that we can use to get to something like 80% test coverage fairly quickly. It simply includes a named role. Since many of our roles just install (and possibly run) software, this test provides significant coverage at almost no cost. To use this role, just run the "test-playbooks/simple-role-test.yaml" playbook and pass the "role_name" variable. For example: https://opendev.org/zuul/zuul-jobs/src/commit/6cec9080a047f549578c7f8291aff… If you need to do anything other than simply including a role (for example, testing how multiple roles interact, or performing validation after the role runs), you should probably make a dedicated playbook for the job. I think that starting now, we should require at least the simple-role-test playbook for every role in the repo (unless there is some good reason it won't work). Some roles have special handling for different platforms and therefore need to be tested on each. Some notable examples include many of the roles which typically appear in base jobs. I have created a script in tools/update-test-platforms.py which will look for jobs with the tags "all-platforms" or "all-platforms-multinode" and it will automatically create (or delete) identical jobs for each of the platforms that are available in OpenDev. Of course, if you don't need the whole set (perhaps you only need to test on one or two specific platforms), you can still do the same thing manually. The script is located here: https://opendev.org/zuul/zuul-jobs/src/commit/6cec9080a047f549578c7f8291aff… And here is an example job which uses it: https://opendev.org/zuul/zuul-jobs/src/commit/6cec9080a047f549578c7f8291aff… It adds every job to the check and gate pipeline too. The next change which is relevant is that Zuul now automatically runs jobs when their configurations change. This means that we can have many, many jobs in the zuul-jobs repo (i.e., perhaps one job per role), each of which has a file matcher for the role directory (and possibly test playbook), and these jobs will only run on changes to those files or changes to their own job definitions. As a result, we should expect to have lots of jobs in this repo, but expect very few of them to run on any given change. The names of these jobs should start with the prefix "zuul-jobs-test". For example, "zuul-jobs-test-install-pdk-dependencies" tests the "install-pdk-dependencies" role. Thanks to David Simard who set up the original versions of the base role tests along with a fine example of a well-tested standalone role ("upload-git-mirror"). He showed us the way, and the changes I have made are simply to facilitate that test design. I've started working on adding test jobs for existing roles in the repo. There are quite a lot, and I would appreciate help on that. We're in no hurry, so if you can spare a minute every now and then to add a new job, that would be great. Also, if someone is proposing a change to an untested role, see if you can add a quick test job for it at the same time. Thanks, Jim

1 0

Re: zuul-base-jobs: Changing git connection
by Andreas Jaeger 15 Jul '19

15 Jul '19

On 15/07/2019 16.53, Andreas Jaeger wrote: > On 01/07/2019 16.14, Andreas Jaeger wrote: >> We are deprecating the git.zuul-ci.org server, it redirects already to >> opendev.org. Thus, there's a change ready for zuul-base-jobs to switch >> to the new URL. This means that everybody using zuul-base jobs, needs to >> add a connection to "opendev.org" to their zuul config (if not already >> existing), otherwise your jobs will break. >> >> The change for this is: >> https://review.opendev.org/667813 >> >> I've marked the change as WIP, I'll un-WIP it after the 15th of July, > > We're merging this now, in case you need to update your config, Since a question came up: You need to change the baseurl from https://git.zuul-ci.org/ to https://opendev.org/zuul Andreas -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg GF: Nils Brauckmann, Felix Imendörffer, Enrica Angelone, HRB 247165 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

OpenInfra Days Vietnam 2019 (Hanoi) - Call For Presentations
by Trinh Nguyen 12 Jul '19

12 Jul '19

Hello, Hope you're doing well :) The OpenInfra Days Vietnam 2019 [1] is looking for speakers in many different topics (e.g., container, CI, deployment, edge computing, etc.). If you would love to have a taste of Hanoi, the capital of Vietnam, please join us this one-day event and submit your presentation [2]. *- Date:* 24 AUGUST 2019 *- Location:* INTERCONTINENTAL HANOI LANDMARK72, HANOI, VIETNAM Especially this time, we're honored to have the Upstream Institute Training [3] hosted by the OpenStack Foundation on the next day (25 August 2019). [1] http://day.vietopeninfra.org/ [2] https://forms.gle/iiRBxxyRv1mGFbgi7 [3] https://docs.openstack.org/upstream-training/upstream-training-content.html See you in Hanoi! Bests, On behalf of the VietOpenInfra Group. -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 1

Zuul moved to zuul OpenDev Zuul Tenant
by corvus＠inaugust.com 12 Jul '19

12 Jul '19

Hi, In the OpenDev installation of Zuul (which is the Zuul that Zuul itself uses for gating), I have moved all of the Zuul projects to their own tenant (named "zuul"). If you want to see the status, you won't find it on zuul.openstack.org anymore. The new url is: https://zuul.opendev.org/t/zuul/status Also, if you have been using any dev releases (or our completely unadvertised javascript content tarball releases), new versions are no longer published to tarballs.openstack.org, but are now at: https://tarballs.opendev.org/zuul/zuul/ Zuul maintainers are now completely responsible for the pipeline definitions and trusted jobs that are part of the zuul tenant. These are located in the zuul/project-config project: https://opendev.org/zuul/project-config If that project hasn't been on your radar, now is a good time to notice it. Several of the release and publication jobs have changed as part of the move, so keep an eye out for unexpected problems there. Some of them now use the promote pipeline, so we should end up with faster publication. There is one immediate behavior change: the zuul tenant lacks the 'clean-check' requirement that the openstack tenant had. This means that you can approve a change to enqueue it into gate before the check results have returned. Feel free to use this to your advantage -- we trust the gate. :) -Jim

1 0

Design for mirrors in zuul-jobs
by corvus＠inaugust.com 10 Jul '19

10 Jul '19

Hi, When we started zuul-jobs, we had the idea that being able to use local mirrors or proxies instead of remote package mirrors, etc, is a good practice that we'd like to share with the wider community. However, our implementation in the configure-mirrors role (and others) was inherited from and built around the systems we had been running in OpenDev (and OpenStack infra), and ended up encoding a number of assumptions which don't generally hold. We'd like to replace it with a more generic system which can accommodate a wider range of schemes. I've proposed a system at: https://review.opendev.org/669948 which I think will achieve that. Essentially, each type of mirror that the roles in zuul-jobs may expect to know about would be a key in a dictionary, and under that key are data specific to that mirror. So the configure-mirrors role would, if it's being run on a Fedora system, check the 'fedora' key of the mirror_info variable, and if it finds it, use that URL to configure Fedora package mirrors. The container roles would likewise use the same mirror_info variable to see if there is a "dockerhub" entry in the dictionary. Please take a moment and review that change (which is documentation only at this point) and see if it accommodates the use cases you're aware of, and suggest any changes that may help us avoid backing into another corner in the future. Thanks, Jim

1 0

Fwd: [OpenStack Foundation] [Shanghai Summit] CFP Deadline TONIGHT
by Jimmy McArthur 02 Jul '19

02 Jul '19

Deadlines! Submit! > *From:* Ashlee Ferguson <ashlee(a)openstack.org> > *Date:* July 2, 2019 at 2:17 PM > *To:* foundation(a)lists.openstack.org, > openstack-discuss(a)lists.openstack.org, community(a)lists.openstack.org, > kata-dev(a)lists.katacontainers.io > *Subject:* [OpenStack Foundation] [Shanghai Summit] CFP Deadline TONIGHT > Hi everyone, > > The Shanghai Summit Call for Presentations [1] deadline is TONIGHT, > July 2 at 11:59 pm PT (July 3, 2019 at 15:00 China Standard Time)! > > Submit your presentations, panels, and Hands-on Workshops for the Open > Infrastructure Summit [2] by the end of today, and join the global > community in Shanghai, November 4-6, 2019. Sessions will be presented > in both Mandarin and English, so you may submit your presentation in > either language. > > Tracks [4]: > 5G, NFV & Edge > AI, Machine Learning & HPC > CI/CD > Container Infrastructure > Getting Started > Hands-on Workshops > Open Development > Private & Hybrid Cloud > Public Cloud > Security > > Other Helpful Shanghai Summit & PTG Information-- > > * Register now [5] before the early bird registration deadline in > early August (USD or RMB options available) > * Apply for Travel Support [6] before August 8. More information here [7]. > * Interested in sponsoring the Summit? [8]. > * The content submission process for the Forum and Project > Teams Gathering will be managed separately in the upcoming months. > > We look forward to your submissions! > > Cheers, > Ashlee > > [1] https://cfp.openstack.org/ > [2] https://www.openstack.org/summit/shanghai-2019/ > [3] https://cfp.openstack.org/ > [4] https://www.openstack.org/summit/shanghai-2019/summit-categories/ > [5] https://www.openstack.org/summit/shanghai-2019/ > [6] https://openstackfoundation.formstack.com/forms/travelsupportshanghai > [7] https://www.openstack.org/summit/shanghai-2019/travel/ > [8] https://www.openstack.org/summit/shanghai-2019/sponsors/ > > > > > _______________________________________________ > Foundation mailing list > Foundation(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

Assigning nodeset/nodes dynamically based in user who made the pull request in github
by Kasibhatla Sarma 01 Jul '19

01 Jul '19

Hi Team, I am trying to see if there are any options using which I can select the nodeset/nodes dynamically. For example, assume that I have two users in two different regions (us-west and us-east) Based on who made the pull request in GitHub, we would like to run the check/gate pipelines on specific nodes. For example, - nodeset: name: emea nodes: - name: node_emea label: centos76 groups: - name: emea nodes: - node_emea The first job returns the location of the user who made a pull request (say zuul_location) - job: name: check_location run: playbooks/check_location.yaml parent: base I would like to use the location in the nodeset as something like this.. - job: name: pullrequest_label run: playbooks/pullrequest_label.yaml dependencies: - check_location parent: base vars: location: "{{ zuul_location }}" nodeset: "{{ zuul_location }}" I would like to know if there are ways to achieve this Thanks, Sarma K

5 8

CFP Deadline for Open Infrastructure Summit Shanghai
by Jimmy McArthur 26 Jun '19

26 Jun '19

Hi Everyone! The July 2 deadline to submit a presentation [1] for the Open Infrastructure Summit [2] in Shanghai is in less than one week! Submit your session today and join the global community in Shanghai, November 4-6, 2019. Sessions will be presented in both Mandarin and English, so you may submit your presentation in either language. Submit your presentations, panels, and hands-on workshops [3] before July 2 at 11:59 pm PT (July 3, 2019 at 15:00 China Standard Time). Tracks [4]: Container Infrastructure Hands-on Workshops AI, Machine Learning & HPC Private & Hybrid Cloud Public Cloud 5G, NFV & Edge Open Development Getting Started CI/CD Security Upcoming Shanghai Summit Deadlines * Register now [5] before the early bird registration deadline in early August (USD or RMB options available) * Apply for Travel Support [6] before August 8. For more information on the Travel Support Program, go here [7]. * Interested in sponsoring the Summit? [8]. * The content submission process for the Forum and Project Teams Gathering will be managed separately in the upcoming months. We look forward to your submissions! Cheers, Jimmy [1] https://cfp.openstack.org/ [2] https://www.openstack.org/summit/shanghai-2019/ [3] https://cfp.openstack.org/ [4] https://www.openstack.org/summit/shanghai-2019/summit-categories/ [5] https://www.openstack.org/summit/shanghai-2019/ [6] https://openstackfoundation.formstack.com/forms/travelsupportshanghai [7] https://www.openstack.org/summit/shanghai-2019/travel/ [8] https://www.openstack.org/summit/shanghai-2019/sponsors/

1 0

Feedback for Zuul web UI
by Paul Belanger 24 Jun '19

24 Jun '19

Greetings, I wanted to share some feedback I've gotten over the last few weeks about the Zuul web UI, I am mostly doing so, because I am struggling to make progress on fixing these issue myself (I don't have my JS experience). Here are a few recent examples: Builds page ----------- * Lack of pagination support. Currently, there is no easy way to scroll through the history of the builds UI. Right now, it is hardcoded to a single page, of 50 results. Users would like the ability to go further backwards in time, even listing more then 50 results per page. * More filters. It has been asked, for the ability to add filtering for start / end time ranges. This would allow a user to create a weekly report email, linking to the results of the week. The context is periodic jobs. Voting / non-voting jobs has also been requested. * Regex of job name filters. We currently have a lot of jobs which append the version of python onto a job name. For example, ansible-test-network-integration-vyos-python37, ansible-test-network-integration-vyos-python36, etc. A few users have requested the ability to use a single regex for job name filter. Buildset page ------------- * Add link to builds page of jobs that ran. Some users would like to see a link create, which auto creates the build page filters for a change that was build. This is because, in our case we have some jobs to do not report back to github, and depending on PR to list jobs isn't 100%. I'm happy to give additional information if needed, or also happy to write the code, howerver I'd likely need some hand holding for the first little bit. Thanks! Paul

2 1

Zuul autohold changes
by David Shrewsbury 17 Jun '19

17 Jun '19

Hello, I've mentioned this info in the IRC channel, but thought it would be a good idea to mention this on the mailing list as well. I have a series of changes [1] up that significantly change the way Zuul deals with autohold requests. The tl;dr of it is that we now store those requests in ZooKeeper rather than in memory. Advantages of this change are: 1. Easily identify which nodes are held for a request and to easily delete those held nodes when the request is deleted. 2. Supports future scheduler scale-out. 3. Hold requests are kept across Zuul restarts. This work conflicts with Matthew's work on the web API [2] as it adds new commands for deleting autohold requests, and getting autohold detail information. I fully expect his work to merge first, so my series of changes will likely need rework after that merge. I bring this up because I'm about to be AFK for a couple of weeks for shoulder surgery (such fun), so if those merges happen while I'm out, I'm hoping someone can volunteer to fix any merge conflicts or other minor changes that may be needed. Since this all started because of a hand-wavey comment from Monty, I volunteer him. :) :) :) j/k [1] https://review.opendev.org/#/q/topic:autohold-revamp [2] https://zuul-ci.org/docs/zuul/developer/specs/tenant-scoped-admin-web-API.h… -Shrews

2 1

Reviews for the Bitbucket Server driver
by Mark Meyer 14 Jun '19

14 Jun '19

Hi, I'd like you to review the Bitbucket Server driver for Zuul. We now have all the components in place. Basic testing shows that it's working and my team at work has been using it for a while in an experimental setting. Now we need to go the next steps and have it refined. *Not Bitbucket Cloud Thanks, mark -- Mark Meyer mark(a)ofosos.org

1 0

Slack connectivity
by Mark Meyer 13 Jun '19

13 Jun '19

Hey list, I'd like to gauge interest here. So you want connectivity options for slack? I'm thinking of having this as part of zuul to trigger jobs and report results, out alternatively as an external bit that runs on the scheduler node. We already have some code and some ideas. But I don't feel like walking that path on my own. What so you think? Cheers, mark -- Mark Meyer mark(a)ofosos.org

4 3

GitHub API ReadTimeout Errors
by Paul Belanger 12 Jun '19

12 Jun '19

Greetings, We (ansible team) are running into a issue using the zuul github driver, please see the following pastebin: http://paste.openstack.org/show/752756/ As you can see, we don't seem to be getting reliable network access to api.github.com. I am currently trying to figure out if this is a network issue with our control plane provider (vexxhost) or something related to GitHub side (eg: bad load balancer). However, what it does result in, is Zuul missing events from GitHub and not properly enqueue PRs into the pipelines. I understand there is only so much we might be able to do regarding a network issue, but I'd be interested to hear if there are idea of how we could tolerate them more. I also wonder if we should be reporting these issues back to the users PR too. My main goal is to minimize the amount of humans that _think_ zuul is to blame for tests not being run on their PRs, when in fact it is something else. - Paul

2 3

Shanghai PTG Changes
by Kendall Nelson 12 Jun '19

12 Jun '19

Hello All, After Denver we were able to take time to reflect on the improvements we can make now that the PTG will occur immediately following the summit for the near future. While Shanghai will have its own set of variables, it's still good to reevaluate how we allocate time for groups and how we structure the week overall. tldr; - Onboarding is moving into the PTG for this round (updates stay a part of the Summit) - You can still do regular PTG stuff (or both onboarding and regular PTG stuff) - PTG slots can be as short as 1/4 of a day - More shared space at the Shanghai venue, less dedicated space - New breakdown: 1.5 days of Forum and 3.5 days of PTG - Survey will be out in a few weeks for requesting PTG space We'll have our traditional project team meetings at the PTG in Shanghai as the default format, that won't change. However, we know many of you don't expect to have all your regulars attend the PTG in Shanghai. To combat this and still help project teams make use of the PTG in the most effective way possible we are encouraging teams that want to meet but might not have all the people they need to have technical discussions to meet anyway and instead focus on a more thorough onboarding of our Chinese contributors. Project teams could also do a combination of the two, spend an hour and a half on onboarding (or however much time you see fit) and then have your regular technical discussions after. Project Updates will still be a part of the Summit like normal, its just the onboardings that will be compacted into the PTG for Shanghai. We are making PTG days more granular as well and will have the option to request 1/4 day slots in an effort to leave less empty space in the schedule. So if you are only doing onboarding, you probably only need 1/4 to 1/2 of a day. If you are doing just your regular technical discussions and still need three days, thats fine too. The venue itself (similar to Denver) will have a few large rooms for bigger teams to meet, however, most teams will meet in shared space. For those teams meeting to have only technical discussions and for teams that have larger groups, we will try to prioritize giving them their own dedicated space. For the shared spaces, we will add to the PTGbot more clearly defined locations within the shared space so its easier to find teams meeting there. I regret to inform you that, again, projection will be a very limited commodity. Yeah.. please don't shoot the messenger. Due to using mainly shared space, projection is just something we are not able to offer. The other change I haven't already mentioned is that we are going to have the PTG start a half day early. Instead of only being 3 days like in Denver, we are going to add more time to the PTG and subtract a half day from the Forum. Basically the breakdown will be 1.5 Forum and 3.5 PTG with the Summit overlapping the first two days. I will be sending the PTG survey out to PTLs/Project Leads in a couple weeks with a few changes. -Kendall Nelson (diablo_rojo)

1 0

Zuul project update 2019-06-10
by corvus＠inaugust.com 10 Jun '19

10 Jun '19

Hi, Last week we merged the Tenant-scoped admin web API spec: https://zuul-ci.org/docs/zuul/developer/specs/tenant-scoped-admin-web-API.h… We can start reviewing the implementation for that now (status:open topic:zuul_admin_web). David is finishing up a series which stores autohold information in Zookeeper to improve the experience around that. Tobias has continued his work on adding event IDs to log messages. Clark is moving us to node version 10 across all of our javascript jobs. Mark Meyer has been refining his patch series to add a Bitbucker driver. I've been (and will continue to) work on moving Zuul into its own tenant in the OpenDev Zuul. That will require some changes to where we publish branch-tip builds. Help write the next update email by updating https://etherpad.openstack.org/p/zuul-update-email Thanks, Jim

1 0

Toggle host-key-checking per label
by Paul Belanger 05 Jun '19

05 Jun '19

Greetings, I'd like to get a few eyes on https://review.opendev.org/663378/ please, as I'm currently blocked on doing some network automation with nodepool / zuul. Due to issues with a network appliance, we have a use case where an interface comes online but there is no default gateway assigned (apparently this needs to be done by a human). In this case, we actually want nodepool to launch the node, but not scan for hostkeys. This is okay for us, because zuul doesn't directly manage this node (due to connection being network_cli), we actually create a nodeset with another node (fedora) that zuul can still reach then use nested ansible to provision the network appliance. We cannot move the network node into its own pool, because we cannot split labels multinodes across pools, we get node_failures back from nodepool. I'm open to other ideas / solutions to work around this use-case, but believe adding a host-key-checking toggle at the label level, should work. - Paul

1 0