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

Update Serenity migration plan with live execution 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-26 15:48:34 +00:00
parent 186e6b1cc4
commit 1dddcbd37d
1 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/planning/SERENITY_MAJORITY_MIGRATION_PLAN.md
View File

@@ -4,6 +4,25 @@ Status: approved planning baseline for the post-D7 Serenity drain strategy.
Last updated: 2026-05-26 Last updated: 2026-05-26
## Execution update — 2026-05-26
Completed live:
- `Wizarr` retired from Serenity runtime
- stale Pangolin frontend for `wizarr.paccoco.com` disabled; public hostname now returns `404` instead of fronting a dead service
- `Hawser` + `dockersocket` verified live and healthy on Serenity
- `Notifiarr` re-evaluated against live PD headroom and intentionally left on Serenity for now
- `netdata` re-evaluated and kept on Serenity for now as host-local monitoring, not as an early migration target
Current blockers verified live:
- PD is still RAM-constrained (`31 GiB total`, `27 GiB used`, `2.3 GiB free` at check time)
- PD still consumes Serenity storage over NFS (`/mnt/unraid/data` and `/mnt/unraid/immich` mounted from `10.5.30.5`)
- backup-DNS replacement is still only a target direction in docs; no Pi 4B resolver lane is live yet
- Serenity-local `Newt` is still part of the current Pangolin path for Serenity resources, so the special-case access lane is not retired yet
Interpretation:
- The no-regret cleanup phase is complete.
- The majority migration phase remains blocked on future infrastructure work, not on missed low-risk cleanup.
## Goal ## Goal
Move the majority of remaining Docker workload off Serenity without recreating NFS/path-locality pain, while preserving the few roles that still legitimately need to live there until later infrastructure work is complete. Move the majority of remaining Docker workload off Serenity without recreating NFS/path-locality pain, while preserving the few roles that still legitimately need to live there until later infrastructure work is complete.