# DeveloperWiki:ServerMigration

# Current setup

## luna.archlinux.org

- bbs
- wiki
- aur
- mailman

## nymeria.archlinux.org

- mail
- repos/rsync [turned off]

## dragon.archlinux.org

- backups [turned off]

## alberich.archlinux.org

- releng stuff. no idea
- tracker

## gudrun.archlinux.org

- planet [turned off]
- bugs
- archweb
- patchwork
- projects [turned off]

## gerolde.archlinux.org

## celestia.archlinux.org

- pkgbuild.com

# Desired setup

## vostok.archlinux.org (Intel Xeon E3-1245 2 x 3 TB 16GB ECC RAM)

- backups [done]

## apollo.archlinux.org ([1])

- bbs
- wiki
- aur
- mailman
- planet [done]
- bugs
- archweb
- patchwork
- projects
- mail

## soyuz.archlinux.org ([2])

NOTE: Talk to heftig about server specs before ordering.

- pkgbuild.com
- releng stuff. no idea
- tracker

## orion.archlinux.org (Intel Xeon E3-1245V2 32GB ECC 2x3TB)

- repos/rsync [done]
- sources [done]
- archive

# Plan of attack

- Get new servers (2 px61-ssd)
- Write ansible scripts for all services
- Services are to be split into 2 servers so that one is the webhost with outside-facing stuff and one is for internal stuff
- Delete all old stuff in the wiki about old setups

# misc TODO

- Run local resolving nameserver on mail server to make sure blacklist/whitelist checks are not blocked because the hetzner ns has hit some limits (install local unbound + change DNS in networkd file)

- Set up email on vostok
- Set up status backup checking script (ask Florian, simple find command) on vostok

- Set up orion
  - Migrate archive from seblu's server
  - Set up automatic updates

- Migrate patchwork. Reference: https://github.com/getpatchwork/patchwork/blob/master/docs/deployment.md
  - Add automatic updates when patches are pushed to a repo (at the bottom of the above link)

Category:

- DeveloperWiki