diff options
| author | tv <tv@krebsco.de> | 2026-11-05 02:27:03 +0100 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-05 02:27:03 +0100 |
| commit | c10f9144b1436d4918855a657715b453a6228a44 (patch) | |
| tree | e20badbad227b7e05e94f5f6a161854beec1bd56 /docs | |
| parent | d510e3a7b223b75b5187470432f909665b6cd967 (diff) | |
dashboard: map remake votes
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/dashboard.md | 6 | ||||
| -rw-r--r-- | docs/openapi.yaml | 4 |
2 files changed, 9 insertions, 1 deletions
diff --git a/docs/dashboard.md b/docs/dashboard.md index b7247ab..7cdc7b7 100644 --- a/docs/dashboard.md +++ b/docs/dashboard.md @@ -76,6 +76,12 @@ Every member of the swarm, by alias (or a shortened node ID): the members' clocks by more than `--clock-skew-warn`, beyond what the measurements allow. The members report their peers' clocks with their links, so this works for members this node doesn't reach itself; it needs three members compared. +* **Amber**: it coordinates a remake of this node's epoch (then also a thin amber ring + around it), or voted for one, while that remake is open: voting, or committed until + the member switched. A small amber breath as a remake is proposed (its coordinator) + and as each vote comes; a short pop once it's decided, green if committed, red if + aborted (or expired), and the nodes turn back. Of the remakes in this node's document: + every member's vote shows, as it reaches this node. * **A golden glow**, growing from it and fading, once: it just entered a new epoch (a remake, [`remakes.md`](remakes.md)). For every member that reports its links (they say its epoch), and this node's peers, as they change while the page is open: so diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 677af66..bfad909 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -756,7 +756,9 @@ paths: (the epoch the member said it is in: `generation`, `id`) and `links`, each with `peer`, `transport`, `relayed`, `down`, `rttMs`, `dormant` and `others` (the peer's other transports: `transport`, `rttMs`, `relayed`), as the member answered a LINKS; ours always, the others' while fresh) and `live` (whether the - members' links are subscribed to, `/admin/dashboard/links`). One producer + members' links are subscribed to, `/admin/dashboard/links`), and `remakes` + (those of this node's epoch: `id`, `coordinator`, `phase` as in + `/admin/remakes`, `voters` (node IDs) and `fromGeneration`, the epoch's). One producer per node makes it every 2 s while anyone looks (and for a minute after this request), subscribed to the members' links (each tells of a change as it happens; renewed every 30 s); every client gets the same. Only with the `dashboard` cargo feature. |