You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,6 +101,16 @@ make example-orphans # Check for orphaned processes
101
101
make dev-down # Stop the control plane
102
102
```
103
103
104
+
### 4. Live Lab Demo
105
+
106
+
If you are on an x86_64 Linux host or nested-KVM x86_64 environment with KVM and QEMU, you can run the live lab demo which executes a KVM workload natively:
107
+
108
+
```bash
109
+
make demo-live-lab
110
+
```
111
+
112
+
For more information, see the [Live Lab Demo](docs/live-lab.md) documentation.
113
+
104
114
## Repository Layout
105
115
106
116
-`schedune-control-plane/`: The Go-based control plane, API, and orchestration logic.
Copy file name to clipboardExpand all lines: docs/index.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,4 +37,8 @@ Schedune **is not yet** capable of full workload compatibility discovery/import,
37
37
-**Lifecycle management:** Rigorous state machine with append-only traces, robust restart recovery (rehydration), and real `/proc`-backed orphan sweeping.
The `demo-live-lab` script provides an interactive demonstration of Schedune's `VirtualMachine` runtime lifecycle utilizing KVM and QEMU.
4
+
5
+
It runs locally on an x86_64 Linux host or nested-KVM x86_64 environment that possesses KVM extensions and the `qemu-system` binaries.
6
+
7
+
## What it does
8
+
9
+
The demo proves host node ingestion, runtime lifecycle, and backend readiness by completing the following sequence:
10
+
11
+
1.**Preflight Checks:** Ensures you have KVM extensions and QEMU.
12
+
2.**Environment Reset:** Drops the local state.
13
+
3.**Agent Inspect & Control Plane Start:** Scrapes host capabilities locally, generating a `node_id`, and pushes them via Schedune Intake.
14
+
4.**Artifact Creation:** Generates a 10MB empty `qcow2` image.
15
+
**Note: The demo intentionally uses an empty `qcow2` because its focus is proving the underlying KVM execution and capability engine, not booting a specific Guest OS or Application.*
16
+
5.**Explain & Predict:** Analyzes why an architecture-specific VM requiring KVM maps strictly to the local Node's Holding Pool.
17
+
6.**Validate & Dry-Run:** Confirms the Launch Specification and simulates execution.
18
+
7.**Execute:** Directly spawns a `qemu-system-*` process on the node via Schedune.
19
+
8.**Lifecycle & Readiness:** Polls until the control socket reports the virtual machine is actively listening.
20
+
9.**Trace & Events:** Shows the recorded telemetry trace and state machine events for the Launch.
21
+
10.**Termination:** Issues an API call to tear down the underlying process.
22
+
11.**Orphans:** Confirms no lingering processes exist in the Recovery engine.
0 commit comments