[16:04:14] jelto: https://gerrit.wikimedia.org/g/integration/zuul/deploy/+/refs/heads/master/Makefile :) [16:04:40] a Makefile that runs a container using docker-registry.wikimedia.org/python2-build [16:04:49] which results in some wheels that are bundled in a tarball [16:05:07] then for deployment, scap invokes the makefile.deploy to unbundle that tarball on the targets [16:05:17] o/ [16:05:20] o/ [16:05:29] https://gerrit.wikimedia.org/g/integration/zuul/deploy/+/refs/heads/master/Makefile :) [16:05:29] 18:04:41 <•hashar> a Makefile that runs a container using docker-registry.wikimedia.org/python2-build [16:05:30] 18:04:49 <•hashar> which results in some wheels that are bundled in a tarball [16:05:30] 18:05:07 <•hashar> then for deployment, scap invokes the makefile.deploy to unbundle that tarball on the targets [16:05:42] copy pasted that for you dduvall :b [16:05:58] ty [16:06:28] previously we deployed Zuul with a Debian package https://gerrit.wikimedia.org/r/plugins/gitiles/integration/zuul/+/refs/heads/debian/jessie-wikimedia/debian/ [16:07:11] with our patches/cherry picks in a branch managed by debian `pq` https://gerrit.wikimedia.org/r/plugins/gitiles/integration/zuul/+/refs/heads/patch-queue/debian/jessie-wikimedia [16:07:29] (`pq` in french is a short form for "toilet paper", which made it always hilarious to deal with) [16:07:42] here is the buildkitd puppet module for reference https://gerrit.wikimedia.org/r/plugins/gitiles/operations/puppet/+/refs/heads/production/modules/buildkitd/manifests/init.pp [16:08:15] I have used gbp to manage the mess + cowbuilder for the images and using our modules/package_builders deb hooks. I have learned a lot, but that was a lot of work to ship a python app :] [16:08:23] and https://gerrit.wikimedia.org/r/plugins/gitiles/operations/puppet/+/refs/heads/production/modules/buildkitd/templates/buildkitd.service.erb [16:08:54] ad the unit https://gerrit.wikimedia.org/g/operations/puppet/+/refs/heads/production/modules/buildkitd/templates/buildkitd.service.erb [16:09:34] so that is a systemd service managing `docker run`. Good to know, thanks for the link! [16:09:43] I am off, will check back later tonight [16:09:51] uses `docker run --privileged` too [16:10:14] which is definitely a special case, but one that applies to zuul-executor as well [16:10:40] i.e. give it the capabilities necessary to isolate its workloads [17:00:20] thcipriani: i was wrong about zuul-merger. the dev env does run it on the executor host, but the upstream helm chart has it deployed independently https://opendev.org/zuul/zuul-helm/src/commit/903a17974583bc2017b219113798471ce3719607/charts/zuul/templates/merger/deployment.yaml [17:03:07] oh, that's nice. gives us some flexibility about where that bit goes. [17:04:25] and that makes sense, analogous to the old-timey communication through gearman (except now, I'm guessing, it's communicating through zookeeper?) [19:49:07] quota bump is done for the Cloud VPS project [22:45:19] <3 [22:46:24] everyone has access to the zuulv3 project and I think that James should be with us Soon™ based on the last round of back and forth re:contract.