swarm-controller: ask the builder for the archetypes again soon after a failed pass
This commit is contained in:
parent
5633107b32
commit
263b21021a
1 changed files with 116 additions and 11 deletions
|
|
@ -56,7 +56,9 @@ an archetype from any other source name.
|
|||
|
||||
1. swarm-controller asks the builder for the list on the queue subject
|
||||
`$SWARM.builder.archetypes` once the queue connects, and every 10 minutes
|
||||
after that.
|
||||
after that. The controller asks again after a pass that gets no answer or
|
||||
a failed evaluation: after 10 seconds, then 20, doubling up to 10 minutes,
|
||||
until one succeeds.
|
||||
2. The builder evaluates the `meta` of each `hyperhiveArchetypes` entry on
|
||||
its own hyperhive and nixpkgs sources, and answers with the JSON or the
|
||||
last lines `nix` printed:
|
||||
|
|
@ -76,8 +78,9 @@ an archetype from any other source name.
|
|||
|
||||
A builder host redeploy can change the list. The next pass, within 10
|
||||
minutes, picks it up. When no builder answers, the controller keeps the
|
||||
stored list and logs a warning on each pass. A swarm with no builder enabled
|
||||
shows no archetype select.
|
||||
stored list and logs a warning on each pass. A swarm whose
|
||||
builder connects after the controller has no list until a retry succeeds. A swarm with no builder enabled shows no
|
||||
archetype select.
|
||||
|
||||
The stored value:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue