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

Refresh Serenity placement plan after live review
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 03:48:49 +00:00
parent a17d432b0f
commit d8bdc36392
3 changed files with 106 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/planning/PD_FUTURE_STATE_ARCHITECTURE.md
View File

@@ -200,6 +200,13 @@ Optional elsewhere:
- heavy inference on Rocinante if PD does not get the 4090
- high-risk security experiments on a future dedicated lab node if the school/lab workload outgrows PD-hosted segmented VMs
### Move off Serenity early; does not need the storage cutover
- Wizarr -> PD or retire if no longer useful
- Hawser + dockersocket -> PD or retire as a pair
- netdata -> keep only where it still adds monitoring value
These are low-risk peel-off candidates because they are not part of the storage-local torrent/media locality lane.
## Cybersecurity VM model on PD
### This is acceptable on PD
@@ -251,7 +258,7 @@ Suggested policy posture:
### Phase 1: document and reduce Serenity sprawl now
- document current host roles and future-state design
- classify Serenity services into keep / move / retire
- move low-risk non-storage-tied apps off Serenity first
- move low-risk non-storage-tied apps off Serenity first (`Wizarr`, `Hawser` + `dockersocket`, and possibly `netdata`)
### Phase 2: build upgraded PD
- install TrueNAS Scale on the new PD hardware
@@ -263,6 +270,7 @@ Suggested policy posture:
- migrate any remaining general-purpose apps off Serenity
- relocate databases/appdata onto the intended SSD tier
- validate ingress, monitoring, and DNS roles
- keep `Newt`, `reranker`, and the off-PD Technitium node as explicit special cases until their redesign work is ready
### Phase 4: move the storage-dependent torrent/media automation stack
- after the storage move design is finalized, move qbit + ARR locality to PD
@@ -293,5 +301,6 @@ Suggested policy posture:
For the current Serenity Docker review, the guiding rule is:
- remove obvious sprawl from Serenity now
- peel off the miscellaneous low-risk apps before touching the storage-locality lane
- do not over-optimize the final placement around Serenity permanence
- remember that once PD directly owns the storage, the qbit/ARR locality argument flips to PD