Re: [HTCondor-users] Issues moving to new job route syntax

[Alessandro Pascolini <alessandro.pascolini@xxxxxxxxxxxx>]

Hi Cole,

indeed I tired the condor_transform_ads as well, I forgot to write it in the previous mail (ops..).

I don't get any output when running the comand:

# cat old-syntax-file

JOB_TRANSFORM_AddHS06 = [

eval_set_HostFactor = "$$(t1_wn_hs06:0)";

eval_set_numcpus = "$$(TotalCpus:16)";

eval_set_HepScore = "$$(t1_wn_hepscore:0)";

]

# condor_transform_ads -convert:file old-syntax-file

From what I read on the documentation it should print the new syntax on stdout, am I wrong?

Thanks,

Alessandro 

On 2 Oct 2024, at 16:04, Cole Bollig via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:

Hi Alessandro,

Condor_upgrade_check only checks for use of the old job router syntax in the configuration. If the old syntax was already removed, then the tool will say everything is successful. To help assist with the transition we updated condor_transform_ads to convert old job router syntax to new job router syntax. You can write the old syntax to a file `foo` and then run the following to see the new syntax:

condor_transform_ads -convert:file foo

The HTCondor-CE documentation has a whole section dedicated to converting syntaxes (https://htcondor.com/htcondor-ce/v23/configuration/job-router-overview/#converting-to-classad-transforms).

If this doesn't work let us know,

Cole Bollig

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Alessandro Pascolini <alessandro.pascolini@xxxxxxxxxxxx>
Sent: Wednesday, October 2, 2024 3:22 AM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Issues moving to new job route syntax

 

Hi everyone,

since HTCondor24 is dropping support to the old job routing syntax I've been working on updating our job_routers/transforms.

I faced an issue since I couldn't find a replacement for this transform:

JOB_TRANSFORM_AddHS06 = [ 

eval_set_HostFactor = "$$(t1_wn_hs06:0)"; 

eval_set_numcpus = "$$(TotalCpus:16)"; 

eval_set_HepScore = "$$(t1_wn_hepscore:0)";

]

It basically allowed us to copy these custom machine attributes as job attributes. 

From what I read on the documentation the eval_set_* macro will no longer be available so I am looking for an equivalent macro in the new syntax.

I have already tried with the EVALSET macro but with no luck, maybe I am doing it wrong. 

Here is my attempt:

JOB_TRANSFORM_HEPScore @=end

  EVALSET t1_HEPSCORE $(t1_wn_hepscore)

@end

Speaking with Todd during the HTC Wokrshop he suggested to use the tool provided in new HTCondor versions.

I used the condor_upgrade_check tool but it told me: 

"No issues found with installed HTCondor for known incompatibilities."

Do you have any suggestion on how to implement this in the new syntax?

Cheers,

Alessandro

_______________________________________________
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/

Attachment: smime.p7s
Description: S/MIME cryptographic signature