[Feature]: Implement an ARC 7 CE - Slurm integration test in a CI workflow
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the arc-slurm integration-test stack and the CI workflow described in the issue, then inspect the scaffold referenced by # and IC-ADR-002. Verify the image healthcheck, run the real arcsub → arcstat → arcget flow, assert the retrieved output, and confirm ARC/Slurm logs are uploaded on every run.
Written by the indexing model from the issue text.
Description
User Story
As a contributor for the ARC module,
I want an ARC 7 CE wired to Slurm running in CI with a real submit → monitor → retrieve test,
So that changes to the ARC path are validated end-to-end against a real LRMS and no regressions slip in.
Feature Description
Stand up the arc-slurm integration-test stack (IC-ADR-002): an ARC 7 Compute Element
(REST/AREX) wired to a single-node Slurm LRMS, plus CI that builds the image, boots it, and runs a
full submit → monitor → retrieve test with the real ARC client tools
(arcsub/arcstat/arcget). ARC's arcctl test-ca mints CA + host cert at install → no grid-PKI
in CI; the client credential is written to the shared credentials/ volume.
Harmonize onto the scaffold from # per the checklist.
Definition of Done
- Image builds & boots in CI; healthcheck (
curl -kthe REST info URL) passes -
arcsubsubmits,arcstatreachesFinished,arcgetretrieves, output asserted - ARC/Slurm logs uploaded as artifacts on every run
- Harmonized onto the scaffold
Alternatives Considered
- Official ARC image — none is maintained; pinned RPMs on EL9 is the supported path (ADR §Facts).
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
-
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
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100