Page MenuHomeSoftware Heritage

Migrate pergamon to bullseye
Open, NormalPublic

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

Event Timeline

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 :-)

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 moved this task from done to Component upgrades on the System administration board.