[Feature] Implement SSH-slurm / local-slurm integration-test in CI workflow
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, docker-compose, github-actions, python
- Domain
- ci-cd, devops, infrastructure
Research direction
Review the _images/slurm/, stacks/ssh-slurm/, stacks.yml, and CI workflow locations mentioned in the checklist, then compare them with the referenced foundation scaffold. Verify that both stack variants start a healthy single-node cluster, run the Slurm integration tests, and satisfy the SSH credential and GitHub Actions requirements.
Written by the indexing model from the issue text.
Description
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 execpytest inside the container (exec_in_container: true,
manifeststack: ssh-slurm).
Harmonize onto the scaffold from # per the checklist.
Definition of Done
- Cluster starts cleanly;
sinfoshows the compute nodeidle; healthcheck passes - Test jobs complete and produce output; CI workflow passes on GH Actions
- sshd variant: key-based access works;
ssh-slurmreachable over port 22 - Harmonized onto the scaffold:
docker compose, EL9 + pinned Slurm RPM under_images/slurm/,
stacks/ssh-slurm/layout,ssh-slurm+local-slurmstacks.ymlentries, bespoke
workflow removed - SSH creds ephemeral:
ssh-keygenin a CI step →authorized_keys, known-hosts via
ssh-keyscan
Alternatives Considered
Related Issues
Additional Context
- Dominant language
- Python
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DIRACGrid/intercede
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in DIRACGrid/intercede
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100