|
@@ -732,7 +732,12 @@ when `[registry]` is set; without the section, builds behave as before.
|
|
|
## Power
|
|
## Power
|
|
|
|
|
|
|
|
- `off`: SSH shutdown → wait → HA `turn_off` per-node entities + cluster extras
|
|
- `off`: SSH shutdown → wait → HA `turn_off` per-node entities + cluster extras
|
|
|
-- `on`: HA `turn_on` (no SSH, requires HA config)
|
|
|
|
|
|
|
+- `on`: HA `turn_on` with **ensure-powered**: a node the caller believes down (web: last
|
|
|
|
|
+ fleet snapshot; CLI: 1.5 s TCP probe) whose plug reads on gets a **30 s plug power cycle**
|
|
|
|
|
+ (a shorter cut leaves the PSU rail energized — the machine stays in soft-off). Each node's
|
|
|
|
|
+ outcome becomes the job message (web) / log lines (CLI)
|
|
|
|
|
+- jobs: the web registry persists to `web-jobs.json` next to the global config; jobs that
|
|
|
|
|
+ were running at shutdown are marked failed with a `sm121 runlock list` hint
|
|
|
- `switch --from <src> --to <tgt>`: disable nodes/extras unique to `from`, enable all in `to`
|
|
- `switch --from <src> --to <tgt>`: disable nodes/extras unique to `from`, enable all in `to`
|
|
|
|
|
|
|
|
### RouterOS devices (`[mikrotik]` config)
|
|
### RouterOS devices (`[mikrotik]` config)
|
