Description

As a pre-requisite, we should consider whether we want to distribute
some of its services to several other servers [1]. That'd definitely help
to split and then upgrade that node.

[1] T1166

Related Objects
Search...

Status	Assigned	Task
Migrated	gitlab-migration	T3579 Meta-task: upgrade infrastructure to Debian Bullseye
Migrated	gitlab-migration	T3808 Migrate pergamon to bullseye
Migrated	gitlab-migration	T3817 Install grafana on its own server

Event Timeline

ardumont triaged this task as Normal priority.Dec 15 2021, 10:08 AM

ardumont created this task.

ardumont mentioned this in T3579: Meta-task: upgrade infrastructure to Debian Bullseye.

It'd be nice to move grafana (which is a public-access service with a fairly large attack surface) to a separate VM that's not our (internal) puppet master.

It has a bunch of reverse proxies and direct service https hosts (jenkins, debian repo, annex.softwareheritage.org, bitbucket-archive, ...), as well, which could move to a, well, reverse proxy :-)

vsellier created subtask T3817: Install grafana on its own server.Dec 22 2021, 9:42 AM

ardumont closed this task as Resolved.Jan 4 2022, 4:08 PM

ardumont reopened this task as Open.

ardumont claimed this task.

ardumont moved this task from Component upgrades to done on the System administration board.

ardumont edited projects, added System administration; removed System administration (Component upgrades).

ardumont moved this task from done to Component upgrades on the System administration board.

ardumont edited projects, added System administration (Component upgrades); removed System administration.

ardumont removed ardumont as the assignee of this task.Jan 4 2022, 4:10 PM

vsellier closed subtask T3817: Install grafana on its own server as Resolved.Jan 14 2022, 5:13 PM

gitlab-migration changed the status of subtask T3817: Install grafana on its own server from Resolved to Migrated.Oct 19 2022, 6:05 PM