This page enumerates the known steps for the planned migration of sourceware services from the PHX2 to the RDU2 colocation facility.

Status is indicated with ☐☑☒ check boxes.

  • ☑ provision new hardware (2018-03: completed: 2 identical Dell PowerEdge R630, 2cpu*16core*2smt=64 cpus, 256GB RAM, 10*600GB HDD in RAID6)
  • ☑☑ named server2.sourceware.org and server3.sourceware.org
  • ☑☑ install centos7 (2018-03)
  • ☑☑ reinstall centos8 (2019-10-02)
  • ☑☑ install /root/.ssh/authorized_keys
  • ☑☑ firewalld setup (firewalld driving nft nftables)
  • ☑☑ fail2ban (sshd 'jail') Fail2BanPolicy
  • ☑☑ mdmonitor

Redundancy setup:

  • ☑☑ cron auto-rsync of old-sourceware payload dirs to server & server3 RedundancyPolicy
  • ☑ server2 pushing to server3 for new /sourceware and /root partitions
  • ☐ set up off-site rsync backup too

Install software to support all services: SoftwarePolicy

Switchover:

  • ☑ DNS PTR for server2/3, including ipv6
  • ☑ month of: announce switchover date
  • ☑ month of: move primary DNS service to new server
  • ☑ month of: shorten DNS TTLs
  • ☑ week of: announce outage schedule
  • ☑ day of: shut down most network services
  • ☑ day of: last mysqldump BACKUP.sh (30+ mins to generate, hours? to apply)
  • ☑ day of: remount /sourceware1 read-only on old server to freeze it during move
  • ☑ day of: last rsync
  • ☑ day of: archive last rsync copy of sourceware/root, /sourceware1 as read-only on new box
  • ☑ day of: update DNS
  • ☑ day of: give server2 the DNS A/CNAME alias of sourceware.org
  • ☑ day of: update server3->server2 local rsync
  • ☑ day of: mass rename /home/*/.qmail -> .forward
  • ☐ get remote console access
  • ☐ PROFIT