Scratchpad for planning ideas for the winter-2025 migration.

Hardware resources

  • New SFC server: server1.sourceware.org: Dell R740, 1.5TB RAM, 6*3.8TB SSD, 20+core
  • Old RH servers: server2.sourceware.org, server3.sourceware.org
  • OSUOSL servers:
    • 2 x86_64 smallish servers for container builders (48G/62G mem, 260GB/450GB disk, 16/24 cores)
    • OSUOSL is offering to replace these two with one larger one. 2x28 cores (2x56 threads), 768GB RAM machine. Need to provide disks. There are 2 x NVMe M.2 slots and 6 x 2.5" SATA drive bays.
    • snapshots server (8G mem, 620GB disk, 4 cores)
    • 2 arm64 builders (16G/32G mem, 200GB/320GB disk, 8/16 cores).
  • OSPO RH VM: forge.sourceware.org (6G mem, 8GB root /, 60G data /srv, 3 cores)

Software

We wish to split the unitary sourceware.org server into multiple VMs, as practical. This will likely mean that the bare metal servers '''will not be accessible''' to the public, only the VMs they host. We wish to maintain appearance of current operation model (maintainers can direct ssh to git-push, URLs preserved, etc.).

VMs on server1

Guiding principles: no direct file sharing between/across VMs.

  • sourceware.org + gcc.gnu.org: a RHEL8? megaVM containing most current sourceware stuff; git repos, bugzilla; mysql; gitweb; postfix; rsync
    • if practical: mailman: a RHEL8 VM running mailman2 + public-inbox; postfix; mailing-list archives by git-over-inbox/http only
    • We can upgrade this to something newer if we run mailmain2 in a container
  • inbox: Provides http, imap, nntp, Needs (one) incoming email
    • Proposed VM: 8GB main distro /, 120GB lists data /srv, 16GB mem, 6 cores.
  • patchwork: Needsits own database (or access to a database VM?), (one) incoming email
    • Proposed VM (including own database): 12GB main distro OS /, 12GB patchwork data (2 GB patchwork + ?? database), 12GB mem, 4 cores
  • buildbot: (pushing bunsen data to sourceware:/git/bunsendb.git via cross-vm credential)
    • Proposed VM: 8GB main distro OS /, 30GB data /srv (14G gitpoller, + 16G sqlite state), 32GB mem, 4 cores
  • forge: maybe repatriate this from RH OSPO hosting service in entirety
    • Proposed VM: 12GB main distro OS /, 128GB data /srv (120GB forgejo repos, 8GB postgresql), 32GB mem, 8 cores
  • forge-stage: a test environment for the above

additional possible VMs:

  • bunsen: cloning bunsen data from sourceware:/git/bunsendb.git; running indexer & web-ui
    • Disk need ~140GB+ for bunsendb git and ~300GB+ for bunsenweb and ~45GB+ for bunsenql (~485GB+ total data).
  • gitweb/cgit; cloning git repos from sourceware:/git/
  • moinmoin: wikis
  • cygwin?

Services on server1 host

  • rhel10
  • no developer/project/maintainer logins at all
  • vm hosting: as above
  • vm backup: LVM snapshots of VM virtual disks
  • rsyslog or journal-remote: log collection from all the VMs; ideally even httpd logs

Services on server2 + server3

  • ?
  • LVM snapshot copies from server1

Other

See also OpenHouse2025