Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

TELEICU/Topology: Difference between revisions

From OHC Network Wiki
More languages
Content deleted Content added
Fix Mermaid diagram: remove <pre> wrapping (via update-page on MediaWiki MCP Server)
Fix bullet lists: convert - to * for proper MediaWiki unordered lists (via update-page on MediaWiki MCP Server)
 
Line 14: Line 14:
1–3 virtual machines in reliable cloud environments, serving as the K3s control plane. These nodes:
1–3 virtual machines in reliable cloud environments, serving as the K3s control plane. These nodes:


- Run embedded etcd for HA control plane state
* Run embedded etcd for HA control plane state
- Host the K3s server process
* Host the K3s server process
- Are reachable over Tailscale from all spoke/hub nodes
* Are reachable over Tailscale from all spoke/hub nodes
- Run in cloud regions with stable power and internet
* Run in cloud regions with stable power and internet
- Are the management entry point for both Ansible and NixOS paths
* Are the management entry point for both Ansible and NixOS paths


=== Agent nodes (hospital sites) ===
=== Agent nodes (hospital sites) ===
Line 24: Line 24:
Every hospital PC — whether spoke or hub — runs as a K3s agent node. Each agent:
Every hospital PC — whether spoke or hub — runs as a K3s agent node. Each agent:


- Runs K3s agent process, registered to the control plane
* Runs K3s agent process, registered to the control plane
- Hosts containerized TELEICU middleware workloads
* Hosts containerized TELEICU middleware workloads
- Connects over Tailscale for all control-plane communication
* Connects over Tailscale for all control-plane communication
- Pulls its node-level configuration (Ansible pull or comin)
* Pulls its node-level configuration (Ansible pull or comin)
- Reports monitoring data to VictoriaMetrics
* Reports monitoring data to VictoriaMetrics


== Network topology ==
== Network topology ==
Line 62: Line 62:
All traffic between agent nodes and the control plane traverses Tailscale:
All traffic between agent nodes and the control plane traverses Tailscale:


- '''K3s registration''': agent → CP over Tailscale IPs
* '''K3s registration''': agent → CP over Tailscale IPs
- '''Configuration pull''': ansible-pull or comin fetches from git repo (routed through CP or directly)
* '''Configuration pull''': ansible-pull or comin fetches from git repo (routed through CP or directly)
- '''Metrics''': node → VictoriaMetrics endpoint
* '''Metrics''': node → VictoriaMetrics endpoint
- '''Incident notifications''': heartbeat missing → on-device agent classifies cause → alert routed to hub admin
* '''Incident notifications''': heartbeat missing → on-device agent classifies cause → alert routed to hub admin


== No sensitive data in this page ==
== No sensitive data in this page ==