Thursday, 2019-05-23

*** jamesmcarthur has joined #zuul00:08
*** jamesmcarthur has quit IRC00:18
*** jamesmcarthur has joined #zuul00:19
*** jamesmcarthur has quit IRC00:25
*** jamesmcarthur has joined #zuul00:52
*** jamesmcarthur has quit IRC00:58
*** jamesmcarthur has joined #zuul01:28
*** jamesmcarthur has quit IRC01:33
*** jamesmcarthur has joined #zuul01:45
*** jamesmcarthur has quit IRC01:49
*** jamesmcarthur has joined #zuul02:12
*** jamesmcarthur has quit IRC02:17
*** irclogbot_3 has quit IRC02:26
*** irclogbot_0 has joined #zuul02:30
*** jamesmcarthur has joined #zuul02:35
*** jamesmcarthur has quit IRC03:05
*** rlandy|bbl is now known as rlandy03:14
*** bhavikdbavishi has joined #zuul03:16
*** rlandy has quit IRC03:20
*** jamesmcarthur has joined #zuul03:26
*** bhavikdbavishi has quit IRC03:45
*** bhavikdbavishi has joined #zuul03:45
openstackgerritTristan Cacqueray proposed zuul/zuul master: Add nodesets API route  https://review.opendev.org/60587703:48
*** jamesmcarthur has quit IRC03:48
*** jamesmcarthur has joined #zuul03:56
*** bhavikdbavishi has quit IRC04:06
*** bhavikdbavishi has joined #zuul04:07
*** jamesmcarthur has quit IRC04:13
*** jamesmcarthur has joined #zuul04:40
*** jamesmcarthur has quit IRC04:51
*** swest has joined #zuul04:54
*** jamesmcarthur has joined #zuul04:57
*** swest has quit IRC04:59
*** swest has joined #zuul05:00
*** jamesmcarthur has quit IRC05:04
*** jamesmcarthur has joined #zuul05:12
openstackgerritFelix Schmidt proposed zuul/zuul master: Differentiate between queued and waiting jobs in zuul web UI  https://review.opendev.org/66087805:12
*** raukadah is now known as chandankumar05:25
*** saneax has joined #zuul05:28
*** zbr has joined #zuul05:34
openstackgerritFelix Schmidt proposed zuul/zuul master: Differentiate between queued and waiting jobs in zuul web UI  https://review.opendev.org/66087805:37
*** jamesmcarthur has quit IRC05:57
*** jamesmcarthur has joined #zuul05:58
openstackgerritFelix Schmidt proposed zuul/zuul master: Differentiate between queued and waiting jobs in zuul web UI  https://review.opendev.org/66087806:21
*** themroc has joined #zuul06:54
*** jamesmcarthur has quit IRC06:54
*** bjackman has joined #zuul07:01
*** themroc has quit IRC07:05
*** pcaruana has joined #zuul07:07
openstackgerritFabien Boucher proposed zuul/zuul master: Pagure driver - https://pagure.io/pagure/  https://review.opendev.org/60440407:12
*** rf0lc0 has joined #zuul07:23
*** rfolco has quit IRC07:26
*** themroc has joined #zuul07:30
*** jpena|off is now known as jpena07:45
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] zone file vaildator  https://review.opendev.org/66091607:45
*** gtema has joined #zuul07:48
*** bjackman has quit IRC07:48
*** bjackman has joined #zuul07:50
openstackgerritMarkus Hosch proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455707:50
openstackgerritMerged zuul/zuul-jobs master: Switch to TOX_CONSTRAINTS_FILE  https://review.opendev.org/65788607:51
*** themroc has quit IRC07:57
*** themroc has joined #zuul08:03
*** saneax has quit IRC08:07
*** saneax has joined #zuul08:08
*** bhavikdbavishi has quit IRC08:11
*** hashar has joined #zuul08:21
*** sanjayu_ has joined #zuul08:27
*** saneax has quit IRC08:29
*** themroc has quit IRC08:32
*** themroc has joined #zuul08:39
*** panda|rover has quit IRC08:40
*** themroc has quit IRC08:42
*** panda has joined #zuul08:42
openstackgerritFelix Schmidt proposed zuul/zuul master: Report job depedencies via MQTT reporter  https://review.opendev.org/66094008:44
openstackgerritFelix Schmidt proposed zuul/zuul master: Report job depedencies via MQTT reporter  https://review.opendev.org/66094008:47
*** themroc has joined #zuul08:48
*** bhavikdbavishi has joined #zuul08:49
*** jamesmcarthur has joined #zuul08:51
*** jangutter has joined #zuul08:54
*** jamesmcarthur has quit IRC08:55
*** bhavikdbavishi1 has joined #zuul08:59
*** bhavikdbavishi has quit IRC08:59
*** bhavikdbavishi1 is now known as bhavikdbavishi08:59
*** themroc has quit IRC09:02
*** jamesmcarthur has joined #zuul09:04
*** themroc has joined #zuul09:06
*** panda is now known as panda|rover09:11
openstackgerritFelix Schmidt proposed zuul/zuul master: Report job depedencies via MQTT reporter  https://review.opendev.org/66094009:13
*** themroc has quit IRC09:15
*** gtema has quit IRC09:15
*** gtema has joined #zuul09:16
*** themroc has joined #zuul09:17
*** electrofelix has joined #zuul09:38
*** jamesmcarthur has quit IRC09:44
*** jamesmcarthur has joined #zuul09:45
*** fbo has joined #zuul09:49
openstackgerritTristan Cacqueray proposed zuul/zuul master: trigger: add job filter event  https://review.opendev.org/63990509:54
openstackgerritTristan Cacqueray proposed zuul/zuul master: webtrigger: add initial driver and event  https://review.opendev.org/55515309:54
openstackgerritTristan Cacqueray proposed zuul/zuul master: webtrigger: add web route and rpclistener  https://review.opendev.org/55483909:54
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: add build button to trigger job  https://review.opendev.org/63571609:54
openstackgerritFelix Schmidt proposed zuul/zuul master: Show retry attempts in UI  https://review.opendev.org/66096009:57
*** jamesmcarthur has quit IRC09:58
*** jamesmcarthur has joined #zuul10:10
*** electrofelix has quit IRC10:12
*** electrofelix has joined #zuul10:13
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Zone file validation role  https://review.opendev.org/66091610:15
*** jamesmcarthur has quit IRC10:16
*** jamesmcarthur has joined #zuul10:21
openstackgerritIan Wienand proposed openstack-infra/zone-zuul-ci.org master: Add zone-check job  https://review.opendev.org/66096710:22
*** jamesmcarthur has quit IRC10:26
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Zone file validation role  https://review.opendev.org/66091610:32
*** jamesmcarthur has joined #zuul10:39
*** paladox has quit IRC10:41
*** jamesmcarthur has quit IRC10:43
*** paladox has joined #zuul10:45
openstackgerritTobias Henkel proposed zuul/zuul master: Log github requests with annotated events  https://review.opendev.org/66080010:47
openstackgerritTobias Henkel proposed zuul/zuul master: Annotate logs around build completion and cancellation  https://review.opendev.org/66080610:47
*** jamesmcarthur has joined #zuul10:48
*** jamesmcarthur has quit IRC10:52
openstackgerritFelix Schmidt proposed zuul/zuul master: Report job depedencies via MQTT reporter  https://review.opendev.org/66094010:57
*** gtema has quit IRC10:57
*** gtema has joined #zuul10:58
*** AshBullock has joined #zuul11:00
*** jpena is now known as jpena|lunch11:01
openstackgerritMark Meyer proposed zuul/zuul master: Create a basic Bitbucket event source  https://review.opendev.org/65883511:10
openstackgerritMark Meyer proposed zuul/zuul master: Upgrade formatting of the patch series.  https://review.opendev.org/66068311:10
*** jamesmcarthur has joined #zuul11:16
AshBullockHey guys, I'm trying to get the logging working with zuul from scratch guide. On my base job I have a post logging playbook as described in the logging guide here: https://zuul-ci.org/docs/zuul-jobs/log-roles.html I'm getting this ssh error: http://paste.openstack.org/show/751980/11:19
AshBullockThis is when it's trying to upload the logs from the executor box to the logging box I have provisioned. I'm using the following secrets from the add-fileserver role as shown here:   http://paste.openstack.org/show/751981/ and my playbook is shown here: http://paste.openstack.org/show/751982/11:19
AshBullockThe zuul executor is running as the zuul user, I created a zuul user on the logging box, is there any other step I am missing here?11:19
AshBullockI made sure both the fedora user and zuul user had the relevant authorised keys on the target logging box, and I can login manually via ssh using the private key from the secrets file11:21
pabelangerAshBullock: you may want to confirm your ssh_known_hosts attribute is correct on site_logs11:23
pabelangerwonder if you are getting hostkey mismatch11:23
pabelangerwhich will prevent ansible from connecting to remote node11:23
pabelangeror11:23
pabelangerdns isn't setup on zuul-executor11:23
openstackgerritFlavio Percoco proposed zuul/zuul master: Read multiple *.conf files from directory  https://review.opendev.org/66097711:24
pabelangerand cannot resolve ip-10-xxx-xx-xx.eu-west-1.compute.internal11:24
pabelangermaybe try IP address first11:24
*** AshBullock has quit IRC11:26
*** bhavikdbavishi has quit IRC11:29
*** sshnaidm|afk is now known as sshnaidm11:42
*** panda|rover is now known as panda|rover|eat11:59
tobiashclarkb or pabelanger: want to review https://review.opendev.org/616306 (tenant and project specific resource usage stats)?12:10
tobiashthat might be interesting to you as well12:11
*** gtema has quit IRC12:17
*** jamesmcarthur has quit IRC12:18
*** jamesmcarthur has joined #zuul12:18
*** rf0lc0 is now known as rfolco12:18
*** rlandy has joined #zuul12:29
*** jpena|lunch is now known as jpena12:30
*** jamesmcarthur has quit IRC12:30
*** sanjayu_ has quit IRC12:30
*** flepied has joined #zuul12:31
*** AshBullock has joined #zuul12:34
pabelangertobiash: sure, will look shortly12:34
pabelangertobiash: yah, looks extremely helpful! +212:39
pabelangerlet clarkb get some eyes on it12:39
tobiashyupp12:39
pabelangerespecially when you have to pay for nodepool resources :)12:39
*** gtema has joined #zuul12:47
*** jamesmcarthur has joined #zuul12:52
*** panda|rover|eat is now known as panda|rover13:00
*** sanjayu_ has joined #zuul13:01
*** jamesmcarthur has quit IRC13:05
*** bjackman has quit IRC13:05
*** bjackman_ has joined #zuul13:05
openstackgerritFabien Boucher proposed zuul/zuul master: Set the DiskAccountant log when size > self.limit as warning level  https://review.opendev.org/66099613:12
fboto ease grep usage in executor logs ^13:17
*** gtema has quit IRC13:27
*** bjackman_ has quit IRC13:41
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Fix case sensitivity in codeowners check  https://review.opendev.org/66100313:43
openstackgerritMerged zuul/zuul-jobs master: Zone file validation role  https://review.opendev.org/66091613:58
*** yolanda__ has joined #zuul14:02
*** yolanda__ is now known as yolanda14:03
*** pcaruana has quit IRC14:10
*** AshBullock has quit IRC14:27
*** pcaruana has joined #zuul14:29
*** gtema has joined #zuul14:32
mordredflaper87: left comment on https://review.opendev.org/#/c/66097714:57
*** sanjayu_ has quit IRC14:58
pabelangertobiash: do you have any thoughts on maybe update our quota checks in nodepool to be per nodeset, not just a node?  The issue I am seeing, since we have pretty small quota available in our nodepool regions, is when we do multi-node testing, we check provider for quota but we end up only launch 1 or 2 nodes. And the ready node is locked, for lets say 1 hours until there is more room to launch the 2nd node in the14:58
pabelangernodeset.14:58
fungiyeah, that seems like an inefficient use of resources14:59
pabelangerThis is more an optimization I think of the nodes, since that ready locked node could service another single nodeset14:59
pabelangerfungi: yah, my thoughts too.14:59
pabelangerfor now, it isn't a huge deal14:59
fungideferring a larger request which won't be fulfilled right away to that smaller requests can be served in the meantime would be tough though, because you're liable to just end up never running the jobs with the larger requests14:59
pabelangerbut something nice to have14:59
fungiwe should probably recommend a minimum quota of 2x the size of the nodeset max size limit15:01
fungior something along those lines15:01
pabelangerfungi: right, or in this case, we have more regions that do have the quota, but nodepool doesn't know about that. IIRC, the launcher won't ask if quota is available in another region right now, and release the request to it15:01
fungiahh, yeah i suppose that could be an alternative to solve the deadlock15:01
pabelangerI also think, the launcher is too aggressive at grabbing nodesets (just a guess), I was thinking we maybe could do what we do in zuul-executor when a new request comes online.  That way another launcher has an option to try the node-request.  Often, if a project has multiple multi-node jobs, they seem to all be run in the same region.  I understand that is needed for the nodeset, but a group of nodesets could15:03
pabelangerbe split up more15:03
pabelangersome sort of back-off15:03
pabelangerShrews: you likely have thoughts too^15:06
Shrewsthose ideas require fundamental changes to how nodepool works. basically a redesign15:07
Shrewsall great ideas, but not easily hackable into the current system15:08
flaper87mordred: thanks... totally missed the return15:16
*** chandankumar is now known as raukadah15:17
*** jamesmcarthur has joined #zuul15:21
*** jamesmcarthur_ has joined #zuul15:32
*** jamesmcarthur has quit IRC15:36
*** hashar has quit IRC15:42
*** themroc has quit IRC15:44
mordredShrews: jfdi15:46
mordredShrews: (that was me making a joke about the people who like to ignore design issues in favor of Writing Moar Code - but I just realized it could have come across without the humor)15:48
clarkbpabelanger: Shrews what we likely can do with less major redesign is grab request, notice we would block, release the request without adding current provider to the tried list, then block15:52
clarkbthat would allow other providers to service it but the workflow in nodepool doesn't fundamentally change.15:53
fungithough could end up indefinitely starving larger requests if there is a constant stream of smaller ones15:56
clarkbif we process them serially I don't think it would15:58
clarkbthough there is a race there if you move ahead because one provider has the lock on a request that it eventually gives us15:58
clarkbs/gives us/gives up/15:58
clarkbThis is where the request proxy idea I've had would help a lot but that is far bigger of a design change15:59
clarkbbasically don't have requests get directly handled by providers. Instead have them get delegated to providers as necessary by an intermediary15:59
clarkbthis would allow us to fifo requests always giving the next node of type foo to the next request that needs type foo nodes16:00
*** tosky has joined #zuul16:00
*** pcaruana has quit IRC16:09
*** gtema has quit IRC16:13
*** mattw4 has joined #zuul16:16
pabelangerclarkb: yah, I think that would also work16:28
pabelangeralso, just hit https://zuul-ci.org/docs/zuul/admin/components.html#attr-executor.disk_limit_per_job for first time16:29
pabelangertime to double it16:29
clarkbpabelanger: keep in mind that limit is there to prevent jobs from creating many gigs of logs/artificats16:30
clarkbyou might have a runaway job16:30
pabelangerclarkb: yah, in this case, it is ARA16:30
pabelangerbecause were generating static html to upload to swift16:31
pabelangerwe have something like 40+ plays that ansible-test is doing16:31
pabelangerso I suspect talking up a bit of space16:31
pabelangerI'd guess none of that data is compress coming back to zuul-executor16:31
pabelangershould see if I can fix that16:32
corvuspabelanger: if you change that, it will be a little tricky in that we want swift to deal with log files in their original format (though compressed in storage and transit)16:33
pabelangeryah16:33
pabelangerupping to 500MB shouldn't be a huge issue ATM16:34
corvus(in other words, we want swift to have an object called "log.txt" with content-type text/plain and content-transfer-encoding gzip, not "log.txt.gz" with content-type application/gzip)16:35
clarkbfungi: Shrews pabelanger simpler way to deal with the large requests starvation may be to record required quota for request that will cause provider to block, unlock the request, block then only unblock when you have space for that many resources?16:35
corvus(the current system of keeping things uncompressed until log upload is the easiest way of doing that)16:35
clarkbthis could still haev races depending on the state of the requests db when you unlock but at least you should have enough quota to serve a request at least as large as the one that would've caused you to block16:35
pabelangercorvus: do you have major concerns of having the nodes do the upload directly to swift? over executor? I know we'd have to share the password with the node16:36
clarkbI don't think you want those creds on the test node16:36
pabelangeryah, that's the downside16:37
*** mgoddard has quit IRC16:38
tjgreshanodepool questions appropriate on this IRC channel?16:39
*** mgoddard has joined #zuul16:39
clarkbtjgresha: yes16:40
tjgreshaso i told nodepool to keep min ready 10 - to test my hooks to my openstack provider.. so it runs the dib, uploads the image, then it spawns instances and as soon as they are done, deletes them16:43
clarkbtjgresha: as soon as what is done?16:44
tjgreshasorry soon as instances are in ready state16:44
pabelangersounds like nodepool can't reach them via SSH?16:45
pabelangermaybe check your launcher debug log16:45
*** zbr has quit IRC16:45
tjgreshaexception that is being thrown is "instance set to active before it has an IP"   -- but i wasn't sure if that was a red herring or is it was like pabelanger suggested -ssh issue16:46
tjgreshawill NP tear down an instance immediately if it can't SSH?16:47
clarkbtjgresha: not immediately. It should try to connect via ssh repeatedly up to a timeout. However if the instance is active without an IP that might be a short circuit failure16:47
pabelangeryah, maybe also attaching to incorrect network?16:48
tjgreshaits is instant teardown .. i tried adjusting the timeouts16:49
tjgreshajust on the demo-net for now.16:49
tobiashmordred: fyi, I responded on 66097716:50
mordredtobiash: thanks!16:53
tjgreshaoddly i can see some of the instances are getting IP's and even floating - yet even those get torn down..   i will poke on the ssh keys for a bit and see if that changes things..16:53
* SpamapS did too16:54
*** tjgresha has quit IRC16:55
*** tjgresha has joined #zuul16:55
pabelangertjgresha: you might want to look at your provider security rules, maybe SSH is being blocked there16:56
tjgreshapabelanger - will double check that..16:57
SpamapStjgresha:Also there are a few options for nodepool that affect how networking is handled... it might make sense to tweak them.16:59
SpamapShttps://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].pools.auto-floating-ip comes to mind17:00
*** pcaruana has joined #zuul17:00
SpamapStjgresha: ^^ also https://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].pools.networks17:00
*** AshBullock has joined #zuul17:01
AshBullockHey guys, thanks for the help earlier, I now have logs being sent from the zuul executor to the logging box, and this looks great. However the job-output.json file is blank for all jobs http://paste.openstack.org/show/751996/17:02
AshBullockwhereas the jobs-output.txt shows the whole task run as I'd expect. I expected the json file to show the verbose output of the run. Is there a setting I'm missing for the JSON file to get populated?  Thanks in advance, again !17:03
clarkbpabelanger: in write out psuedo code I've realized by idea won't solve your thing because I would still block until N node quota is available (to avoid starving larger requests)17:04
clarkbpabelanger: what my thing will do is allow other providers to pick up a request and they may not block17:04
*** armstrongs has joined #zuul17:05
*** AshBullock has quit IRC17:07
clarkbpabelanger: your thing needs the request intermediary so that it can do a straight fifo of all the nodes (though if you are single cloud provider then you may already effectively be that fifo)17:07
*** tosky has quit IRC17:08
*** tosky has joined #zuul17:12
clarkbashbullock is gone, but I don't understand how that json file could be empty unless no plays were actually run or the v2_playbook_* callbacks aren't working for some reason17:15
clarkbzuul does take different paths if setting up ara callbacks17:18
armstrongsim in ash team17:18
clarkbhowever it appends the ara callbacks to the other callbacks path17:18
armstrongsso we are running playbooks and are using ansible 2.617:18
*** jpena is now known as jpena|off17:19
armstrongsits a very simple hello world debug command at this point17:19
armstrongsbut no matter what we put the json output is empty17:20
armstrongsthe txt one is populated17:20
armstrongshow would we debug the v2_playbook_* callbacks with zuul?17:21
clarkbhrm the callbacks are installed via symlinks to zuul/ansible/base/callbacks. The link points to a valid path in the zuul tree and the stream callback is in the same dir as the json callback so I don't think it is an installation problem17:21
clarkbmordred: tobiash ^ any ideas?17:22
*** tosky has quit IRC17:22
tobiashjson output is broken for nodeless jobs17:22
*** tosky__ has joined #zuul17:23
tobiashthere had been a fix recently17:23
tobiashhttps://review.opendev.org/65980217:23
clarkbarmstrongs: ^ I guess try updating to a zuul version that includes that commit? There isn't a release that includes that commit. Will have to install from git.17:24
armstrongsZuul version: 3.8.2.dev49 f5d6b9bd17:25
armstrongsis what im on17:25
clarkbarmstrongs: that is the commit before the one that should fix your issue17:26
armstrongshaha awesome17:26
armstrongsok thanks so much again guys17:26
*** armstrongs has quit IRC17:31
*** themroc has joined #zuul17:46
pabelangerclarkb: ack18:09
pabelangerclarkb: having other providers try, could be an improvement18:10
openstackgerritTobias Henkel proposed zuul/zuul master: Allow to select the merge method in GitHub  https://review.opendev.org/61794918:10
pabelangertobiash: exciting^18:11
tobiashpabelanger: that's an old change I need to dust off18:12
tobiash(and refactor) ;)18:12
pabelangertobiash: does switching to say squash change how a dependent pipeline would work? or are we in the same boat as merge commits today18:13
*** klindgren has quit IRC18:13
tobiashpabelanger: I think it should work the same if we teach the merger how to do squash merge18:14
*** klindgren has joined #zuul18:14
tobiashpabelanger: that would be a follow-up to this then18:14
pabelangerokay, yah, that's what I was guessing too18:14
tobiashthe merger already supports different merge modes and my plan is to leverage this and plumb through to the reporter18:14
tobiashafterwards the merger can learn additonal merge modes pretty easy18:15
pabelangernice18:15
pabelangerI know there has been some ansible folks asking for squash, since that is what they are used too18:15
tobiashhowever I'm not sure if anyone uses different merge modes at all so not sure how well this is tested18:15
pabelangerwould be cool thing to say zuul now supported :)18:16
tobiashjepp18:16
*** rlandy is now known as rlandy|brb18:16
pabelangerso, I kinda hate myself for asking this, but where did we land on adding a slack reporter to zuul? eg: Along side database / email.18:17
pabelangerin the mean time, I am going to poke at SpamapS role for slack18:18
*** hashar has joined #zuul18:29
*** bjackman_ has joined #zuul18:34
*** bjackman_ has quit IRC18:41
*** rlandy|brb is now known as rlandy18:42
*** electrofelix has quit IRC18:47
openstackgerritTobias Henkel proposed zuul/zuul master: Allow to select the merge method in Github  https://review.opendev.org/61794919:06
tobiashpabelanger: this lays the foundation so we can implement rebase and squash-merge on top of that ^19:07
Shrewscorvus: I'm looking to add a test to zuul that just tests zk interaction (no need to start any daemons) but doesn't look like such unit tests currently exist. Is that correct, or am I blind?19:10
corvusShrews: i think test_nodepool does that19:17
SpamapSpabelanger: Please do! It works great, we use it every day.. just never could get a real test going.19:17
SpamapStobiash: zomg I *so* need squash merge.19:18
SpamapSour git history is... interesting.19:18
fungidoes that make some attempt at reconciling the committer and author fields?19:19
Shrewscorvus: ah so it does, but nodepool specific. Would you be opposed to a new test_zk.py unit test file for zk-only interactions?19:20
Shrewscorvus: similar to what i have in nodepool19:20
clarkbfungi: I do know that if you do it by hand it lets the person doing the merge/squash edit things which I think would make you committer at least. Not sure who becomes committer/author when done via api19:23
SpamapSworth some experimentation and assertion in the docs19:30
corvusShrews: go for it! :)19:33
openstackgerritTobias Henkel proposed zuul/zuul master: Allow to select the merge method in Github  https://review.opendev.org/61794919:33
openstackgerritTobias Henkel proposed zuul/zuul master: Allow to select the merge method in Github  https://review.opendev.org/61794919:35
openstackgerritTobias Henkel proposed zuul/zuul master: Support squash merge in Github  https://review.opendev.org/66109619:40
daniel2So it seems the way Zuul CI works is that github is suppose to send a webhook push to Zuul to trigger the tests?  Is there a way to poll for changes with Zuul?19:40
tobiashSpamapS: that adds squash merge ^19:40
corvusdaniel2: no19:42
fungithe git driver could check for updates to a branch, but wouldn't trigger on pull requests19:46
SpamapSdaniel2: it can also be triggered by a comment on a PR19:48
SpamapSbut, yeah, no webhook, no workie.19:49
SpamapSThere's a webhook proxy somewhere out there that can help if you have zuul behind draconian firewalls.19:49
clarkbgithub also publishes their IP ranges so you could punch firewall holes that are specific19:50
pabelangerWoah, if I am reading https://help.github.com/en/articles/repository-permission-levels-for-an-organization right, a new group for humans (not write access) to use labels19:58
pabelangerthat's one more step to removing write access for humans on github repos19:58
fungifilthy humans. the machines will have their day20:00
SpamapSdaniel2:https://github.com/BonnyCI/github-webhook-proxy20:01
SpamapSpabelanger:I did see that, and I'm quite happy about it.20:01
pabelangerSpamapS: yah, same. I've been asking every github human for this for a while, I am happy it has happened20:02
*** themroc has quit IRC20:07
mordredonly 8 years after we asked the first time20:15
pabelanger++20:16
*** jamesmcarthur_ has quit IRC20:16
*** tosky__ is now known as tosky20:18
daniel2SpamapS: https://github.com/stakater/GitWebhookProxy20:24
daniel2This one seems more up to date20:24
daniel2Just out of curiosity, is nodepool really only designed for OpenStack stuff?  Could it be used to build say FreeBSD nodes?20:29
mordreddaniel2: it works with openstack, ec2 and pre-built static nodes with support coming for gce and azure (hopefully)20:30
mordreddaniel2: and we have people using it to boot windows vms and network appliance vms, so I see no reason it couldn't do freebsd20:30
daniel2i guess its more of building freebsd nodes with disk image builder.20:30
clarkbI don't think anyone has added elements to do that, but I imagine it would work. Biggest gotcha is probably fs differences?20:31
mordredyah. so for that - there's still nothing stopping dib from making freebsd images - although I don't htink we have a freebsd base element20:31
clarkbso you may end up wanting to run dib on freebsd to build freebsd20:31
clarkb(because zfs and ufs on linux is weird)20:31
mordredthat said - nodepool can boot vms in clouds from already-existing images20:31
mordredso you could use an existing freebsd image - or manually upload one and then just reference that from the nodepool config if you weren't interested in making a base freebsd element in dib20:32
mordredwhich is all to say - it should TOTALLY be possible - but none of us have done it :)20:32
daniel2I might give it a try20:33
clarkbdaniel2: at a high level the way dib works is to spin up a chroot then run-parts a bunch of elements' scripts in the chroot then end with an image conversion20:33
clarkbdaniel2: I expect that with a few tweaks that would work for freebsd (at least running on freebsd too)20:33
daniel2I might look into creating a port for nodepool and disk image builder for FreeBSD this weekend.20:34
mordredcool!20:34
daniel2Probably do one for zuul too, it really shouldnt be hard because they are python applications.20:37
daniel2That makes them extremely portable.20:37
clarkbyes, though zuul (and maybe nodepool) both use a select alternative that doesn't exist on OS X iirc20:37
clarkbthat may be the other gotcha20:37
clarkbhttps://docs.python.org/3/library/select.html#select.poll20:39
clarkbinternet seems to imply that actually works on freebsd but not osx20:40
clarkbso may be fine20:40
daniel2clarkb: I wonder if some modifications can be done to use kqueue.20:40
openstackgerritDavid Shrewsbury proposed zuul/zuul master: WIP: Store hold requests in zookeeper  https://review.opendev.org/66111420:40
daniel2or kevent, im not looking much into it right this moment20:40
clarkbif select.poll works I think it is probably fine as is20:41
daniel2This should be fun.  Now I'm invested, I'm going to create FreeBSD ports (or at least try) for Zuul/Nodepool and disk image-builder20:41
daniel2If anything it will be a good learning experience.20:42
fungialso running a zuul executor on freebsd could be "interesting" as i expect bubblewrap is linux-specific so you may need to do something with a jail instead if you want to have similar protections around ansible forks20:47
*** pcaruana has quit IRC20:47
daniel2fungi: I could possibly tie it into the linux emulation20:48
fungii've been out of touch with the state of linux emulation in *bsd, didn't realize it had grown support for things like network namespaces and cgroups20:59
daniel2fungi: I'm not entirely sure, which is why I said "possibly"21:00
SpamapSI doubt diskimage-builder would work on freebsd without *heavy* modification.21:03
SpamapSUnless they have the same loopback manipulation tools.21:04
fungiloopback filesystem support is basically the same, only the names of the utilities/options and virtual devices are different21:05
fungier, loopback block storage i mean21:05
SpamapSThat's what I mean. losetup, etc. etc... lots of work to do21:08
SpamapSwhoa, they've been busy21:08
SpamapShttps://opendev.org/openstack/diskimage-builder/src/branch/master/diskimage_builder/block_device/plugin.py21:08
SpamapShttps://opendev.org/openstack/diskimage-builder/src/branch/master/diskimage_builder/block_device/level0/localloop.py probably just need to cargo-cult that21:09
*** hashar has quit IRC21:21
*** flepied has quit IRC22:57
tristanCcorvus: re: having a base job create a containers on a static host so that untrusted job run in a restricted environment similar to the nodepool runc driver (i propose we call that feature pledge like the openbsd syscall)22:58
*** panda|rover has quit IRC22:59
tristanCit seems like we can almost do that with https://review.opendev.org/590092 by having the job start with no nodeset22:59
*** panda has joined #zuul22:59
tristanChowever the issue i'm facing is taking care of abort/cancel operation that may leak contexts over time...23:00
tristanCwould it be possible to have a cleanup action performed before re-using a static node?23:00
clarkbtristanC: there has been talk of adding a cleanup run phase that always runs (before post? maybe after post?)23:02
*** tosky has quit IRC23:05
*** rlandy has quit IRC23:06
tristanCclarkb: it seems like abort/cancel operation are fire-and-forget in zuul model. Wouldn't it be more simple to implement it in nodepool side when doing the "in-used" -> "ready" transition?23:06
clarkbtristanC: we removed all of the functionality in nodepool that "managed" instances internally23:06
clarkbtristanC: because the idea was zuul could do it. Zuul mostly can except in the abort case23:07
SpamapSI'd like to see it as a distinct phase in zuul buildsets.23:07
SpamapSIdeally, zuul would always run a cleanup job after any buildset ended.23:07
SpamapSThat's not just for static nodes, it helps with anything where you need to allocate resources during jobs.23:08
clarkbSpamapS: it will have to be per job not buildset due to job retries23:08
clarkb(could possibly also have per buildset cleanups)23:08
SpamapSFor instance, I'd like to spin up an entire EKS cluster in a zuul job, to test the stuff that initializes them. I want to be 100% sure that EKS cluster is always killed, no matter what job that runs after the spin up of the cluster fails.23:08
SpamapSThe other path to that, is the idea of an ansible nodepool provider, which could do that.23:09
clarkbSpamapS: that could still be a job cleanup action in the paused job23:09
clarkb(doesn't need to be buildset)23:09
SpamapSclarkb:yeah I don't fully understand paused jobs yet.23:09
SpamapSis that spelled out? Maybe that's all I want.23:09
clarkbI think it is documented /me looks23:10
clarkbhttps://zuul-ci.org/docs/zuul/user/jobs.html#pausing-the-job23:10
corvuswhat's still missing for that use-case is something that runs if the job (the parent job -- the paused job) is aborted, say, due to a new patchset.  that's what a 'cleanup' phase would do i think.23:11
clarkbyup we need a new run phase to properly close that gap23:12
clarkb(but it doesn't need to be per buildset and I think it does need to be per job to handle retries)23:12
corvusagree23:13
openstackgerritTristan Cacqueray proposed zuul/zuul master: encrypt_secret: display the full_url on error  https://review.opendev.org/66113423:18
tristanCgreat, iiuc, a "cleanup" job attribute with a playbook that is always executed would be great for the job pledge feature23:21
corvusi think that will get us 99% of the way there, with a small hole involving executor failure -- but we can probably close that with the zuulv4/everything-in-zookeeper work23:25
openstackgerritIan Wienand proposed zuul/zuul-jobs master: validate-zone-db : add job and make more generic  https://review.opendev.org/66113823:43
SpamapScorvus:the 1% have enough money to solve it themselves.23:45
SpamapS;)23:45
SpamapSwow23:45
SpamapSthis pause thing23:45
SpamapShow did I miss that?23:45
SpamapSI've been trying to bend a bunch of jobs into weird places and all I needed was that. ;)23:46
openstackgerritIan Wienand proposed zuul/zuul-jobs master: validate-zone-db : add job and make more generic  https://review.opendev.org/66113823:49
*** mattw4 has quit IRC23:50

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!