Opened 7 months ago

Last modified 6 weeks ago

#29974 assigned project

move critical services off, and then replace, moly

Reported by: anarcat Owned by: anarcat
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

As part of #29817, we found out that moly.torproject.org has vastly surpassed its shelf life, having been installed in 2011. It's a big machine with multiple KVM guests, so we can't simply retire it and redistribute its guests elsewhere, at least not without filling up the rest of the infrastructure.

So we probably need to find a replacement box for moly.

Child Tickets

TicketStatusOwnerSummaryComponent
#31784assignedhiromove majus off of molyInternal Services/Tor Sysadmin Team
#31785assignedhiromove getulum off molyInternal Services/Tor Sysadmin Team
#31786closedanarcatmove dictyotum off molyInternal Services/Tor Sysadmin Team

Change History (2)

comment:1 Changed 6 weeks ago by anarcat

Owner: changed from tpa to anarcat
Status: newassigned
Summary: retire/replace molymove critical services off, and then replace, moly

we can't just retire moly: it's a critical point of presence, one of very precious places outside of Hetzner. but we might just want to replace the hardware anyways, or, in the immediate term, move critical, non n+1 services off of the machine.

this currently means migrating:

  • dictyotum
  • majus
  • getulum

those could moved off to the new FSN cluster. this does implies all our backups are in one basket, but we already have that problem as bungei is already at hetzner and holds the bulk of the information regarding backups (ie. the storage server).

comment:2 Changed 6 weeks ago by anarcat

note that the dictory server migration should be attempted using the restore procedure, see also #30880.

Note: See TracTickets for help on using tickets.