Monday, 2021-07-26

*** marios is now known as marios|ruck05:41
*** rpittau|afk is now known as rpittau07:55
*** holser is now known as holser_08:50
*** jcapitao is now known as jcapitao_lunch11:00
opendevreviewBenedikt Löffler proposed zuul/nodepool master: WIP: Upload script  https://review.opendev.org/c/zuul/nodepool/+/80225511:03
opendevreviewBenedikt Löffler proposed zuul/nodepool master: WIP: Upload script  https://review.opendev.org/c/zuul/nodepool/+/80225511:05
*** dviroel|out is now known as dviroel11:53
opendevreviewSimon Westphahl proposed zuul/zuul master: Set runtime related system attributes on reconfig  https://review.opendev.org/c/zuul/zuul/+/80174912:01
opendevreviewFelix Edel proposed zuul/zuul master: Add MergerApi  https://review.opendev.org/c/zuul/zuul/+/78768612:03
opendevreviewFelix Edel proposed zuul/zuul master: Execute merge jobs via ZooKeeper  https://review.opendev.org/c/zuul/zuul/+/80229912:03
opendevreviewFelix Edel proposed zuul/zuul master: Align Executor API test helper methods with Merger API  https://review.opendev.org/c/zuul/zuul/+/80230012:03
*** jcapitao_lunch is now known as jcapitao12:33
opendevreviewSimon Westphahl proposed zuul/zuul master: Cache system config in Zookeeper  https://review.opendev.org/c/zuul/zuul/+/80185912:53
opendevreviewSimon Westphahl proposed zuul/zuul master: Cache system config in Zookeeper  https://review.opendev.org/c/zuul/zuul/+/80185913:20
JPEWHow 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
corvusJPEW: 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
JPEWBasically; building the same software with different configurations13:44
corvusJPEW: 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 example13:44
corvusJPEW: like these python jobs from zuul-jobs: https://opendev.org/zuul/zuul-jobs/src/branch/master/zuul.d/python-jobs.yaml13:45
corvusJPEW: 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-template13:46
corvusJPEW: 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.html13:47
JPEWcorvus: Ya, that's helpful. Thanks!13:48
corvusJPEW: yw13:48
*** shrews[m] is now known as Shrews14:27
Shrewsawww, does matrix not preserve nick capitalization?14:29
Shrewsshrews < Shrews14:29
mordredshrews: you can totally see it. Check display name14:30
mordredOr /displayname i think14:30
mordredSet14:31
fungiin irc it's showing up capitalized, fwiw14:31
Shrewsgood. i'd hate for folks to get confused  :)14:31
funginot that shrews, the other Shrews!14:32
fungithe one who knows where to find his shift key14:32
opendevreviewMatthieu Huin proposed zuul/zuul master: Example Docker compose: keycloak integration  https://review.opendev.org/c/zuul/zuul/+/76994314:59
opendevreviewFelix Edel proposed zuul/zuul master: Execute merge jobs via ZooKeeper  https://review.opendev.org/c/zuul/zuul/+/80229915:03
opendevreviewFelix Edel proposed zuul/zuul master: Align Executor API test helper methods with Merger API  https://review.opendev.org/c/zuul/zuul/+/80230015:03
opendevreviewFelix Edel proposed zuul/zuul master: Provide zk_client to merger client rather than the whole scheduler  https://review.opendev.org/c/zuul/zuul/+/77302915:03
opendevreviewFelix Edel proposed zuul/zuul master: Remove history from RecordingMergeClient  https://review.opendev.org/c/zuul/zuul/+/77303015:03
opendevreviewFelix Edel proposed zuul/zuul master: Move merge request cleanup from merger to scheduler  https://review.opendev.org/c/zuul/zuul/+/80232115:03
corvusfelixedel: 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
corvusfelixedel: (why not add it directly to the scheduler in the first place)15:06
felixedelcorvus: 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
corvusfelixedel: okay thanks; we can probably leave it that way then15:09
*** holser_ is now known as holser16: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 there16: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 setup16:30
corvusTyler 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|afk16: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|out16:54
*** dviroel is now known as dviroel|afk16:56
corvusTyler 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 later17: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 LTS17:02
corvusi think we test the quick-start on 20.0417:04
fungiconfirmed: https://zuul.opendev.org/t/zuul/build/bcb2b070fbcc495aa34f477113e7ea77/log/zuul-info/inventory.yaml#1917:05
fungii was just looking that up17:05
corvusTyler 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
corvustrying a t2.small now17: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 haha17:22
fungiright, 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 small17:22
TylerPearce[m]That makes sense. Thanks for your help troubleshooting!17:23
corvushopefully we'll figure that out in a little bit and we can update the docs :)17:23
TylerPearce[m]Yes 😀17:23
corvussmall is looking more promising so far17:24
corvus              total        used        free      shared  buff/cache   available17:25
corvusMem:        2032708     1224320       77664        1816      730724      62106417: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
corvussorry about the edits...17:26
corvusanyway, at the end of the quickstart setup, the machine is using ~1.2G of ram17:27
corvusso i think 2 is a realistic minimum -- though we haven't run any jobs yet17: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
opendevreviewJames E. Blair proposed zuul/zuul master: Update tutorial instructions with RAM requirement  https://review.opendev.org/c/zuul/zuul/+/80237517:30
fungiTylerPearce[m]: neat, so zuul would run lightweight jobs from the executor to trigger circleci?17:31
TylerPearce[m]Yes! That's the plan17:32
fungii guess that also gives you the flexibility to run other jobs directly with zuul later if/when you get comfortable doing so17: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 way17:34
fungiabsolutely makes sense, yep17:34
corvusTyler 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
corvusTyler 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 gating17:37
TylerPearce[m]Thank you for suggesting that update so quickly! I appreciate all the help17:37
fungithat's definitely an interesting secondary error manifesting based on your log17:39
mordredTyler 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
fungiyeah, in theory zuul can push the predicted state to wherever the jobs are being run17:44
TylerPearce[m]I'll let you know what I come up with if (hopefully 'when') I figure it out17:44
*** holser_ is now known as holser19:28
*** dviroel|afk is now known as dviroel20:04
opendevreviewJames E. Blair proposed zuul/zuul master: Add some unit tests for the merger api  https://review.opendev.org/c/zuul/zuul/+/80239821:03
opendevreviewJames E. Blair proposed zuul/zuul master: Add some unit tests for the merger api  https://review.opendev.org/c/zuul/zuul/+/80239821:32
opendevreviewMerged zuul/zuul master: Update tutorial instructions with RAM requirement  https://review.opendev.org/c/zuul/zuul/+/80237522:03
opendevreviewJames E. Blair proposed zuul/zuul master: Shard merge request payload  https://review.opendev.org/c/zuul/zuul/+/80240322: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
opendevreviewJames E. Blair proposed zuul/zuul master: Store ephemeral waiter nodes for merger api  https://review.opendev.org/c/zuul/zuul/+/80240423:00
opendevreviewJames E. Blair proposed zuul/zuul master: Shard merger api results  https://review.opendev.org/c/zuul/zuul/+/80240523:18
opendevreviewJames E. Blair proposed zuul/zuul master: Add lost merge results cleanup method  https://review.opendev.org/c/zuul/zuul/+/80240623:18
corvusfelixedel: 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, i23:22
corvusthink 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/!