Re: [HTCondor-users] JOB_TRANSFORM and JOB_ROUTER

["Beyer, Christoph" <christoph.beyer@xxxxxxx>]

Hi Malathi,

for transforms, see an example in the manual at

4.7.2 condor_schedd Policy Configuration

It is difficult to explain these more complex methods without knowing what kind of initial problem you are trying to solve ...

Best

christoph

--
Christoph Beyer
DESY Hamburg
IT-Department

Notkestr. 85
Building 02b, Room 009
22607 Hamburg

phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx

---

Von: "Malathi via HTCondor-users" <htcondor-users@xxxxxxxxxxx>
An: "John M Knoeller" <johnkn@xxxxxxxxxxx>
CC: "Malathi" <malathi@xxxxxxxx>, "htcondor-users" <htcondor-users@xxxxxxxxxxx>, "htcondor-admin" <htcondor-admin@xxxxxxxxxxx>
Gesendet: Freitag, 15. Dezember 2023 06:46:03
Betreff: [HTCondor-users] JOB_TRANSFORM and JOB_ROUTER

Hi,

Thanks for your clarifications and another  few questiones arrived in mind is that 

1.JOB_TRANSFROM will run in single schedd which means local/single pool only and JOB_ROUTER will work in different pool . Is this correct?

2. which version is more comfortable to use these feature 10.X series or 23.X ?

3. can you let me know how to configure JOB_TRANSFORM and JOB_ROUTER with example in config file and submit file to call those function

4. How do I make sure that my jobs are getting transformed within a single pool or different pool? (some specific commands to check)

Please reply these questions also, so that it will be helpful for me to implement in our cluster.

Please do the needful.

Regards,

Malathi

---

From: "John M Knoeller" <johnkn@xxxxxxxxxxx>
To: "htcondor-users" <htcondor-users@xxxxxxxxxxx>
Cc: "Malathi Deenadayalan" <malathi@xxxxxxxx>, "htcondor-admin" <htcondor-admin@xxxxxxxxxxx>
Sent: Thursday, December 14, 2023 9:34:47 PM
Subject: Re: JOB_TRANSFORM and JOB_ROUTER

The JOB_TRANSFORM_* configuration in the AP/Schedd allows the administrator to change jobs as they are submitted.    This provides a way for the admin to enforce policy and provide default behavior.  the untransformed job is lost and only the transformed job ends up in the schedd.

The JOB_ROUTER is a daemon that copies jobs from one schedd and submits transformed copies of those jobs back into the same schedd or to another schedd.   The original job is not lost, instead it is marked as "managed".  As the transformed/routed job runs, state changes to the transformed copy are reflected back to the original job.  when the transformed copy completes, the original job is marked as completed. 

These two mechanisms use the same transform syntax, but they solve different problems.  

Hope this helps.

-tj

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Malathi via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Sent: Thursday, December 14, 2023 12:35 AM
To: htcondor-users <htcondor-users@xxxxxxxxxxx>
Cc: Malathi <malathi@xxxxxxxx>; htcondor-admin <htcondor-admin@xxxxxxxxxxx>
Subject: [HTCondor-users] JOB_TRANSFORM and JOB_ROUTER

 

Hi,

I have great confusion about JOB_TRANSFORM and JOB_ROUTER in HTCondor.
I want to know at when and what purpose JOB_TRANSFORM should be used in HTCondor and what is the role of JOB_ROUTER. Both are doing the same work or different.
How to  configure JOB_TRANSFORM and JOB_ROUTER for my local pool.

Please help me in this regards, I referred all the documents but could not get clear clarification.

I request you to please respond to this mail and clear my clarification.
Anticipating your reply asap......

Regards,
Malathi
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/