# ravanan + Guix + Slurm: how a request travels What is in this directory, how `POST /compute/gemma/ravanan` gets from an HTTP request to jobs running on cluster nodes, and which part of the stack has to exist where. Configuration keys are in [../docs/ravanan-slurm.md](../docs/ravanan-slurm.md); the Slurm-side authentication wiring is in `gn-machines/slurm-session.md`. ``` cwl/ gemma/gemma-loco.scm the workflow, in ccwl (not raw CWL) gemma/manifest.scm the Guix manifest ravanan resolves job commands against ``` Both files are *sources*: `compute_ravanan` compiles the ccwl to a throwaway `.cwl` under `ravanan_cache_dir` on every call (`ccwl compile`, pure macro expansion, no Guix build), so no CWL is ever checked in. To inspect it by hand: ```sh ccwl compile --output=gemma-loco.cwl gemma/gemma-loco.scm ``` ## The sequence ``` POST /compute/gemma/ravanan │ ├─ compute_ravanan (Rust, API host) │ writes /--pheno.txt and -ravanan-inputs.yaml │ ccwl compile gemma-loco.scm -> /--gemma-loco.cwl │ creates /ravanan-store/{files,logs,data} │ invokes: ravanan --store=/ravanan-store │ --guix-manifest=gemma/manifest.scm │ [--batch-system=slurm-api --slurm-api-endpoint=… │ --slurm-jwt= [--slurm-partition=…] [--scratch=…]] │ gemma-loco.cwl inputs.yaml │ ├─ ravanan (front end / API host; never on a node) │ builds a Guix profile from the manifest (gemma) │ per CWL step: gexp->script -> a script in /gnu/store that embeds │ the profile's PATH, ravanan's own work library, and the command │ slurm-api: POST /slurm/v0.0.41/job/submit with │ script = "#!/bin/bash\n