[18:43:55] 10Continuous-Integration-Infrastructure (Zuul upgrade), 06collaboration-services, 13Patch-For-Review: puppetize setup of new zuul VMs - https://phabricator.wikimedia.org/T395938#12047742 (10Dzahn) 05Open→03Resolved Since we celebrated the first succesful build on new zuul - I am optimistically callin... [19:02:24] dduvall: [re upload of build logs and console] [19:02:52] on the zuul dev instance I used the Swift API, notably cause it supports marking an artifact for automatically deletion after X days [19:02:59] so we get garbage collection for free [19:03:25] the task was https://phabricator.wikimedia.org/T397385 , Matthew is on there and recommended to use S3 API instead but we would need to figure out the garbage collection [19:04:03] there are some patches I have made at https://gerrit.wikimedia.org/r/q/project:integration/config+branch:zuul3 [19:04:54] apparently I have copied the `upload-logs-swift` role in order to enable log verbosity [19:04:59] Reason for revert: no more needed after I have found the issue :) [19:05:01] :( [19:07:04] It uploaded to WMCS object storage and there is a workable config at https://gerrit.wikimedia.org/r/c/integration/config/+/1164246 [19:07:39] that is eventually passed to zuul_swift_upload.py [19:09:36] for the prod setup, from the discussion I had with Matthew on the above task we would need a bucket to be created on the `apus` cluster and have the Edge/CDN to expose the bucket [19:10:11] thus internally the object would be at https://apus.discovery.wmnet/zuul/ [19:10:32] and to be exposed somewhere such as https://zuul.wmfusercontent.org/ [20:00:50] hashar: thanks for the info on that. i tried to get what you had in the zuul3 branch into master and i remember having to update the secret. can you check out https://gerrit.wikimedia.org/r/plugins/gitiles/integration/config/+/refs/heads/master/zuul.d/secrets.yaml when you have a chance?