1
1
Fork 0
mirror of https://gitlab.archlinux.org/archlinux/infrastructure.git synced 2024-05-06 07:36:28 +02:00
Official Arch Linux Infrastructure Repository
Go to file
Bartłomiej Piotrowski 0076adb1a6 plugins: add auto_tags plugin 2017-12-07 14:14:33 +01:00
group_vars Remove retired TU - Daniel Micay 2017-12-01 10:50:08 +01:00
host_vars kanboard: Update to 1.1.0 2017-12-02 17:42:13 +01:00
library dbscripts: Add module for staging directory creation 2017-01-29 18:59:58 +01:00
misc Give Jelle root permissions 2017-06-12 10:43:44 +02:00
playbooks Deploy basic config on nymeria and dragon 2017-11-20 21:32:02 +01:00
plugins/callback plugins: add auto_tags plugin 2017-12-07 14:14:33 +01:00
pubkeys Remove retired TU - Daniel Micay 2017-12-01 10:50:08 +01:00
roles kanboard: Remove composer usage 2017-12-02 17:49:34 +01:00
.gitignore plugins: add auto_tags plugin 2017-12-07 14:14:33 +01:00
.gitmodules common: Add checkservices script 2016-08-01 16:09:51 +02:00
README.md Update README regarding installation and certbot 2017-11-06 09:52:22 +01:00
ansible.cfg plugins: add auto_tags plugin 2017-12-07 14:14:33 +01:00
hosts hosts: explicitly set addresses of ind and jpn mirrors 2017-12-07 08:56:57 +01:00

Arch Infrastructure

This repository contains the complete collection of ansible playbooks and roles for the Arch Linux infrastructure.

It also contains git submodules so you have to run git submodule update --init --recursive after cloning or some tasks will fail to run.

Instructions

All systems are set up the same way. For the first time setup in the Hetzner rescue system, run the provisioning script: ansible-playbook playbooks/install-arch.yml -l $host. The provisioning script configures a sane basic systemd with sshd. By design, it is NOT idempotent. After the provisioning script has run, it is safe to reboot.

Once in the new system, run the regular playbook: ansible-playbook playbooks/$hostname.yml. This playbook is the one regularily used for adminstrating the server and is entirely idempotent.

Note about first time certificates

The first time a certificate is issued, you'll have to do this manually by yourself. First, configure the DNS to point to the new server and then run a playbook onto the server which includes the nginx role. Then on the server, it is necessary to run the following once:

certbot certonly --email webmaster@archlinux.org --agree-tos --rsa-key-size 4096 --renew-by-default --webroot -w /var/lib/letsencrypt/ -d <domain-name>

Note that some roles already run this automatically.

Note about opendkim

The opendkim DNS data has to be added to DNS manually. The roles verifies that the DNS is correct before starting opendkim.

The file that has to be added to the zone is /etc/opendkim/private/$selector.txt.

Servers

vostok

Services

  • backups

orion

Services

  • repos/sync (repos.archlinux.org)
  • sources (sources.archlinux.org)
  • archive (archive.archlinux.org)

apollo

Services

  • bbs (bbs.archlinux.org)
  • wiki (wiki.archlinux.org)
  • aur (aur.archlinux.org)
  • mailman
  • planet (planet.archlinux.org)
  • bugs (bugs.archlinux.org)
  • archweb
  • patchwork
  • projects (projects.archlinux.org)

soyuz

Services

  • build server (pkgbuild.com)
  • releng
  • torrent tracker
  • sogrep
  • /~user/ webhost
  • irc bot (phrik)
  • quassel core