[09:11:55] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade): Define where to hold Zuul/Nodepool configuration - https://phabricator.wikimedia.org/T397688 (10hashar) 03NEW
[14:22:12] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade): Artifact storage for updated Zuul CI - https://phabricator.wikimedia.org/T397385#10943097 (10hashar) > From the S3 point of view, Zuul would need a user account on the `apus` cluster, and it would then create the `cilogs` (or whichever name) bucket and set...
[14:24:00] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade): Artifact storage for updated Zuul CI - https://phabricator.wikimedia.org/T397385#10943105 (10hashar) Side track, Zuul has a playbook to upload to Swift: [[ https://zuul-ci.org/docs/zuul-jobs/latest/log-roles.html#role-upload-logs-swift | upload-logs-swift ]...
[14:33:52] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade): Artifact storage for updated Zuul CI - https://phabricator.wikimedia.org/T397385#10943125 (10Corvus) I believe that, in general, radosgw can support the swift object expiration header, but I don't know if support for that needs to be explicitly enabled, or...
[14:59:30] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 06collaboration-services: puppetize setup of new zuul VMs - https://phabricator.wikimedia.org/T395938#10943253 (10Corvus) Note: Zuul doesn't have the ability to use passphrases with any of the ssh keys it uses (for nodepool, or gerrit).
[15:07:36] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 10Release-Engineering-Team (Priority Backlog 📥): Experiment with Quibble job migration - https://phabricator.wikimedia.org/T392117#10943311 (10hashar) Things to tackle: * injecting dependencies (we use parameters functions) * reproducing `wmf-quibble*` us...
[15:07:44] * bd808 sees that wikibugs mysteriously started working here
[15:12:50] <hashar>	 bd808: I thought you did the magic for wikibugs!?!! :]
[15:15:11] <bd808>	 T396387 -- I had tried and then was stumped about why it wasn't working.
[15:15:12] <stashbot>	 T396387: Wikibugs not reporting Phabricator activity to #wikimedia-zuul as hoped - https://phabricator.wikimedia.org/T396387
[15:38:56] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 10Release-Engineering-Team (Priority Backlog 📥): Experiment with Quibble job migration - https://phabricator.wikimedia.org/T392117#10943458 (10thcipriani) >>! In T392117#10943311, @hashar wrote: > Things to tackle: > * injecting dependencies (we use param...
[17:53:12] <hashar>	 after talking with bd808, we can consider using WMCS for object storage
[17:53:23] <hashar>	 and I have to test out uploading using Swift rather than S3
[17:53:54] <hashar>	 I will reach out to SRE (Emperor) about storage in prod, but it is probably not a great idea to have the internal prod Ceph to be exposed publicly to the internet
[17:54:10] <hashar>	 and object storage on WMCS is already ready :]
[17:54:12] <hashar>	 stay tuned!
[17:54:38] <hashar>	 I'll also try a prototype job for MediaWiki extensions dependencies
[17:54:59] <hashar>	 aka CirrusSearch depends on Elastica
[23:36:05] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 07Upstream: terraform-provider-openstack >v3.0.0 uses a gophercloud client that does not work with WMCS Magnum APIs - https://phabricator.wikimedia.org/T397106#10945398 (10bd808) >>! In T397106#10924766, @Andrew wrote: > Opened gophercloud issue here: htt...
[23:56:05] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 13Patch-For-Review: Provision Kubernetes cluster and bastion using OpenTofu and Magnum - https://phabricator.wikimedia.org/T396936#10945434 (10bd808) >>! In T396936#10937326, @taavi wrote: > If Magnum doesn't support dual-stack clusters then I think I con...