TELEICU/Topology: Difference between revisions
From OHC Network Wiki
More languages
More actions
Content deleted Content added
Automated edit (via update-page on MediaWiki MCP Server) |
Fix bullet lists: convert - to * for proper MediaWiki unordered lists (via update-page on MediaWiki MCP Server) |
||
| (One intermediate revision by the same user not shown) | |||
| 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 |
|||
* Host the K3s server process |
|||
* Are reachable over Tailscale from all spoke/hub nodes |
|||
* Run in cloud regions with stable power and internet |
|||
* 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 |
|||
* Hosts containerized TELEICU middleware workloads |
|||
* Connects over Tailscale for all control-plane communication |
|||
* Pulls its node-level configuration (Ansible pull or comin) |
|||
* Reports monitoring data to VictoriaMetrics |
|||
== Network topology == |
== Network topology == |
||
<pre> |
|||
{{#mermaid:flowchart TB |
{{#mermaid:flowchart TB |
||
subgraph CP["Cloud Control Plane"] |
subgraph CP["Cloud Control Plane"] |
||
| Line 58: | Line 57: | ||
TS --- SN |
TS --- SN |
||
}} |
}} |
||
</pre> |
|||
== Node communication == |
== Node communication == |
||
| Line 64: | 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 |
|||
* '''Configuration pull''': ansible-pull or comin fetches from git repo (routed through CP or directly) |
|||
* '''Metrics''': node → VictoriaMetrics endpoint |
|||
* '''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 == |
||
Latest revision as of 09:05, 6 July 2026
The target topology for the TELEICU infrastructure across all 200+ sites.
Components
Control plane (cloud VMs)
1–3 virtual machines in reliable cloud environments, serving as the K3s control plane. These nodes:
- Run embedded etcd for HA control plane state
- Host the K3s server process
- Are reachable over Tailscale from all spoke/hub nodes
- Run in cloud regions with stable power and internet
- Are the management entry point for both Ansible and NixOS paths
Agent nodes (hospital sites)
Every hospital PC — whether spoke or hub — runs as a K3s agent node. Each agent:
- Runs K3s agent process, registered to the control plane
- Hosts containerized TELEICU middleware workloads
- Connects over Tailscale for all control-plane communication
- Pulls its node-level configuration (Ansible pull or comin)
- Reports monitoring data to VictoriaMetrics
Network topology
Node communication
All traffic between agent nodes and the control plane traverses Tailscale:
- K3s registration: agent → CP over Tailscale IPs
- Configuration pull: ansible-pull or comin fetches from git repo (routed through CP or directly)
- Metrics: node → VictoriaMetrics endpoint
- Incident notifications: heartbeat missing → on-device agent classifies cause → alert routed to hub admin
No sensitive data in this page
IP addresses, subnets, DNS names, and specific cloud providers are not documented here. These are environment-specific and maintained in the deployment repository's encrypted variables.