chore: decommission VM 105 (docker-vpn) — reclaim 256 GB #37

cal · 2026-04-03T02:32:57Z

cal commented

2026-04-03 02:32:57 +00:00

Summary

Destroyed VM 105 (docker-vpn) on Proxmox via qm destroy 105 --purge, reclaiming 256 GB on the local-lvm thinpool
Deleted server-configs/proxmox/qemu/105.conf (VM no longer exists)
Marked docker-vpn as DECOMMISSIONED in SSH config and example docs
Updated migration results and upgrade plan to reflect completed decommission

Pre-deletion verification performed

Check	Result
Pi-hole DNS	No records point to VM 105 IP
NPM upstreams	No proxy hosts target VM 105
Proxmox firewall	No rules file (105.fw)
WireGuard/VPN	None — Mullvad VPN eliminated Dec 2025
Existing backup	None (skipped per Cal)
VM 121 (other docker-vpn)	Already removed

Test plan

qm list confirms VM 105 is gone
lvs confirms vm-105-disk-0 removed, 256 GB reclaimed
SSH config has DECOMMISSIONED marker, no active Host block

Closes #20

🤖 Generated with Claude Code

## Summary - Destroyed VM 105 (docker-vpn) on Proxmox via `qm destroy 105 --purge`, reclaiming **256 GB** on the local-lvm thinpool - Deleted `server-configs/proxmox/qemu/105.conf` (VM no longer exists) - Marked `docker-vpn` as DECOMMISSIONED in SSH config and example docs - Updated migration results and upgrade plan to reflect completed decommission ## Pre-deletion verification performed | Check | Result | |-------|--------| | Pi-hole DNS | No records point to VM 105 IP | | NPM upstreams | No proxy hosts target VM 105 | | Proxmox firewall | No rules file (105.fw) | | WireGuard/VPN | None — Mullvad VPN eliminated Dec 2025 | | Existing backup | None (skipped per Cal) | | VM 121 (other docker-vpn) | Already removed | ## Test plan - [x] `qm list` confirms VM 105 is gone - [x] `lvs` confirms `vm-105-disk-0` removed, 256 GB reclaimed - [x] SSH config has DECOMMISSIONED marker, no active Host block Closes #20 🤖 Generated with [Claude Code](https://claude.com/claude-code)

cal added 1 commit 2026-04-03 02:32:57 +00:00

chore: decommission VM 105 (docker-vpn) — reclaim 256 GB disk (#20 )

Auto-merge docs-only PRs / auto-merge-docs (pull_request) Successful in 3s

Details

04b1ef1a05

Destroyed VM 105 on Proxmox (qm destroy 105 --purge), reclaiming 256 GB
on the local-lvm thinpool. Removed stale config and updated docs to
reflect decommissioned status.

Closes #20

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Claude added the

ai-reviewing

label 2026-04-03 02:45:08 +00:00

Claude approved these changes 2026-04-03 02:46:11 +00:00

Claude left a comment

AI Code Review

Files Reviewed

networking/examples/server_inventory.yaml (modified)
networking/examples/ssh-homelab-setup.md (modified)
server-configs/proxmox/qemu/105.conf (deleted)
vm-management/proxmox-upgrades/proxmox-7-to-9-upgrade-plan.md (modified)
vm-management/wave2-migration-results.md (modified)

Findings

Correctness

All changes accurately reflect the decommission described in the PR body — VM 105 conf deleted, DECOMMISSIONED markers added consistently across networking docs, upgrade plan updated, wave2 checklist item marked complete.
The wave2-migration-results.md checklist note "VM 105 destroyed 2026-04-02, VM 121 already removed" is technically accurate but reads a little oddly against a task titled "Decommission VM 121 (docker-vpn)". A reader might be briefly confused by why a VM 121 task references VM 105. Minor clarity issue only.

Security

No issues. This is a housekeeping/documentation-only PR. No secrets exposed, no credentials touched.

Style & Conventions

DECOMMISSIONED comment style is applied consistently across all affected files.
Dates are absolute (2026-04-02), which is good for long-lived docs.
The proxmox-7-to-9-upgrade-plan.md correctly separates "Decommissioned" from "Stopped/Investigate" rather than just deleting the line, preserving historical context.

Suggestions

networking/examples/ssh-homelab-setup.md still references IP .121 in both the primary key and emergency key deployment loop examples (lines 209 and 221 in the file — for ip in 42 33 124 16 88 43 121). Someone following these examples would attempt ssh-copy-id to a now-dead host and get an error. Since this is an examples doc rather than a live script, it won't break anything, but it's worth a follow-up cleanup to remove 121 from those loops.

Verdict: APPROVED

Clean decommission with thorough pre-deletion verification documented in the PR. Changes are internally consistent across all affected files. The one missed reference (.121 in example deployment loops) is minor and in an examples-only file — doesn't block merging.

Automated review by Claude PR Reviewer

## AI Code Review ### Files Reviewed - `networking/examples/server_inventory.yaml` (modified) - `networking/examples/ssh-homelab-setup.md` (modified) - `server-configs/proxmox/qemu/105.conf` (deleted) - `vm-management/proxmox-upgrades/proxmox-7-to-9-upgrade-plan.md` (modified) - `vm-management/wave2-migration-results.md` (modified) ### Findings #### Correctness - All changes accurately reflect the decommission described in the PR body — VM 105 conf deleted, DECOMMISSIONED markers added consistently across networking docs, upgrade plan updated, wave2 checklist item marked complete. - The wave2-migration-results.md checklist note "VM 105 destroyed 2026-04-02, VM 121 already removed" is technically accurate but reads a little oddly against a task titled "Decommission VM 121 (docker-vpn)". A reader might be briefly confused by why a VM 121 task references VM 105. Minor clarity issue only. #### Security - No issues. This is a housekeeping/documentation-only PR. No secrets exposed, no credentials touched. #### Style & Conventions - DECOMMISSIONED comment style is applied consistently across all affected files. - Dates are absolute (2026-04-02), which is good for long-lived docs. - The proxmox-7-to-9-upgrade-plan.md correctly separates "Decommissioned" from "Stopped/Investigate" rather than just deleting the line, preserving historical context. #### Suggestions - `networking/examples/ssh-homelab-setup.md` still references IP `.121` in both the primary key and emergency key deployment loop examples (lines 209 and 221 in the file — `for ip in 42 33 124 16 88 43 121`). Someone following these examples would attempt `ssh-copy-id` to a now-dead host and get an error. Since this is an examples doc rather than a live script, it won't break anything, but it's worth a follow-up cleanup to remove `121` from those loops. ### Verdict: APPROVED Clean decommission with thorough pre-deletion verification documented in the PR. Changes are internally consistent across all affected files. The one missed reference (`.121` in example deployment loops) is minor and in an examples-only file — doesn't block merging. --- *Automated review by Claude PR Reviewer*

Claude added

ai-reviewed

and removed

ai-reviewing

labels 2026-04-03 02:46:16 +00:00

cal closed this pull request

2026-04-03 20:29:31 +00:00

Auto-merge docs-only PRs / auto-merge-docs (pull_request) Successful in 3s

Details