Re: [HTCondor-users] Open OnDemand HTCondor Adapter

[John M Knoeller <johnkn@xxxxxxxxxxx>]

Unfortunately no.  The email trigger cannot currently be configured, it will happen only on job error and termination. 

If you add "log=<file>" to your submit file,  then <file> will get an event for each job that starts.  it is fairly easy to have a python script follow that log and do whatever you want when the execution event is written.

have a look at the JobEventLog object,  particularly the events method in the python bindings.

-tj 

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Joachim Meyer <jmeyer@xxxxxxxxxxxxxxxxxx>
Sent: Thursday, July 10, 2025 4:21 AM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Open OnDemand HTCondor Adapter

Hi Greg,

thanks for your feedback!

Then I'll keep it as is for now.

One remaining question I have, is, whether there is any possible mapping for "email_on_started".

As far as I can tell, HTCondor's notify_user only notifies on errors/termination, not on scheduling.

Is there any option to make HTCondor also send out an E-Mail once the job is started?
This is useful in this context, for clusters with congested interactive slots, where one might send of a request for an interactive session early in the morning and then has to wait a while before getting the claim.

As you're going to read E-Mails in the meanwhile you might miss a good bit of your claim's time.

Thus a notification on start would be great.

Cheers,

- Joachim

Am Dienstag, 8. Juli 2025, 18:06:18 Mitteleuropäische Sommerzeit schrieb Greg Thain via HTCondor-users:

> On 7/7/25 03:19, Joachim Meyer wrote:

> > Hi everyone!

> > I've been playing around with creating an Open OnDemand (OOD) Adapter

> > for HTCondor: https://github.com/OSC/ood_core/pull/885

> > <https://urldefense.com/v3/__https://github.com/OSC/ood_core/pull/885__;!!Mak6IKo!IPmXh8MVW67VeUYxCE7YeaNnDxN52CAyCeo-M_yWNkzj4uEDcgGvturyOy1_BwP1KstGNWCZ6dqURERG4mfgfdd-$>

> >

> > That should allow getting e.g. Code Server running inside HTCondor

> > Jobs quite easily.

>

>

> Joachim:

>

> This is great work which will be of interest to many HTCondor users and

> administrators -- thank you for your efforts here!

>

> >

> > 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").

>

> I think this may be the best way for now.  If the script is small, it

> can be inlined into the submit file and job with with the "shell ="

> submit command, but I wouldn't recommend that for a general purpose

> tool, where you don't know what version of HTCondor you've got.

>

> > 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?

>

> My understanding of the Open On Demand approach is that it prefers to

> have as few batch system dependencies on the OOD machine -- that all it

> asks of the OOD machine is that it can ssh into the batch machine.

>

> -greg
--

Joachim Meyer

HPC-Koordination & Support

Universität des Saarlandes

FR Informatik | HPC

Postanschrift: Postfach 15 11 50 | 66041 Saarbrücken

Besucheranschrift: Campus E1 3 | Raum 4.03

66123 Saarbrücken

T: +49 681 302-57522

jmeyer@xxxxxxxxxxxxxxxxxx

www.uni-saarland.de