Vera

Ansible Fleet Provisioning

Per-machine bring-up: tailscale, services, env.

Ansible Fleet Provisioning (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-02 | Per-machine bring-up: tailscale, services, env. 1 - DEPENDENCY INSTALLATION ansible-galaxy galaxy requirements.yml collections DEPLOYMENT ansible-playbook playbooks/kevin-full-stack.yml inventory.ini infrastructure VERIFICATION molecule test molecule.yml side-effect.yml verify.yml validation 1. Install dependencies with ansible… 2. Run main deployment playbook 3. Execute molecule test suite 4. Validate deployment with side-eff… 5. Final verification of services docker-compose.yml.j2 template version: '3.8' services: emqx: image: emqx/emqx:latest ports: - "1883:1883" - "8083:8083" - "8084:8084" - "8883:8883" - "18083:18083" nginx-kevin-api.conf.j2 template server { listen 80; server_name api.kevin.local; location /api/ { proxy_pass http://127.0.0.1:8000/api/; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } The deployment playbook is highly idempotent, ensuring safe re-runs. Molecule tests cover various stages of deployment and validation. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Vera
Slug
ansible-provisioning
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
1 path
  • ansible