User Story
As a contributor for the Slurm scheduler + SSH/Local transports,
I want a containerised single-node Slurm cluster reachable both over SSH and by local exec, in CI,
So that the SSHTransport × Slurm and LocalTransport × Slurm combinations are validated end-to-end.
Feature Description
Stand up the ssh-slurm and local-slurm stacks (IC-ADR-002) — they share one image and
differ only in how the tests reach the batch node:
ssh-slurm: connect over port 22 (exec_in_container: false);
local-slurm: docker compose exec pytest inside the container (exec_in_container: true,
manifest stack: ssh-slurm).
Harmonize onto the scaffold from # per the checklist.
Definition of Done
Alternatives Considered
Related Issues
Additional Context
User Story
As a contributor for the Slurm scheduler + SSH/Local transports,
I want a containerised single-node Slurm cluster reachable both over SSH and by local exec, in CI,
So that the
SSHTransport × SlurmandLocalTransport × Slurmcombinations are validated end-to-end.Feature Description
Stand up the
ssh-slurmandlocal-slurmstacks (IC-ADR-002) — they share one image anddiffer only in how the tests reach the batch node:
ssh-slurm: connect over port 22 (exec_in_container: false);local-slurm:docker compose execpytest inside the container (exec_in_container: true,manifest
stack: ssh-slurm).Harmonize onto the scaffold from # per the checklist.
Definition of Done
sinfoshows the compute nodeidle; healthcheck passesssh-slurmreachable over port 22docker compose, EL9 + pinned Slurm RPM under_images/slurm/,stacks/ssh-slurm/layout,ssh-slurm+local-slurmstacks.ymlentries, bespokeworkflow removed
ssh-keygenin a CI step →authorized_keys, known-hosts viassh-keyscanAlternatives Considered
Related Issues
Additional Context