[13:55:13] <hashar>	 dduvall: thcipriani: about "Build zuul images for production"  https://phabricator.wikimedia.org/T396245
[13:55:13] <hashar>	 wouldn't it be possible to import upstream images to our registry?
[13:55:26] <hashar>	 I don't know how that was done for Buildkit
[14:06:19] <thcipriani>	 pretty sure we also build buildkit (tho that may be for patches)
[15:24:31] <jelto>	 We have a fork/mirror for buildkit https://gitlab.wikimedia.org/repos/releng/buildkit and build the image in GitLab
[16:57:25] <hashar>	 :)
[18:07:04] <hashar>	 I have talked with James about: the migration script they wrote, jobs secrets, uploading doc and variables/inheritance of jobs
[18:07:05] <hashar>	 :)
[18:07:38] <hashar>	 I might do a Quibble job this week, it is definitely doable, Ahmon did in a previous experiment a while back
[18:08:25] <hashar>	 ---
[18:09:09] <hashar>	 on other news we will need storage to store artifacts (eg test results, log files etc) and I am not sure what is available to us
[18:09:52] <hashar>	 we have Swift for the wiki images/thumbnails etc maybe a container can be added
[18:10:16] <hashar>	 but maybe we nowadays have another storage system exposing a S3 API?
[20:23:24] <bd808>	 There is a S3 bucket system in WMCS that we could probably use if there isn't a better prod home. -- https://wikitech.wikimedia.org/wiki/Help:Object_storage_user_guide
[23:02:31] <bd808>	 T396540 is my new task asking for the `zuul-runners` Cloud VPS project.
[23:02:32] <stashbot>	 T396540: Request creation of zuul-runners VPS project - https://phabricator.wikimedia.org/T396540
[23:02:56] * bd808 needs to figure out why wikibugs is not announcing things here