Ansible configuration for the NLNOG RING: the nodes (*.ring.nlnog.net)
and the infrastructure machines (*.infra.ring.nlnog.net) that run the RING's own services.
Nodes configure themselves: each host runs ansible-pull against this repository on a
schedule (see the ansible role), so a merged commit on master rolls out by itself. The
playbooks are also runnable by hand from a checkout when you need to push a change now.
| Path | What it is |
|---|---|
playbook.yml |
The main playbook — all roles for all hosts, run by ansible-pull |
provision.yml |
First-boot provisioning of a brand-new machine (checks, vault password, base roles, reboot) |
provision-ring-user.yml |
Create a single RING user account on a node |
provision-vault-pass.yml |
(Re)distribute /root/.vaultpw to a node |
ubuntu_upgrade.yml |
Release upgrade of ring nodes |
nodes / nodes.active |
Inventory, generated by ringadmin from the RING database |
group_vars/, host_vars/ |
Per-group and per-host variables |
vault/ |
Ansible-vault encrypted secrets |
roles/ |
One directory per role; roles are attached to hosts in playbook.yml |
open-the-vault.sh |
Vault password script — decrypts vault_passphrase.gpg with your GPG key |
run_local.sh |
Run ansible-pull from the local checkout, for development |
The runbooks live in the doc/ directory of the NLNOG/nlnog-ring
repository. The ones that touch this
repo:
- add_new_machine.md
— end-to-end procedure for bringing a new node online: database registration, DNS, adding
it to the inventory here, and running
provision.ymlagainst it. - add_new_participant.md
— onboarding a new participant, including running
provision-ring-user.ymlto create their account. - delete_participant.txt — decommissioning a node and deactivating accounts; Ansible finishes the cleanup on the next run.
- software.md
— the RING apt repository on
apt.ring.nlnog.netand how to publish packages to it (see also theapt-repositoryandsoftwareroles). - make_new_vms.txt — creating a VM on a container node with libvirt, before it can be provisioned.
- hardware.md — what the infrastructure containers are and which services live where.