evangelostsak 6b81e77dc0 fix(swarm-test): deploy twice only where the drill needs it ...

The drill tears the stack down and restores the data behind it, leaving
the bring-up to whatever deploys next. A meshed round deploys once, so after
a drill nothing brought the stack back onto the recovered export -- and the
round still reported green, because the marker is asserted against the
export rather than against a running stack.

That is observed, not predicted: a meshed BookWyrm round passed with

  backup + restore DR drill took 81s (rc=0)
  ==> DR drill PASSED: ... verified on the NFS export after the update pass

and nothing after it. The cluster finished the round torn down.

A meshed round now deploys before the drill as well, and only when the drill
says it is coming. That first pass carries SWARM_DR_PREPASS, which skips the
end-to-end suites because its stack is about to be thrown away; the pass
after the drill is the full one, so the suites run once and against the
recovered stack. A round with nothing to restore still deploys exactly once.

The arguments every deploy of a round shares move into one mapping, and the
environment the drill reads into one helper, which is what keeps the file
inside the size gate after the addition.

2026-10-04 12:25:54 +02:00

..

swarm

fix(swarm-test): deploy twice only where the drill needs it

2026-10-04 12:25:54 +02:00

__init__.py

feat(swarm): swarm-aware deploy CLI with inventory-derived dep closure

2026-06-05 02:24:51 +02:00