OKR 2022 update

roadmap/2022.md

@@ -84,6 +84,105 @@ TPA.
 
 (From the notes of the [2022-04-04 meeting](meeting/2022-04-04).)
 
+## Q3-Q4
+
+This update was performed by anarcat over email on 2022-10-11, and
+covers work done over Q1 to Q3 and part of Q4. It also tries to
+venture a guess as to how much of the work could actually be completed
+by the end of the year.
+
+### Improve mail services: 30%
+
+We're basically stalled on this. The hope is that TPA-RFC-31 comes
+through and we can start migrating to an external email service
+provider at some point in 2023.
+
+We did do a lot of work on improving spam filtering in RT, however. And
+a lot of effort was poured into implementing a design that would fix
+those issues by self-hosting our email (TPA-RFC-15), but that design was
+ultimately rejected.
+
+Let's call this at 30% done.
+
+### Retire old services: 50%, 66% possible
+
+SVN hasn't been retired, and we couldn't meet in Ireland to discuss
+how it could be. It's likely to get stalled until the end of the year;
+maybe a proposal could come through, but SVN will likely not get
+retired in 2022.
+
+For gitolite/gitweb, I started TPA-RFC-36 and started establishing
+requirements. The next step is to propose a draft, and just move it
+forward.
+
+For schleuder, the only blocker is the community team, there is hope we
+can retire this service altogether as well.
+
+Calling this one 50% done, with hope of getting to 2/3 (66%).
+
+### Cleanup and publish the sysadmin code base: 0%
+
+This is pretty much completely stalled, still.
+
+### Upgrade to Debian 11 "bullseye": 87.5% done, 100% possible
+
+ 1. all machines are upgraded to bullseye
+ 2. migrate to Prometheus for monitoring (or upgrade to Inciga 2)
+ 3. upgrade to Mailman 3 or retire it in favor of Discourse (!)
+
+[milestone](https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/5)
+
+Update: we're down to 12 buster machines, out of about 96 boxes total,
+which is 87.5% done. The problem is we're left with those 12 *hard*
+machines to upgrade:
+
+ * sunet cluster rebuild (4)
+ * moly machines retirement / rebuild (4)
+ * "hard" machines: alberti, eugeni, nagios, puppet (4)
+
+There can be split into buckets:
+
+ * just do it (7):
+   * sunet
+   * alberti
+   * eugeni (modulo schleuder retirement,  probably a new VM for
+     mailman? or maybe all moved to external, based on TPA-RFC-31
+     results)
+   * puppet (yes, keeping Puppet 5 for now)
+ * policy changes (2):
+   * nagios -> prometheus?
+   * schleuder/mailman retirements or rebuilds
+ * retirements (3):
+   * build-x86-XX (2)
+   * moly
+
+So there's still hope to realize at least the first key result here, and
+have 100% of the upgrades done by the end of year, assuming we can get
+the policy changes through.
+
+### Provision a new, trusted high performance cluster: 0%, 60% possible
+
+This actually unblocked recently, "thanks" to the mess at Cymru. If we
+do manage to complete this migration in 2022, it would get us up to 60%
+of this OKR.
+
+### Non-objectives
+
+None of those unplanned things were done, except the "complete email
+services" is probably going to be part of the TPA-RFC-31 spec.
+
+### Editorial note
+
+Another thing to note is that some key results were actually split
+between multiple objectives.
+
+For example, the "retire moly and move the DNS server to a new
+cluster" key result is also something that's part of the bullseye
+upgrade objectives.
+
+Not that bad, but something to keep in mind when we draft the next
+ones.
+
 # How those were established
 
 The goals were set based on a brainstorm by anarcat but that was also