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

TELEICU/Architecture overview: Difference between revisions

From OHC Network Wiki
More languages
Content deleted Content added
Create TELEICU architecture overview concept page (via create-page on MediaWiki MCP Server)
 
Fix Mermaid diagram: remove <pre> wrapping so parser function executes (via update-page on MediaWiki MCP Server)
 
(2 intermediate revisions by the same user not shown)
Line 31: Line 31:


Both paths share the same target topology: all hospital PCs become K3s agent nodes, managed from 1–3 cloud-based control plane VMs. Inter-node communication runs over Tailscale.
Both paths share the same target topology: all hospital PCs become K3s agent nodes, managed from 1–3 cloud-based control plane VMs. Inter-node communication runs over Tailscale.

== Target topology ==

{{#mermaid:flowchart TB
subgraph CP["Cloud Control Plane (1-3 VMs)"]
CP1["CP VM 1<br/>(etcd member)"]
CP2["CP VM 2<br/>(etcd member)"]
CP3["CP VM 3<br/>(etcd member)"]
end

subgraph TS["Tailscale Mesh"]
CP1 --- TS
CP2 --- TS
CP3 --- TS
end

subgraph Sites["Hospital Sites"]
direction TB
HUB["Hub Site<br/>K3s agent + middleware"]
S1["Spoke Site<br/>K3s agent + middleware"]
S2["Spoke Site<br/>K3s agent + middleware"]
S3["Spoke Site<br/>K3s agent + middleware"]
end

TS --- HUB
TS --- S1
TS --- S2
TS --- S3
}}


== Key design decisions ==
== Key design decisions ==
Line 42: Line 71:


See the [[TELEICU/Migration strategy|Migration strategy]] for the full decision framework.
See the [[TELEICU/Migration strategy|Migration strategy]] for the full decision framework.

{{Navbox TELEICU}}


{{Related}}
{{Related}}