How Arch Linux Manage Their Servers: "Infrastructure at Arch: Making servers go brrrrr"

From LinuxReviews
Jump to navigationJump to search

Sven-Hendrik Haaase gave an enlightening talk about the servers and the infrastructure used by Arch Linux to serve packages, The Arch Linux Wiki and the rest of the services the Arch Linux team provides at the Arch Linux Conf 2020 on Saturday October 10th, 2020. The video is about 30 minutes + 15 minutes of Q&A.

written by 윤채경 (Yoon Chae-kyung)  2020-09-11 - last edited 2020-10-11. © CC BY

The video is Copyright Arch Linux. License: Creative Commons Attribution.

The Arch Linux infrastructure is mostly hosted at the German provider Hetzner using 6 bare-metal server and 17 Hetzner cloud servers. They've also got 2 other backup servers for the Borg and 5 servers sponsored by Kape.

These servers are used to host a lot of different services:

Public services:

  • Accounts (SSO/Keycloak)
  • Archive
  • AUR (aurweb)
  • BBS (fluxbb)
  • bug tracker (flyspray)
  • GitLab
  • cgit
  • IRC bot (Phrik)
  • Mailing lists (mailman)
  • main page (archweb)
  • mirrorlist (archweb)

Services for Arch staff only:

  • Build server
  • Kanboard
  • Mail servers
  • Monitoring stack (Grafana, Prometheus, Altermanager)
  • Matrix
  • Quassel

"There was no centralized server management what so ever. Basically there was just a bunch of servers, in some cases quite literally in someone else's bathroom and there was no term called "DevOps" or a Arch Linux DevOps team"

Sven-Hendrik Haaase on how Arch Linux servers were "managed" in the past.

You will enjoy watching the video above if you're curious to learn how a small group of DevOps volunteers manage all the services Arch Linux provides to Arch Linux users and non-Arch Linux usres alike using a minimal amount of servers and man-power.

(0 votes)

Add your comment
LinuxReviews welcomes all comments. If you do not want to be anonymous, register or log in. It is free.