slides(tappaas): swap the cable-pull for a live node-failure demo
All checks were successful
Build docs site / build (push) Successful in 45s
Build slides / build (push) Successful in 1m4s

The cable-pull needs the basement, so it becomes the recorded version and the
live demo is an HA failover instead: tappaas1 carries vm:110 (firewall),
vm:130 (mothership) and vm:140 (identity), all fenced and watchdog armed.
Verified against ha-manager on the cluster.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Lars Rossen 2026-08-27 15:04:00 +02:00
parent f4f9b2a81b
commit a6e37ccd77

View file

@ -348,18 +348,26 @@ that fits under a desk. This is a genuinely new thing as of this year.
## The demo I have been waiting a year to do
<br>
# Pull the cable out.
<br>
Then ask it something.
**But we cannot do that here today.** So instead — **let us kill a node.**
`tappaas1` is running the firewall (`vm:110`), the mothership (`vm:130`)
and identity (`vm:140`) — all HA, fenced, watchdog armed.
I cut its power. They come back on another box.
<!--
DEMO. Physically unplug the uplink. Visible. Then a real question in OpenWebUI.
Have a screen-recorded fallback ready — the tent's projector will betray you.
If it works live, this is the moment of the talk. Do not rush it.
The cable-pull needs the basement, so it is the screen recording today.
LIVE DEMO instead: `ha-manager status` first, so the tent sees the three
services sitting on tappaas1. Then pull tappaas1's power.
Be honest that this drops the firewall — the whole site goes dark for the
fencing timeout before the services restart elsewhere. That pause IS the
demo; narrate it rather than filling it.
`ha-manager status` again to show them landed on another node.
Checked 15:02 today: quorum OK, master tappaas3, fencing armed.
-->
---