* finish retiring old hardware (moly, [ticket 29974](https://gitlab.torproject.org/legacy/trac/-/issues/29974))
* varnish to nginx conversion (#32462)
* solr/search.tpo deployment (#33106)?
* web metrics (#32996)?
* GitLab pages hosting
* experiment with containers/kubernetes for CI/CD
* upgrade to bullseye
...
...
@@ -101,8 +99,7 @@ attention. In general, the over-arching goals are therefore:
* static mirror network retirement / rearchitecture: we want to test
out GitLab pages first and see if it can provide a decent
alternative
* TODO: "finish main website transition", "broken links on
website"... should TPA cover for web stuff?
* web development stuff: goals like "finish main website transition", "broken links on website"... should be covered in the web team, but the capacity of TPA is affected by hiro working on the web stuff
* TODO: are service admins still a thing? should we cover for things
like the metrics team?
* complete puppetization: old legacy services are not in Puppet. that
...
...
@@ -110,6 +107,8 @@ attention. In general, the over-arching goals are therefore:
services should all be built in Puppet
* replace Nagios with Prometheus: not a short term goal, no clear
benefit. reduce the noise in Nagios instead
* solr/search.tpo deployment (#33106), postponed to 2022
* web metrics (#32996), postponed to 2022
# Quarterly breakdown
...
...
@@ -745,3 +744,4 @@ was surprised to see that gitweb and git-rw are used equally by the
team, which the previous calculation told us. The new ones seem to
better reflect actual use (3 monthly, 1 weekly, 6 daily vs 1 monthly,
