about summary refs log tree commit diff
path: root/test/python/server_test_case.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-10-24 10:35:32 +0000
committerPjotr <wrk@bosa.lan>2026-10-24 10:35:32 +0000
commitedba19046cdc6d75205d966fab8d1c4d94c19953 (patch)
treea4ce4145541337e07af647fe3534757f14476408 /test/python/server_test_case.py
parenta7ffb1cfecbdb8ac3fcc6286d7a09f7285c95d67 (diff)
downloadgenenetwork4-edba19046cdc6d75205d966fab8d1c4d94c19953.tar.gz
cwl: Document how a ravanan+Guix+Slurm request actually travels.
cwl/README.md explains the whole path (API -> ccwl compile -> ravanan ->
slurmrestd -> slurmd), where Guix sits (front end only: nodes just need
the same /gnu/store mounted, plus bash, a writable ravanan store for
data/logs, and scratch for the job's working directory), the two caches
(ravanan's work reuse, checked before submitting; gemma-wrapper's
per-chromosome --cache-dir, inside the job) and why the latter is what
actually saves work for this endpoint.

It also answers "can the nodes rebuild the tools instead of sharing a
store": yes in principle, since Guix is deterministic and a node
building the same derivations would materialise identical store paths,
but ravanan submits a store path and Slurm does not substitute
automatically -- so it needs a realise-then-run wrapper (ravanan's
slurm backend already holds the script's derivation), a per-workflow
realise job, or guix publish plus a node-side daemon, with the costs
and channel-pinning caveats listed.  The timing table from the test
cluster (cached: identical; fresh: waves vs synchronous steps) is
included so expectations are explicit.

docs/ravanan-slurm.md and README.md link to it.
Diffstat (limited to 'test/python/server_test_case.py')
0 files changed, 0 insertions, 0 deletions