Plan the retirement of lizard

Riseup is working on reducing costs by transitioning to new systems. This work will still take months to complete but lizard is a 12+ year-old power-hungry machine and soon will be the oldest machine in Riseup's racks.

→ We need a plan to retire lizard.

Current specs

Lizard:

  • 2x Intel® Xeon® CPU E5-2650L v3 @ 1.80GHz (12 core, 24 threads)
  • 256 GB RAM
  • Disks:
    • 2x 465.63 GiB (in RAID 1)
    • 2x 1.82 TiB (in RAID 1)
    • 2x 3.64 TiB (in RAID 1)
    • All Samsung SSD 850 EVO (SATA)
  • Mainboard: Supermicro X10DRi

VMs

Need a new home:

VM description vCPU disk (total/used/avail GiB) mem (MiB)
apt APT repositories for dev 2 1772/1337/352 3921
apt-proxy Just an APT proxy 1 56/20/37 967
dns Primary DNS server 1 11/6/6 1469
mail MX for tails.boum.org 1 6/4/3 1973
misc Several things 1 15/7/9
puppet-git some important Git repositories 4 678/515/167 2978
rsync Rsync server and server-side mirror redirector 1 96/18/77
translate Weblate, staging website and integration with main website 4 169/79/90 7947
whisperback Bug reporting 1 9/4/6 775
www Website 4 639/513/125 1541

Summary of resources that would need to be migrated:

  • Number of VMs: 10
  • vCPU: 20
  • disk: 3.4 TiB total / 2.5 TiB used
  • mem (MiB): ~ 22 GiB

Numbers above don't include the host nor the jenkins VM that's already planned to be moved elsewhere.

FTR, already retired, moved or planned:

  • puppet: Puppet server -- Should be gone soon-ish (see %TPA-RFC-77: Tails and TPA Puppet codebase merge )
  • jenkins: Jenkins orchestrator -- Move to fsn-libvirt-01.tails.net → team#42503
  • bittorrent: Transmission for distributing Tails images -- retired → #18257 (closed)
  • gitlab-runner-3: GitLab Runner -- Move to iguana
Edited Feb 19, 2026 by zen
Assignee Loading
Time tracking Loading