docs/tailnet-services.md missing critical topology details (IPs, ports, compose locations, backup procedures) #7

New issue

Closed

opened 2026-05-09 00:19:44 +00:00 by Mark · 1 comment

Mark commented

2026-05-09 00:19:44 +00:00

Owner

Bug

Date: 2026-05-08
Severity: Medium (operational gaps)

Summary

docs/tailnet-services.md has several gaps that make it unreliable for operations:

1. Missing IPs and Ports

Field	Current Value	Problem
zsus IP	`-`	Blank — cannot SSH/access zsus
LDR port	`-`	Blank — cannot reach LDR
n8n port	`-`	Blank — cannot reach n8n
zbook hardware	`-`	Blank — unknown GPU/specs
unstable hardware	`-`	Blank— unknown GPU/specs for vllm_mm node

2. No docker-compose file locations

Key question: "Where does each service's compose file live?" Currently undocumented for:

Forgejo
Hindsight (API + Control Plane)
OpenWebUI
LDR
n8n
nodehub
vLLM backend

3. No backup/restore procedures

Critical services with no documented backup strategy:

Forgejo repositories (Git data, issues, DB)
Hindsight memory banks
OpenWebUI conversation history
n8n workflows

4. No network topology diagram

Text-only table format lacks:

Service dependency graph (e.g., nodehub depends on ???)
Traffic flow between services
TLS/SSL termination points

5. Unknown roles

kimiclaw — listed as "OpenClaw client (not a server)" but role unclear
znode-tx — listed as "Unknown"
wrkstn-lp-2 — offline, no context
CachyOS — offline, no context

6. Potential port contradiction

vLLM default port is 8000, but doc says "vLLM backend (11434)" and "Backend port: 11434 (vLLM)". Port 11434 is the Ollama standard port. Either the doc is wrong or vLLM is proxied through an Ollama-compatible adapter. Should clarify.

Suggested Fix

Audit each host and fill in blanks. Add sections for:

Compose file locations per service
Backup procedures (what, where, how often)
Dependency graph
Resolve unknown/offline hosts or remove them
Clarify whether port 11434 is vLLM or an Ollama proxy to vLLM

Tags

#infrastructure #docs #topology

## Bug **Date:** 2026-05-08 **Severity:** Medium (operational gaps) ## Summary `docs/tailnet-services.md` has several gaps that make it unreliable for operations: ### 1. Missing IPs and Ports | Field | Current Value | Problem | |-------|---------------|---------| | zsus IP | `-` | Blank — cannot SSH/access zsus | | LDR port | `-` | Blank — cannot reach LDR | | n8n port | `-` | Blank — cannot reach n8n | | zbook hardware | `-` | Blank — unknown GPU/specs | | unstable hardware | `-` | Blank— unknown GPU/specs for vllm_mm node | ### 2. No docker-compose file locations Key question: "Where does each service's compose file live?" Currently undocumented for: - Forgejo - Hindsight (API + Control Plane) - OpenWebUI - LDR - n8n - nodehub - vLLM backend ### 3. No backup/restore procedures Critical services with no documented backup strategy: - Forgejo repositories (Git data, issues, DB) - Hindsight memory banks - OpenWebUI conversation history - n8n workflows ### 4. No network topology diagram Text-only table format lacks: - Service dependency graph (e.g., nodehub depends on ???) - Traffic flow between services - TLS/SSL termination points ### 5. Unknown roles - `kimiclaw` — listed as "OpenClaw client (not a server)" but role unclear - `znode-tx` — listed as "Unknown" - `wrkstn-lp-2` — offline, no context - `CachyOS` — offline, no context ### 6. Potential port contradiction vLLM default port is 8000, but doc says "vLLM backend (11434)" and "Backend port: 11434 (vLLM)". Port 11434 is the Ollama standard port. Either the doc is wrong or vLLM is proxied through an Ollama-compatible adapter. Should clarify. ## Suggested Fix Audit each host and fill in blanks. Add sections for: - Compose file locations per service - Backup procedures (what, where, how often) - Dependency graph - Resolve unknown/offline hosts or remove them - Clarify whether port 11434 is vLLM or an Ollama proxy to vLLM ## Tags #infrastructure #docs #topology