1
1
Fork 0
mirror of https://gitlab.archlinux.org/archlinux/infrastructure.git synced 2024-05-06 20:26:02 +02:00
Official Arch Linux Infrastructure Repository
Go to file
Florian Pritz 4d841c5a6f
Fix dbscripts dir generation for python3
Signed-off-by: Florian Pritz <bluewind@xinu.at>
2018-05-31 10:54:36 +02:00
group_vars Remove resigned dev - angvp 2018-05-31 10:24:06 +02:00
host_vars Update kanboard to 1.2.4 2018-05-17 10:34:00 +02:00
library Fix dbscripts dir generation for python3 2018-05-31 10:54:36 +02:00
misc Add Phillip Smith - fukawi2 to devops 2018-01-29 23:52:36 +01:00
playbooks Update soyuz' oidentd setup 2018-05-22 12:35:06 +02:00
plugins/callback plugins: add auto_tags plugin 2017-12-07 14:14:33 +01:00
pubkeys Remove resigned dev - angvp 2018-05-31 10:24:06 +02:00
roles Fix dbscripts dir generation for python3 2018-05-31 10:54:36 +02:00
.gitignore gitignore: add borg-keys 2018-01-08 07:16:22 +01:00
.gitmodules common: Add checkservices script 2016-08-01 16:09:51 +02:00
README.md README: Add updating the kernel to update steps 2018-05-29 21:46:09 +02:00
ansible.cfg plugins: add auto_tags plugin 2017-12-07 14:14:33 +01:00
hosts Manage nymeria as an archweb staging server 2018-05-01 20:46:12 +02: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.

Updating servers

The following steps should be used to update our managed servers:

  • pacman -Syu
  • manually update the kernel, since it is in IgnorePkg by default
  • sync
  • checkservices
  • reboot

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