Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[HTCondor-users] Condor-CE Configuration for SLURM Jobs with Singularity Containers
- Date: Wed, 10 Dec 2025 16:53:54 +0000
- From: Kamrul Shaker <Kamrul.Shaker@xxxxxxxxxxxx>
- Subject: [HTCondor-users] Condor-CE Configuration for SLURM Jobs with Singularity Containers
Hello HTCondor Community,
I'm setting up a workflow where I need to submit jobs from a Condor-CE client that will be routed to a SLURM
cluster, with jobs running inside Singularity containers on the SLURM worker nodes.
Current Setup:
-
HTCondor-CE configured with SLURM batch system integration
-
SLURM cluster with Singularity support on worker nodes
-
Basic job routing configured using JOB_ROUTER_ROUTE_Slurm_Cluster
What I Want to Achieve:
-
Submit jobs from a Condor-CE client
-
Jobs routed through Condor-CE to SLURM
-
Jobs execute within Singularity containers on SLURM worker nodes
-
Container image path specified in the submit file (e.g., from CVMFS)
My Questions:
-
Are there specific Condor-CE configuration parameters needed to pass Singularity container requirements through to SLURM?
-
Should the submit file use
universe = grid or universe = vanilla when submitting to the CE? -
How should I specify the Singularity image in the submit file so it's properly passed to SLURM? (I'm currently using
+SingularityImage) -
Do I need specific ClassAd attributes in the job router configuration to handle Singularity parameters?
-
Are there any SLURM-specific settings in the CE route configuration that need to be set for Singularity jobs?
Current Job Route Configuration:
JOB_ROUTER_ROUTE_Slurm_Cluster @=jrt
TargetUniverse = 9
GridResource = "batch slurm"
@jrt
JOB_ROUTER_ROUTE_NAMES = Slurm_Cluster
Any guidance on best practices for this workflow or pointers to relevant documentation would be greatly appreciated.
Best Regards,