TELEICU/Topology - Revision history

Admin: Fix bullet lists: convert - to * for proper MediaWiki unordered lists (via update-page on MediaWiki MCP Server)

2026-07-06T03:35:43Z

Fix bullet lists: convert - to * for proper MediaWiki unordered lists (via update-page on MediaWiki MCP Server)

Admin: Fix Mermaid diagram: remove

 wrapping (via update-page on MediaWiki MCP Server)

2026-07-06T03:21:59Z

Fix Mermaid diagram: remove <pre> wrapping (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 08:51, 6 July 2026
Line 32:		Line 32:
	== 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 ==

Admin: Automated edit (via update-page on MediaWiki MCP Server)

2026-07-06T03:09:28Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 08:39, 6 July 2026
Line 72:		Line 72:

	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.		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.

			{{Navbox TELEICU}}

	{{Related}}		{{Related}}

Admin: Replace ASCII topology with Mermaid diagram (via update-page on MediaWiki MCP Server)

2026-07-06T02:55:05Z

Replace ASCII topology with Mermaid diagram (via update-page on MediaWiki MCP Server)

@@ Line 32: / Line 32: @@
 == Network topology ==
-                        │   (etcd member)      │
+        CP1["CP VM 1<br/>(etcd)"]
-                        │   Cloud CP VM 2      │
+        CP3["CP VM 3<br/>(etcd)"]
 == Node communication ==

Admin: Create TELEICU topology reference page (via create-page on MediaWiki MCP Server)

2026-07-06T02:52:15Z

Create TELEICU topology reference page (via create-page on MediaWiki MCP Server)

New page

{{Doc header
|type=reference
|domain=teleicu
|title=Topology
|order=2
}}

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 ==

syntaxhighlight lang="text"
┌─────────────────────┐
│ Cloud CP VM 1 │
│ (etcd member) │
├─────────────────────┤
│ Cloud CP VM 2 │
│ (etcd member) │
├─────────────────────┤
│ Cloud CP VM 3 │
│ (etcd member) │
└──────────┬──────────┘
│
Tailscale mesh
│
┌──────────────────────┼──────────────────────┐
│ │ │
▼ ▼ ▼
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ Hub site (agent) │ │ Spoke site (agent)│ │ Spoke site (agent)│
│ K3s agent │ │ K3s agent │ │ K3s agent │
│ + middleware │ │ + middleware │ │ + middleware │
└──────────────────┘ └──────────────────┘ └──────────────────┘
syntaxhighlight

== 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.

{{Related}}

← Older revision		Revision as of 09:05, 6 July 2026
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 ==