Applies to NEW artifacts only. Existing names go on a TODO list and are
renamed opportunistically.
VM-{SITE}-{ROLE}-{NN}
SITE: IO for site-independent infra, SL for Server Linux,SW for Server Windows, RP for Raspberry Pi, PB for Proxmox Backup.ROLE: same letter codes (the role IS the type abbreviation in this scheme).NN: zero-padded sequence per role, per site.Examples:
VM-SL-00 — Server Linux, RZ, slot 00VM-SL-22 — Server Linux, Home, slot 22VM-PB-02 — Proxmox Backup, slot 02SV-IO-02 — Synology infra (the NAS)tdarr-node-{descriptor} where descriptor identifies the host:
tdarr-node-vm-sl-22 — the VM-hosted CPU nodetdarr-node-pc-rtx3060 — the Windows PC NVENC node (planned)/opt/{service}/. Each service compose has its own directory under /opt/.
Examples: /opt/wiki/, /opt/postgres/, /opt/tdarr/.
grp-{service}-{role}. Apps map by exact name match on the OAuth groups
claim. Examples: grp-wiki-admin, grp-portainer-admin, grp-proxmox-admin.
Container names match the role inside the stack. For Wiki.js: wiki-app
(no wiki-db anymore — it uses the shared postgres_production). For
Tdarr: tdarr-server, tdarr-node.
Gilt seit migration/target-architecture-2026 §1 und policies/ip-allocation-hm.
Pattern: VM-{SITE}-{ROLE}[-{TIER}]-{NN}
SITE ∈ {RZ, HM, LG}ROLE ∈ {EDGE, APP, SVC, DB, MAIL, MEDIA, GAME, DC, BACKUP, REG, BUILD, FW}TIER ∈ {PROD, STAGE} (nur wo PROD/STAGE-Trennung Sinn ergibt)NN zweistellig, paddedBeispiele: VM-RZ-SVC-PROD-01, VM-HM-EDGE-01, VM-HM-APP-STAGE-01.
Pattern: {vmname}.{site}.blackreset.internal — z. B. vm-rz-db-01.rz.blackreset.internal. (DNS-Zone wird nach DC-Migration aktiviert.)
Pattern: {role}-{service} — z. B. wiki-app, wiki-db, nc-app, nc-db, gitlab-app, homepage-app.
Das alte Schema VM-{SL,SW,RP,IO,PB}-NN ist superseded; die noch existierenden VM-SL-* VMs laufen unter dem alten Namen weiter bis Decom oder Migration.