*** marios is now known as marios|ruck | 05:41 | |
*** rpittau|afk is now known as rpittau | 07:55 | |
*** holser is now known as holser_ | 08:50 | |
*** jcapitao is now known as jcapitao_lunch | 11:00 | |
opendevreview | Benedikt Löffler proposed zuul/nodepool master: WIP: Upload script https://review.opendev.org/c/zuul/nodepool/+/802255 | 11:03 |
---|---|---|
opendevreview | Benedikt Löffler proposed zuul/nodepool master: WIP: Upload script https://review.opendev.org/c/zuul/nodepool/+/802255 | 11:05 |
*** dviroel|out is now known as dviroel | 11:53 | |
opendevreview | Simon Westphahl proposed zuul/zuul master: Set runtime related system attributes on reconfig https://review.opendev.org/c/zuul/zuul/+/801749 | 12:01 |
opendevreview | Felix Edel proposed zuul/zuul master: Add MergerApi https://review.opendev.org/c/zuul/zuul/+/787686 | 12:03 |
opendevreview | Felix Edel proposed zuul/zuul master: Execute merge jobs via ZooKeeper https://review.opendev.org/c/zuul/zuul/+/802299 | 12:03 |
opendevreview | Felix Edel proposed zuul/zuul master: Align Executor API test helper methods with Merger API https://review.opendev.org/c/zuul/zuul/+/802300 | 12:03 |
*** jcapitao_lunch is now known as jcapitao | 12:33 | |
opendevreview | Simon Westphahl proposed zuul/zuul master: Cache system config in Zookeeper https://review.opendev.org/c/zuul/zuul/+/801859 | 12:53 |
opendevreview | Simon Westphahl proposed zuul/zuul master: Cache system config in Zookeeper https://review.opendev.org/c/zuul/zuul/+/801859 | 13:20 |
JPEW | How would one do something like a Jenkins Matrix job with Zuul? Is that multiple projects (possibly pulling from the same project template) that run on the same pipeline? | 13:34 |
corvus | JPEW: do you want a set of similar jobs with minor differences? like run the same "job" but with 3 different versions of software? | 13:42 |
JPEW | Basically; building the same software with different configurations | 13:44 |
corvus | JPEW: if so -- look into project inheritance: https://zuul-ci.org/docs/zuul/reference/job_def.html#job - define a job that does most of the work, then inherit from it and change just the version. let me get an example | 13:44 |
corvus | JPEW: like these python jobs from zuul-jobs: https://opendev.org/zuul/zuul-jobs/src/branch/master/zuul.d/python-jobs.yaml | 13:45 |
corvus | JPEW: also, once you have them all defined, you can group them together with a project-template so you can say "run all the python jobs" https://zuul-ci.org/docs/zuul/reference/project_def.html#project-template | 13:46 |
corvus | JPEW: and keep in mind jenkins and zuul use some of the same terms, but they have different meanings (especially project, pipeline, and template) https://zuul-ci.org/docs/zuul/reference/glossary.html | 13:47 |
JPEW | corvus: Ya, that's helpful. Thanks! | 13:48 |
corvus | JPEW: yw | 13:48 |
*** shrews[m] is now known as Shrews | 14:27 | |
Shrews | awww, does matrix not preserve nick capitalization? | 14:29 |
Shrews | shrews < Shrews | 14:29 |
mordred | shrews: you can totally see it. Check display name | 14:30 |
mordred | Or /displayname i think | 14:30 |
mordred | Set | 14:31 |
fungi | in irc it's showing up capitalized, fwiw | 14:31 |
Shrews | good. i'd hate for folks to get confused :) | 14:31 |
fungi | not that shrews, the other Shrews! | 14:32 |
fungi | the one who knows where to find his shift key | 14:32 |
opendevreview | Matthieu Huin proposed zuul/zuul master: Example Docker compose: keycloak integration https://review.opendev.org/c/zuul/zuul/+/769943 | 14:59 |
opendevreview | Felix Edel proposed zuul/zuul master: Execute merge jobs via ZooKeeper https://review.opendev.org/c/zuul/zuul/+/802299 | 15:03 |
opendevreview | Felix Edel proposed zuul/zuul master: Align Executor API test helper methods with Merger API https://review.opendev.org/c/zuul/zuul/+/802300 | 15:03 |
opendevreview | Felix Edel proposed zuul/zuul master: Provide zk_client to merger client rather than the whole scheduler https://review.opendev.org/c/zuul/zuul/+/773029 | 15:03 |
opendevreview | Felix Edel proposed zuul/zuul master: Remove history from RecordingMergeClient https://review.opendev.org/c/zuul/zuul/+/773030 | 15:03 |
opendevreview | Felix Edel proposed zuul/zuul master: Move merge request cleanup from merger to scheduler https://review.opendev.org/c/zuul/zuul/+/802321 | 15:03 |
corvus | felixedel: i'm still reviewing that stack -- but why do you add the cleanup to the merger in one patch and then move it to the scheduler in another? | 15:05 |
corvus | felixedel: (why not add it directly to the scheduler in the first place) | 15:06 |
felixedel | corvus: That was the original patch (long before the actual version of the executor API). I didn't want to change too much in a single patch, so I thought the cleanup is worth it's own patch. | 15:08 |
corvus | felixedel: okay thanks; we can probably leave it that way then | 15:09 |
*** holser_ is now known as holser | 16:00 | |
TylerPearce[m] | Hello! I'm trying to run through the steps in https://zuul-ci.org/docs/zuul/tutorials/quick-start.html but I'm running into some errors trying to run `sudo -E docker-compose -p zuul-tutorial up`. The errors are `ERROR: for zuul_logs_1 a bytes-like object is required, not 'str'`, and a similar error for zuul_gerrit_1. I'm on AWS EC2 instance, starting from a fresh root volume. The instance type is a t2.nano Ubuntu Server 20.04 LTS. Is there | 16:30 |
TylerPearce[m] | something I'm missing? I ran through the steps under "Start Zuul Containers" for Ubuntu, cloned, then tried to run the docker-compose command. No other setup | 16:30 |
corvus | Tyler Pearce: is there any more information along with those errors? if so, can you copy and paste the text into matrix? | 16:35 |
*** rpittau is now known as rpittau|afk | 16:37 | |
*** holser is now known as holser_ | 16:41 | |
* TylerPearce[m] < https://matrix.org/_matrix/media/r0/download/matrix.org/gotLDwtRGRjeOnpHVPlONOwR/message.txt > | 16:45 | |
*** marios|ruck is now known as marios|out | 16:54 | |
*** dviroel is now known as dviroel|afk | 16:56 | |
corvus | Tyler Pearce: hrm, there's really not much to go on there is there. i don't have access to aws right now to try to figure out if there's something about that environment that's causing issues for docker or docker-compose. i should be able to try that later | 17:01 |
TylerPearce[m] | Yeah, sorry there's not much. Do you think using an older version of Ubuntu would help here? I can try running through Ubuntu Server 18.04 LTS | 17:02 |
corvus | i think we test the quick-start on 20.04 | 17:04 |
fungi | confirmed: https://zuul.opendev.org/t/zuul/build/bcb2b070fbcc495aa34f477113e7ea77/log/zuul-info/inventory.yaml#19 | 17:05 |
fungi | i was just looking that up | 17:05 |
corvus | Tyler Pearce: i think you may need more memory than that; i just started a t2.micro (which is 1G as opposed to 0.5G nano) and i think it's having problems. | 17:15 |
corvus | trying a t2.small now | 17:20 |
TylerPearce[m] | Ahh okay, yeah I was using the smallest possible instance. I can try working my way up in sizes until I get one that works haha | 17:22 |
fungi | right, it's worth noting we test the quickstart playbooks and commands on a virtual machine with 8gb ram, which is likely overkill but means we don't necessarily know how small is too small | 17:22 |
TylerPearce[m] | That makes sense. Thanks for your help troubleshooting! | 17:23 |
corvus | hopefully we'll figure that out in a little bit and we can update the docs :) | 17:23 |
TylerPearce[m] | Yes 😀 | 17:23 |
corvus | small is looking more promising so far | 17:24 |
corvus | total used free shared buff/cache available | 17:25 |
corvus | Mem: 2032708 1224320 77664 1816 730724 621064 | 17:25 |
* corvus < https://matrix.org/_matrix/media/r0/download/matrix.org/jiGMIolqzVTzauQNFVMjpRnM/message.txt > | 17:26 | |
* corvus < https://matrix.org/_matrix/media/r0/download/matrix.org/xHXTGtZmNUAhdFKQwDqryinR/message.txt > | 17:26 | |
corvus | sorry about the edits... | 17:26 |
corvus | anyway, at the end of the quickstart setup, the machine is using ~1.2G of ram | 17:27 |
corvus | so i think 2 is a realistic minimum -- though we haven't run any jobs yet | 17:28 |
TylerPearce[m] | Nice, thanks for testing that for me! 2 seems reasonable to get up and running. I'll play around with it once I get it set up, but for our use case we're planning to use CircleCI for running tests so the load should remain pretty low. (Context: Our existing CI system is CircleCI, people still want to use that for running checks since it's all set up, but they want Zuul to manage the merge flow) | 17:30 |
opendevreview | James E. Blair proposed zuul/zuul master: Update tutorial instructions with RAM requirement https://review.opendev.org/c/zuul/zuul/+/802375 | 17:30 |
fungi | TylerPearce[m]: neat, so zuul would run lightweight jobs from the executor to trigger circleci? | 17:31 |
TylerPearce[m] | Yes! That's the plan | 17:32 |
fungi | i guess that also gives you the flexibility to run other jobs directly with zuul later if/when you get comfortable doing so | 17:32 |
TylerPearce[m] | Also yes! I'll probably try to slowly push toward moving things into Zuul over time, but for now this is what people are comfortable with, and it's low-risk this way | 17:34 |
fungi | absolutely makes sense, yep | 17:34 |
corvus | Tyler Pearce: that sounds like a great start. once you have that going, if you start to run more jobs natively in zuul, you can take more advantage of zuul's speculative gating. zuul can speculatively test deep stacks of changes and merge them nearly simultaneously. | 17:34 |
corvus | Tyler Pearce: i pushed up a doc change suggesting 2GiB as a minimum for now -- let us know if you end up needing more :) | 17:35 |
TylerPearce[m] | I'm hoping to utilize the speculative gating as part of the initial rollout. I haven't figured out the specifics, but I'm hoping I can create a dependent pipeline that calls the CircleCI checks, waits for the results, then uses that as the pass/fail for gating | 17:37 |
TylerPearce[m] | Thank you for suggesting that update so quickly! I appreciate all the help | 17:37 |
fungi | that's definitely an interesting secondary error manifesting based on your log | 17:39 |
mordred | Tyler Pearce: the biggest challenge to sort when you poke at the specifics is figuring out how to get CircleCI checks to use the git checkout state from zuul. If you figure that out - it'll probably be a really interesting pattern! | 17:42 |
fungi | yeah, in theory zuul can push the predicted state to wherever the jobs are being run | 17:44 |
TylerPearce[m] | I'll let you know what I come up with if (hopefully 'when') I figure it out | 17:44 |
*** holser_ is now known as holser | 19:28 | |
*** dviroel|afk is now known as dviroel | 20:04 | |
opendevreview | James E. Blair proposed zuul/zuul master: Add some unit tests for the merger api https://review.opendev.org/c/zuul/zuul/+/802398 | 21:03 |
opendevreview | James E. Blair proposed zuul/zuul master: Add some unit tests for the merger api https://review.opendev.org/c/zuul/zuul/+/802398 | 21:32 |
opendevreview | Merged zuul/zuul master: Update tutorial instructions with RAM requirement https://review.opendev.org/c/zuul/zuul/+/802375 | 22:03 |
opendevreview | James E. Blair proposed zuul/zuul master: Shard merge request payload https://review.opendev.org/c/zuul/zuul/+/802403 | 22:41 |
*** ChanServ changes topic to "Discussion of the project gating system Zuul | Website: https://zuul-ci.org/ | Docs: https://zuul-ci.org/docs/ | Source: https://opendev.org/zuul | Channel logs: https://meetings.opendev.org/irclogs/%23zuul/" | 22:57 | |
opendevreview | James E. Blair proposed zuul/zuul master: Store ephemeral waiter nodes for merger api https://review.opendev.org/c/zuul/zuul/+/802404 | 23:00 |
opendevreview | James E. Blair proposed zuul/zuul master: Shard merger api results https://review.opendev.org/c/zuul/zuul/+/802405 | 23:18 |
opendevreview | James E. Blair proposed zuul/zuul master: Add lost merge results cleanup method https://review.opendev.org/c/zuul/zuul/+/802406 | 23:18 |
corvus | felixedel: there are some things that we did in the executor api change that didn't make it into the merger api. i left comments on them, and also some new things i spotted. i pushed up some changes to implement some of those. if you agree with them, i think we should squash them all into 787686. some will necessitate updates to 802299 -- since that's the case, i think we should go ahead and squash 802321 into 802299. if we do all of that, i | 23:22 |
corvus | think we can end up with 2 changes that are tested and easy to understand and review. | 23:22 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!