How ataylor-us/infra works
Project type and purpose
• This is an Infrastructure-as-Code (IaC) project, using Ansible to automate configuration of a home lab:
– A hypervisor host (EL10) running multiple VMs and containers.
– A Fedora “client” VM used as the Ansible control node.
– Additional EL10 VM hosting services.
– A separate physical workstation.
• Services include reverse proxy (Caddy), backups (borgmatic), mail notifications, CalDAV/CardDAV clients, container hosts, file sync, virtualization, etc.
• Secrets are managed via Ansible Vault (backed by Bitwarden), network overlay by Tailscale.
File structure
• Top-level playbooks:
– master.yml (full run)
– playbooks/update_packages.yml, clean_packages.yml, client_sync.yml
• Inventory and variables:
– hosts.yml defines groups: container_hosts, interactive_boxes, etc.
– group_vars/ and host_vars/ contain per-group and per-host settings plus vault files.
• Roles directory:
– Dozens of roles, each encapsulating a single service or concern (e.g. reverse_proxy, backups, virtualization, notifications).
– Each role has defaults/, tasks/, handlers/, templates/ or files/.
• Configuration:
– ansible.cfg, requirements.yml (external roles), .get-vault-pass.sh, .get-become-pass.sh.
README for architecture insights
• Describes network topology:
– One hypervisor (bare-metal) running two VMs.
– Fedora VM as control node for Ansible.
– EL10 VM for extra services.
– Separate workstation.
– All hosts connected over Tailscale.
• External dependencies: Bitwarden for vault secrets, Borgbase for backups, Pushover for notifications, Tailscale auth server.
Components and interactions
1. Ansible Control Plane
– Your local machine (runs .get-become-pass.sh, .get-vault-pass.sh).
– Fedora “client” VM (inventory, group_vars, roles, master.yml).
2. Inventory / Variables store
– hosts.yml, group_vars/, host_vars/
3. Target Hosts
– Hypervisor (EL10 bare-metal)
• KVM/QEMU virtualization host
• Runs “container_hosts” group roles (containers, virtualization templates)
– VM Service Host (EL10)
• Runs Caddy reverse_proxy, backups, file_sync, feed_reader, etc.
– Workstation (interactive_boxes)
• Runs desktop-type roles: ide, editor, file_manager, email_client, pim_client
4. External Services
– Tailscale coordination server
– Bitwarden vault (secret retrieval)
– Borgbase (remote backup repo)
– Pushover (notifications)
– Control VM → hypervisor/VMs/workstation: SSH connections, Ansible playbook execution.
– Hosts ↔ Tailscale server: overlay network traffic.
– Roles/templates → local services on each host (Caddy config, system service enable/disable).
– Hosts → Borgbase: backup data push.
– Hosts → Bitwarden: vault secrets pull.
– Hosts → Pushover API: mailrise notifications.
c. Architectural patterns and design principles
– Modular role-based IaC: one role per service/concern.
– Separation of control plane (Ansible controller) vs. data plane (inventory hosts).
– Group_vars/host_vars layered configuration for environment segmentation.
– Template-driven configuration (Jinja2 templates for Caddyfiles, configs).
– Externalized secrets via Vault plugin.
d. Key technologies and frameworks
– Ansible (playbooks, roles, inventory)
– SSH for transport
– Jinja2 templating
– KVM/QEMU virtualization
– Caddy reverse proxy
– Borgmatic / Borgbase for backups
– Tailscale for mesh networking
– Bitwarden CLI for vault secrets
– Pushover API for notifications
– vdirsyncer for CalDAV/CardDAV sync