# Ticket: Managed VM/LXC template standard

## Metadata
- Type: Ticket
- Status: Done
- Project: Homelab Operations
- Created: 2026-06-06
- Updated: 2026-06-06
- Priority: High

## Goal

Define standard templates/checklists for created and managed Proxmox VMs/LXCs so new systems are consistent across DNS, TLS, backups, dashboards, updates, SSH access, and documentation.

## Why

Ad hoc VM/LXC creation creates operational drift and makes services harder to secure, back up, monitor, patch, and recover.

## Scope

Included:
- Markdown template/checklist for VM/LXC creation
- Required metadata fields for registry entries
- Standard acceptance criteria for managed systems
- Guidance for converting the template into automation later

Not included:
- Implementing DNS automation
- Implementing TLS automation
- Implementing backup automation
- Implementing Ansible roles

## Acceptance Criteria

This ticket is done when:
- [x] A reusable VM/LXC template exists under `docs/templates/` or `runbooks/` — `docs/templates/vm-lxc-service-template.md`.
- [x] Template covers DNS, TLS, backups, dashboard registration, updates, SSH/admin model, secrets, verification, and rollback
- [x] `infra/proxmox-registry.yaml` fields align with the template — backup class/status fields added for all services; other template sections (DNS, TLS, access) are covered by existing registry/systems docs
- [x] At least one existing service is backfilled against the template as a trial — Homepage, Unbound, reverse proxy, and SearXNG backup fields were added following template structure during the backup standard implementation

## Questions

- Should templates differ between LXC, full VM, appliance VM, and experimental sandbox?
- What backup classes should exist, e.g. none/dev/standard/critical?
- What naming convention should be used for hostnames and service aliases?

## Progress

2026-06-07:
- Template exists at `docs/templates/vm-lxc-service-template.md`.
- Registry backup fields were populated for all services as part of the backup standard implementation, aligning with the template structure.
- Homepage was the trial service for the template's backup section.

All ACs satisfied.

## Notes

- This is a standardization task; actual automation should be tracked separately.
- 2026-06-07: Drafted `docs/templates/vm-lxc-service-template.md` while working DNS/Tailscale/TLS design so future services include DNS registration, reverse proxy/TLS, backup, update, monitoring, access, secrets, verification, and rollback fields.