- plans/: mark Slate AX → SODOLA migration as Done (2026-06-02) - infrastructure/network.md: rewrite to reflect actual topology — Fritz!OS 8.x lacks second-IP-network support, so Proxmox routes between vmbr1 (192.168.178.10, uplink) and vmbr0 (192.168.8.x, internal portless bridge with 192.168.8.1 alias). Static route on Fritz!Box, no NAT on Proxmox. Technitium DHCP enabled for 192.168.8.100–240 (gateway .1, DNS .2). Caddy service unit was missing on CT 121 — recreated and enabled. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
17 lines
839 B
Markdown
17 lines
839 B
Markdown
# Plans
|
|
|
|
Pre-flight runbooks for planned changes that haven't happened yet. Once executed, move the outcome to `investigations/` (if anything interesting happened) or just a changelog entry on the affected node pages.
|
|
|
|
## Index
|
|
|
|
| Date | Title | Status |
|
|
| ---- | ----- | ------ |
|
|
| 2026-06-01 | [Slate AX → SODOLA managed switch migration](2026-06-01-slate-ax-to-sodola-migration.md) | Done |
|
|
|
|
## Conventions
|
|
|
|
- File name: `YYYY-MM-DD-<slug>.md`. Use the *target* date if known, otherwise the planning date.
|
|
- Status: `Planned` → `In Progress` → `Done` (update index entry as it moves).
|
|
- When done: add a changelog entry on every affected node page, then update status to `Done` here. If things went sideways, open an investigation.
|
|
- Plans are append-only once execution starts — don't rewrite pre-flight intent after the fact.
|