Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[HTCondor-users] Open OnDemand HTCondor Adapter
- Date: Mon, 7 Jul 2025 10:19:51 +0200 (GMT+02:00)
- From: Joachim Meyer <jmeyer@xxxxxxxxxxxxxxxxxx>
- Subject: [HTCondor-users] Open OnDemand HTCondor Adapter
Hi everyone!
I've been playing around with creating an Open OnDemand (OOD) Adapter for HTCondor: https://github.com/OSC/ood_core/pull/885
That should allow getting e.g. Code Server running inside HTCondor Jobs quite easily.
As I'm not the most familiar with all of HTCondor's submission tricks, I would appreciate if anyone could give their two cents w.r.t how I'm submitting jobs in there.
Open OnDemand often runs on a non-submit machine and ssh's to a submission machine to execute, in our case, condor_submit.
OOD provides a script (think run.sh) that should be submitted as executable - Slurm and friends take this as STDIN, which can be done quite nicely via ssh.
With HTCondor, as far as I know, the executable always has to be a file on the submission node (or, shared fs or anything a transfer plugin supports ..) and only submit commands can be handed as stdin. Thus, my current approach is to write a temp file for run.sh on the submission node (ssh bash -c "cat >/tmp/tempname.sh").
Would you have any nicer suggestions that would require only limited changes to HTCondor configurations?
I've been considering using remote submission (calling condor_submit locally using -name to direct it to submission hosts), but I was uncertain if this is always available / might be a pain to set up?
If you have any other suggestions, let me know - also feel free to chip in on the GitHub PR!
Hope this might also be useful for anyone else :)
Best,
- Joachim Meyer