rblundon 881e2e24a8 Add shared nginx-proxy role; deploy Hermes in Docker; rename Paperclip
nginx-proxy (new role):
- Shared nginx + certbot under /opt/nginx, replacing the copies that
  lived inside the Paperclip compose project
- Apps publish via tasks_from: add_vhost (cert marker -> issue cert ->
  write vhost -> nginx -t -> reload); a vhost that fails nginx -t is
  rolled back
- Certs issued one per domain via Cloudflare DNS challenge; domains
  registered as marker files in cert-domains/; optional LE staging
- Stock nginx.conf plus conf.d (directory mounts, not single-file
  mounts); catch-all server drops unknown Host/SNI
- Containers renamed to nginx and certbot

hermes_docker (new role):
- Official Hermes image, host networking, gateway and dashboard bound
  to loopback and published through nginx-proxy
- Dashboard login via basic-auth provider, secrets from the vault
- Main model set from hermes_model (fantasmic endpoint, key from vault);
  config.yaml overrides are merged from a 0600 staged file that is
  removed afterwards, so the key never appears in a command line
- Data dir owner-only (HERMES_HOME_MODE=0700)

paperclip-docker:
- Remove nginx, certbot and docker-compose download tasks; deploy with
  community.docker.docker_compose_v2 (idempotent, remove_orphans)
- Stop passing the Cloudflare token and certbot email to the Paperclip
  container via env_file
- Bind Postgres to 127.0.0.1 (host networking exposed it on all
  interfaces); stop chowning pgdata, which the postgres image owns
- Handler recreates the paperclip service so .env changes apply
- Domain m-v.wdw-labs.cloud -> cranium-command.wdw-labs.cloud

Playbooks:
- Add day1_deploy_nginx_proxy.yml and day1_deploy_hermes_docker.yml
- deploy_paperclip_stack.yml: run nginx-proxy before paperclip-docker,
  CLI-based container checks (no Docker SDK dependency)
- Remove deploy-hermes.yml

Host vars: add nginx_proxy_certbot_email and nginx_proxy_certbot_staging
(staging stays on until the switch to real certs).
2026-09-30 23:12:40 -05:00
2026-05-26 11:48:23 -05:00
2026-03-06 23:10:56 -06:00
2026-05-25 20:21:24 -05:00
2026-05-25 20:21:24 -05:00
2026-06-29 20:55:25 -05:00
2025-03-16 19:28:01 -05:00
2026-06-29 20:49:57 -05:00

mk-labs

Automated infrastructure provisioning and configuration for a personal homelab, built on GitOps practices with clear tool responsibility boundaries.

Architecture

A single operator action — setting a VM record's status to Staged in NetBox — triggers a fully automated provisioning pipeline:

NetBox (webhook) → n8n (validate & orchestrate) → Terraform (create VM + DHCP)
                                                 → Ansible (OS config + DNS + status update)
Tool Host IP Responsibility
NetBox fire-station 10.1.71.102 Source of truth — VM records, IP allocation, VLAN data
n8n tiki-room 10.1.71.23 Event orchestration, validation, pipeline sequencing
Terraform city-hall 10.1.71.35 Proxmox VM lifecycle, Unifi DHCP reservations
Ansible / Semaphore imagineering 10.1.71.22 OS configuration, DNS records, NetBox status updates
Proxmox fantasyland 10.1.71.13 Target hypervisor

All systems on the Server Trusted VLAN (10.1.71.0/24).

Repository Structure

homelab/
├── ansible/
│   ├── inventory/          # NetBox dynamic inventory + static
│   ├── playbooks/          # Runnable playbooks (vm-provision, DNS, OS updates)
│   ├── roles/              # vm-baseline, dns-manager, common, haproxy, n8n, observer, etc.
│   ├── tasks/              # Shared includable task files
│   ├── group_vars/         # Group variable definitions
│   ├── host_vars/          # Per-host variable definitions
│   ├── templates/          # Jinja2 templates
│   └── ansible.cfg
│
├── terraform/
│   ├── proxmox/vm/         # bpg/proxmox provider — VM creation from templates
│   ├── unifi/dhcp/         # Unifi provider — DHCP static reservations on UDM Pro
│   └── dns/                # DNS record management
│
├── packer/
│   ├── ubuntu-24.04/       # Ubuntu 24.04 VM template (small → xlarge-plus sizes)
│   └── fedora-42/          # Fedora 42 VM template
│
├── n8n/
│   └── workflows/          # Exported n8n workflow JSON (vm-provisioning)
│
├── netbox/
│   └── initializers/       # Custom fields, VLANs, IP prefixes as code
│
└── docs/
    └── decisions/          # Architecture decision records

Pipeline Flow

# System Action
1 NetBox Operator sets VM status to Staged → webhook fires
2 n8n Validates payload (hostname, IP, VLAN, template, proxmox_node)
3 n8n → city-hall SSH + terraform apply — creates VM on Proxmox
4 n8n Queries Proxmox API for MAC address
5 n8n → NetBox Writes MAC to VM interface record
6 n8n → city-hall SSH + terraform apply — creates DHCP reservation on UDM Pro
7 n8n → imagineering Triggers Ansible via Semaphore API
8 Ansible OS baseline, SSH hardening, Technitium DNS A record
9 Ansible → NetBox Sets VM status to Active

On any failure, NetBox status is set to Failed. No auto-retry — operator investigates.

Hardware

  • 7× Dell 7050 SFF
  • 3× Minisforum TH60
  • 2× Minisforum MS01
  • Synology DS1621+
  • Ubiquiti UDM Pro

Software Stack

  • Virtualization: Proxmox
  • Automation: Terraform, Ansible, n8n, Semaphore
  • DNS: Technitium (authoritative), Unbound (recursive)
  • IPAM/DCIM: NetBox
  • Networking: Ubiquiti UDM Pro
  • Templates: Packer (Ubuntu 24.04, Fedora 42)

Getting Started

See docs/decisions/vm-provisioning-flow.md for the full architecture decision record.

Previous OpenShift/ACM/Fastpass content is preserved in the archive/pre-mk-labs branch.

Security

No sensitive data is stored in this repository. Secrets are managed via Ansible Vault and environment variables on pipeline hosts.


Status: 🚧 Active Development — VM Provisioning Pipeline

Last Updated: February 2026

S
Description
No description provided
Readme MIT
25 MiB
0 Stars 0 Watchers 0 Forks
Languages
Jinja 49%
HCL 24.9%
Shell 19.2%
Python 6.2%
Dockerfile 0.7%