Tech:Server lifecycle

This page describes the stages a Miraheze server goes through.

Requesting
Anyone from Site Reliability Engineering managing services offered by the Technical Team, such as MediaWiki Administrators and Site Reliability Engineers, can request a server. The request is ideally tracked in Phabricator, assigned to the Director of Site Reliability Engineering. If approved, they will purchase the server, or authorise a Site Reliability Engineer to do that.

Installing
These steps must be performed in order. This list is not exhaustive, but applies to all servers. Certain servers, such as Proxmox hosts, may require


 * 1) Add an entry for the server to the miraheze.org DNS zone. If possible, also setup reverse DNS for the IPs.
 * 2) Change the hostname of the server. This must be in the format .miraheze.org. If you cannot do this via the Service Provider, run the command   via the console.
 * 3) Log in via the console, KVM, or whatever it is called by the Service Provider. In most case, you have received the password via mail. Never share root passwords with other people.
 * 4) Most servers are accessible via SSH by default. In that case, you may find it easier to work via PuTTY or similar. To do that, dump the fingerprint of the SSH host key. For PuTTY,   seems to be appropriate.
 * 5) When connecting, verify the fingerprint matches. If so, you can proceed with the rest of the steps.
 * 6) Add the fingerprint to Tech:SSH fingerprints. Do this early, so you don't forget this.
 * 7) Configure the server via Puppet: Tech:Puppet

Decommissioning
TODO

Upgrade
TODO