- 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 21 Aug '19

21 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 06 Aug '19

06 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 15 Jul '19

15 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