[07:57:14] <_joe_> brett: given the last time I touched my i3 configuration was 3 years ago, I can't say I share the same experience with its bugginess [08:47:20] wikibugs is down? [08:58:07] see https://phabricator.wikimedia.org/T357729 [13:07:44] cross post, sorry for the spam, Hi folks, I need some help finding someone to cover a Friday EMEA shift tomorrow, if you are available please reach out. Thank you! [22:09:13] Two questions for the room: 1) Did anyone in particular inherit the job of understanding puppet5 vs puppet7 from jbond? 2) Is there any reason to think that it's possible to install/run a puppet7 server on Buster or Bullseye, or has that only been tested on Bookworm? [22:14:05] andrewbogott I think moritz-m is probably the best person to ask...I believe puppet 7 will run fine on Bullseye, but not on Buster [22:15:25] andrewbogott: fundraising-tech runs their own puppetservers and tickets like T347353 and T345207 sound like they had puppetserver before going to bookworm [22:15:26] it's impossible to operate puppet 7 on older distros. upstream rewrite the server part entirely and switched from ruby/passenger to a new implementation written in clojure (and using jruby for various parts). packaging the entire stack in Debian was a very big task which involved packaging > 100 clojure related libraries and various other necessary depdencies [22:15:26] T347353: Upgrade Fundraising puppet servers to bookworm and puppetserver 7.x - https://phabricator.wikimedia.org/T347353 [22:15:26] T345207: Puppet 7.x support in Fundraising environment - https://phabricator.wikimedia.org/T345207 [22:16:46] for 2 basically no because, ^^^ this. for 1, id say jhathaway [22:17:28] thanks jbond and sorry for the legacy ping :) [22:17:42] no worries [22:17:57] the agent has been made to work on bullseye, though. but not for the soon-to-be-obsolete buster [22:17:58] nice to see you around jbond! 👋 [22:18:09] :) im always lurking ;) [22:18:18] cheers jbond:) [22:18:36] also the packaging is non-trivial, so it is nice to leverage the work from the debian maintainers [22:18:53] they even uploaded puppet 8 recently to experimental [22:20:18] This all fits with what I'm seeing. I need to rearrange my model of this from "upgrade cloud-vps puppet servers" to "rebuild cloud-vps puppetservers" but then we were going to have to do that eventually for bookworm anyway. [22:20:26] and agent 8.4.0 is even in sid already [22:20:32] andrewbogott: I'm also happy to join brainstorming discussions on upgrading, or provide thoughts on phab tasks [22:21:17] thanks! I think the only truly messy bit will be keeping track of puppetmaster-local changes on a dozen different servers... [22:21:38] hopefully they don't rewrite the entire puppetserver again ;( [22:21:38] jbond: architected having both 5 & 7 servers running concurrently and migrating clients piecemeal, that has worked well for us, moritzm has done the bulk of the migrations [22:21:42] in theory they're at least all in local git commits, but it might be simpler to just rsync everything rather than try to git clone [22:22:59] inflatador: they did try a rewrite everything in Go approach, but abandoned the effort [22:24:04] and they rewrote facter twice already as well: from Ruby to C++ and again in Ruby, so maybe Puppetserver 9 leaps back to ruby/passenger again, you never know :-) [22:24:24] jhathaway I'm imagining migrating all the ERBs to golang templating ;( [22:25:07] ha, they weren't that crazy [22:25:28] there's even an implementation of Ruby in Go, but don't give them any ideas... [22:25:30] * inflatador would welcome ERB or pretty much any other templating language for golang [22:26:22] golang's templating is like jq for me, I understand it only when I am working on it for a day, then it is all forgotten [22:27:56] that sounds like a good psychic defense ;P [22:28:35] I'll start telling that to myself!