Document the scheduler

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A6HeySA27EkGANZN95QySW
2026-08-27 09:36:39 +02:00
parent 7d87dfffdd
commit e2f97d36e4
3 changed files with 63 additions and 7 deletions
@@ -251,6 +251,10 @@ what is wrong if not, whether it is paired with a portal and reaching it, then
 every flow with its state, its node count and whether it has unpublished
 changes, and the last few runs and failures under them.

+A `resources` line names each machine the engine can run a node on and how much
+of it is in use, plus how many nodes are queued for one. It is absent on an
+engine that accounts for nothing.
+
 The portal reads one of three ways. `no portal` means this installation was
 never enrolled. `portal hub.fluksio.com` means the link is up. `portal
 unreachable` names the error, and is the one worth acting on — the dashboard is
@@ -278,6 +282,16 @@ kB of JSON still lists as a table; `Client.runs()` is where the whole value is
 read. `--local` reads the same history from an in-process engine, without one
 having to be served.

+### `fluksio flavors`
+
+```sh
+fluksio flavors
+```
+
+The named sizes a node can ask for — `@node(resources="gpu-small")` — with the
+cores, memory and cards each stands for. Editing them is the Workers screen or
+`POST /api/v1/flavors`; this is the read.
+
 ### `fluksio sweep`

 ```sh