TELEICU/Canary rollout - Revision history

Admin: Fix 3 Mermaid diagrams: remove

 wrapping (via update-page on MediaWiki MCP Server)

2026-07-06T03:22:02Z

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

← Older revision		Revision as of 08:52, 6 July 2026
Line 10:		Line 10:
	== Stages ==		== Stages ==

	<pre>
	{{#mermaid:flowchart LR		{{#mermaid:flowchart LR
	STAGING["Staging<br/>(test VMs/hardware)"]		STAGING["Staging<br/>(test VMs/hardware)"]
Line 21:		Line 20:
	REGIONAL -->\|"gate →"\| FLEET		REGIONAL -->\|"gate →"\| FLEET
	}}		}}
	</pre>

	== Gating criteria ==		== Gating criteria ==
Line 37:		Line 35:
	=== Ansible path ===		=== Ansible path ===

	<pre>
	{{#mermaid:flowchart LR		{{#mermaid:flowchart LR
	STAGING["staging branch"]		STAGING["staging branch"]
Line 48:		Line 45:
	REGIONAL -->\|"merge"\| MAIN		REGIONAL -->\|"merge"\| MAIN
	}}		}}
	</pre>

	=== NixOS path ===		=== NixOS path ===

	<pre>
	{{#mermaid:flowchart LR		{{#mermaid:flowchart LR
	STAGING["Update flake → rebuild in staging"]		STAGING["Update flake → rebuild in staging"]
Line 63:		Line 58:
	REGIONAL -->\|"gate →"\| FLEET		REGIONAL -->\|"gate →"\| FLEET
	}}		}}
	</pre>

	{{Navbox TELEICU}}		{{Navbox TELEICU}}

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

2026-07-06T03:10:00Z

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

← Older revision		Revision as of 08:40, 6 July 2026
Line 64:		Line 64:
	}}		}}
	</pre>		</pre>

			{{Navbox TELEICU}}

	{{Related}}		{{Related}}

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

2026-07-06T02:55:22Z

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

@@ Line 10: / Line 10: @@
 == Stages ==
 == Gating criteria ==
@@ Line 29: / Line 37: @@
 === Ansible path ===
 {{Related}}

Admin: Create TELEICU canary rollout flow page (via create-page on MediaWiki MCP Server)

2026-07-06T02:53:39Z

Create TELEICU canary rollout flow page (via create-page on MediaWiki MCP Server)

New page

{{Doc header
|type=flow
|domain=teleicu
|title=Canary rollout
|order=9
}}

Both migration paths use the same staged rollout process to minimize fleet-wide risk.

== Stages ==

# '''Staging''' — a small set of test VMs or spare hardware that mirrors production. Every change lands here first.
# '''Canary (1–2 sites)''' — real hospital PCs, selected from sites with tolerant operations. Changes soak here for a validation period.
# '''Regional rollout''' — one state or hub region at a time, with a gating check after each region.
# '''Fleet-wide''' — remaining sites after all regions have passed.

== Gating criteria ==

A stage must pass all checks before promoting to the next:

* All nodes report healthy to K3s control plane
* VictoriaMetrics shows no anomaly in key metrics
* Downtime classifier reports expected status (no false positives)
* Hub admin confirms no degradation in clinical workflow
* Rollback tested and confirmed working

== Per-path ==

=== Ansible path ===

# Push change to ansible repo <code>staging</code> branch → staging nodes converge on next pull
# Merge to <code>canary</code> branch → canary nodes pull and apply
# Merge to <code>regional/<state></code> branch → that state's nodes converge
# Merge to <code>main</code> → fleet-wide rollout

=== NixOS path ===

# Update flake → rebuild in staging
# For canary: <code>deploy-rs .#canary-node</code> (push) or merge to canary branch for comin
# For regional: tag a release → comin picks up the tag
# For fleet: update <code>main</code> branch of flake → all comin agents pull new generation

== Branch/tag structure ==

syntaxhighlight lang="text"
main ────────────── fleet-wide
├── regional/kerala
├── regional/maharashtra
├── …
└── canary
└── staging
syntaxhighlight

{{Related}}