fizzlepoof/truenas-stacks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record PD Pi-hole retirement state
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
Details
secret-guardrails / gitleaks (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Fizzlepoof
2026-05-27 20:22:07 +00:00
parent dea83b64af
commit 2ab4ff4428
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/architecture/SERVICES_DIRECTORY.md
View File

@@ -51,7 +51,7 @@ OpenClaw is no longer treated as an active PD service in the operator inventory.
| Service | Host | Port | Status | | Service | Host | Port | Status |
|---------|------|------|--------| |---------|------|------|--------|
| Technitium primary source node | PD (`10.5.30.8` via `technitium-pilot` macvlan stack) | 53 / 5380 | ✅ Active source of truth; PD root cron runs `technitium-pilot/bin/sync_backup_nodes.sh` every 15 minutes, and recent logs show successful sync + verification of Nomad (`10.5.30.9`) and Serenity (`10.5.30.10`) | | Technitium primary source node | PD (`10.5.30.8` via `technitium-pilot` macvlan stack) | 53 / 5380 | ✅ Active source of truth; PD root cron runs `technitium-pilot/bin/sync_backup_nodes.sh` every 15 minutes, and recent logs show successful sync + verification of Nomad (`10.5.30.9`) and Serenity (`10.5.30.10`) |
| Nebula Sync | PD | legacy Pi-hole-only helper | ⚠️ Not part of the active Technitium design. A stale `nebula-sync` container still exists in the old Pi-hole stack and is currently `unhealthy`; retire it with the remaining Pi-hole leftovers instead of treating it as DNS source-of-truth | | Legacy Pi-hole runtime | PD + N.O.M.A.D. | legacy resolver path (`10.5.30.53`, Pi-hole/Unbound/Keepalived) | ⚠️ Not part of the active Technitium design. PD's old Pi-hole stack (`nebula-sync`, `pihole-primary`, `unbound-pihole-primary`, `keepalived-pihole-primary`) was retired on 2026-05-27 and PD was repointed to Technitium. The legacy VIP `10.5.30.53` still answers from the surviving NOMAD Pi-hole stack (`pihole-nomad` + `unbound-pihole-nomad` + `keepalived-pihole-nomad`), so treat it as leftover legacy DNS, not source-of-truth. |
## Media (PD) ## Media (PD)

4
docs/planning/DEPLOY_PIHOLE.md
View File

@@ -1,9 +1,9 @@
# Pi-hole Deployment Plan # Pi-hole Deployment Plan
**Status:** Historical Trusted-VLAN design. PD primary is still valid, but after NOMAD moved to Servers (`10.5.30.7`) its participation in the old Trusted-side VIP `10.5.30.53` was disabled to restore correct routing. Do not reuse this document for NOMAD as-is until a same-subnet HA redesign exists. **Status:** Historical Pi-hole design. It is no longer the active DNS source of truth. PD's old primary runtime was retired on 2026-05-27 after local resolver cutover to the Technitium trio, but the legacy VIP `10.5.30.53` still survives from NOMAD's leftover Pi-hole stack. Treat this document as history/reference, not the current intended DNS architecture.
**Architecture:** 3-node HA cluster with Keepalived VIP, Unbound recursive DNS, Nebula Sync **Architecture:** 3-node HA cluster with Keepalived VIP, Unbound recursive DNS, Nebula Sync
> **Warning:** The examples below describe the original Trusted-side plan where NOMAD was `10.5.30.7` and shared VIP `10.5.30.53/24`. They are retained as historical deployment notes, not the current NOMAD runtime truth. > **Warning:** The examples below describe the original HA Pi-hole plan. Current live reality is split: PD's old Pi-hole runtime is gone, but NOMAD still has legacy Pi-hole containers and currently carries the old VIP `10.5.30.53`. Do not treat anything below as the desired current-state DNS design.
--- ---

6
docs/planning/TODO.md
View File

@@ -5,9 +5,9 @@
- [x] Regenerate N.O.M.A.D. Newt secret (was exposed in chat) — completed 2026-05-15 - [x] Regenerate N.O.M.A.D. Newt secret (was exposed in chat) — completed 2026-05-15
## Infrastructure ## Infrastructure
- [x] Deploy Pi-hole HA on PD + N.O.M.A.D. with VIP `10.5.30.53` — completed 2026-05-15; historical Trusted-VLAN design, later superseded after NOMAD moved to Servers (`10.5.30.7`) and its Trusted-side Keepalived role was disabled pending a same-subnet HA redesign; see docs/planning/DEPLOY_PIHOLE.md - [x] Deploy Pi-hole HA on PD + N.O.M.A.D. with VIP `10.5.30.53` — completed 2026-05-15; historical design later superseded by the Technitium trio. As of 2026-05-27 the PD primary runtime at `/mnt/docker-ssd/docker/compose/pihole` has been retired, while the legacy VIP still survives from NOMAD's leftover stack at `/opt/pihole-nomad`; see docs/planning/DEPLOY_PIHOLE.md
- PD primary live at `/mnt/docker-ssd/docker/compose/pihole` - PD primary retired 2026-05-27 after local resolver cutover to Technitium (`10.5.30.8/.9/.10` + `9.9.9.9`)
- NOMAD backup live at `/opt/pihole-nomad` - NOMAD legacy survivor still live at `/opt/pihole-nomad`
- RPi4 remains optional future BACKUP2 work if you want a third node later - RPi4 remains optional future BACKUP2 work if you want a third node later
- [x] Deploy Kima-Hub — completed 2026-05-06; docs/planning/DEPLOY_KIMA_HUB.md now serves as deployment/repair reference - [x] Deploy Kima-Hub — completed 2026-05-06; docs/planning/DEPLOY_KIMA_HUB.md now serves as deployment/repair reference
- [ ] Set up off-site backup for vital data (appdata, databases, config repo, photos) - [ ] Set up off-site backup for vital data (appdata, databases, config repo, photos)