... | ... | @@ -36,10 +36,10 @@ attention. In general, the over-arching goals are therefore: |
|
|
* [ ] setup a new MX server to receive incoming email, with
|
|
|
"real" (Let's encrypt) TLS certificates, routing to
|
|
|
"legacy" (eugeni) mail server
|
|
|
* [ ] setup submit-01 to deliver people's emails ([issue 30608](https://gitlab.torproject.org/tpo/tpa/team/-/issues/30608))
|
|
|
* [x] setup submit-01 to deliver people's emails ([issue 30608](https://gitlab.torproject.org/tpo/tpa/team/-/issues/30608))
|
|
|
* [ ] split mailing lists out of eugeni (build a new mailman 3
|
|
|
mail server?)
|
|
|
* [ ] split schleuder out of eugeni (or retire?)
|
|
|
* [ ] split schleuder out of eugeni (or retire?) ([issue](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40564))
|
|
|
* [ ] stop using eugeni as a smart host (each host sends its own
|
|
|
email, particularly RT and CiviCRM)
|
|
|
* [ ] retire eugeni (if there is really nothing else left on it)
|
... | ... | @@ -49,17 +49,20 @@ attention. In general, the over-arching goals are therefore: |
|
|
* [ ] scale GitLab with ongoing and surely expanding usage
|
|
|
* [ ] possibly split in multiple server ([#40479](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40479))
|
|
|
* [x] throw more hardware at it: resized VM twice
|
|
|
* [ ] monitoring?
|
|
|
* [ ] provide reliable and simple continuous integration services
|
|
|
* [ ] retire Jenkins (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40218)
|
|
|
* [ ] replace with GitLab CI, with Windows, Mac and Linux runners
|
|
|
* [ ] monitoring? we should monitor the runners, as they have
|
|
|
Prometheus exporters
|
|
|
* [x] provide reliable and simple continuous integration services
|
|
|
* [x] retire Jenkins (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40218)
|
|
|
* [x] ~~replace with GitLab CI, with Windows, Mac and Linux
|
|
|
runners~~ delegated to the network team (yay! self-managed
|
|
|
runners!)
|
|
|
* [x] deployed more runners, some with very specific docker configurations
|
|
|
* [ ] [fix the blog formatting and comment moderation](https://gitlab.torproject.org/tpo/web/blog-trac/-/issues/33115), possible solutions:
|
|
|
* [ ] migrate to a static website and Discourse https://gitlab.torproject.org/tpo/tpa/team/-/issues/40183 https://gitlab.torproject.org/tpo/tpa/team/-/issues/40297
|
|
|
* [x] [fix the blog formatting and comment moderation](https://gitlab.torproject.org/tpo/web/blog-trac/-/issues/33115), possible solutions:
|
|
|
* [x] migrate to a static website and Discourse https://gitlab.torproject.org/tpo/tpa/team/-/issues/40183 https://gitlab.torproject.org/tpo/tpa/team/-/issues/40297
|
|
|
* [ ] improve communications and monitoring:
|
|
|
* [x] document "downtimes of 1 hour or longer", in a status page [issue
|
|
|
40138](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40138)
|
|
|
* [ ] ~~reduce alert fatigue in Nagios~~ Nagios is going to require a redesign in 2022, even if just for upgrading it, because it is a breaking upgrade. maybe rebuild a new server with puppet or consider replacing with Prometheus + alert manager
|
|
|
* [x] ~~reduce alert fatigue in Nagios~~ Nagios is going to require a redesign in 2022, even if just for upgrading it, because it is a breaking upgrade. maybe rebuild a new server with puppet or consider replacing with Prometheus + alert manager
|
|
|
* [x] publicize debugging tools (Grafana, user-level logging in systemd
|
|
|
services)
|
|
|
* [x] encourage communication and ticket creation
|
... | ... | @@ -67,11 +70,14 @@ attention. In general, the over-arching goals are therefore: |
|
|
* [x] make a real mailing list for admins so that gaba and non-tech
|
|
|
can join ([ticket](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40548))
|
|
|
* [ ] be realistic:
|
|
|
* [ ] cover for the day-to-day routine tasks
|
|
|
* [ ] reserve time for the unexpected
|
|
|
* [x] cover for the day-to-day routine tasks
|
|
|
* [x] reserve time for the unexpected (e.g. GitLab CI migration,
|
|
|
should schedule team work)
|
|
|
* [ ] reduce expectations
|
|
|
* [ ] on budget: hosting expenses should rise outside of budget
|
|
|
(January 2020: 1050EUR/mth, January 2021: 1150EUR/mth)
|
|
|
* [x] on budget: hosting expenses shouldn't rise outside of budget
|
|
|
(January 2020: 1050EUR/mth, January 2021: 1150EUR/mth, January
|
|
|
2022: 1470EUR/mth, ~100EUR rise approved, rest is DDOS, IPv4
|
|
|
billing change)
|
|
|
|
|
|
## Nice to have
|
|
|
|
... | ... | @@ -94,9 +100,9 @@ attention. In general, the over-arching goals are therefore: |
|
|
* [ ] varnish to nginx conversion (#32462)
|
|
|
* [x] GitLab pages hosting (see [issue tpo/tpa/gitlab#91](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/91))
|
|
|
* [ ] experiment with containers/kubernetes for CI/CD
|
|
|
* [ ] upgrade to bullseye
|
|
|
* [ ] cover for some metrics services ([issue 40125](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40125))
|
|
|
* [ ] help other teams integrate their monitoring with
|
|
|
* [ ] upgrade to bullseye - a few done, 12 out of 90!
|
|
|
* [x] cover for some metrics services ([issue 40125](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40125))
|
|
|
* [x] help other teams integrate their monitoring with
|
|
|
Prometheus/Grafana (e.g. [Matrix alerts](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40216),
|
|
|
tpo/tpa/team#40089, tpo/tpa/team#40080, tpo/tpa/team#31159)
|
|
|
|
... | ... | |