Re: [HTCondor-users] Requesting Software & Accessing ClassAds during Runtime

[Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>]

Hi Lukas,

Consider using an "ICCMajorVersion" attribute as a list type. The requirements line could then use the list membership ClassAd function to look for the right version. 

The job environment will have a $_CONDOR_JOB_AD environment variable, which can be parsed using condor_q -classads with -autoformat. 

   -Michael Pelletier. 

On Jun 27, 2017, at 5:24 AM, Koschmieder, Lukas <Lukas.Koschmieder@xxxxxxxxxxxxxxxxxxx> wrote:

Hi,

I would like to ask two questions.

Question 1

We're using a certain technique to handle software requirements in our Condor cluster. I would like to know if there is better way to do that.

This is how we do it:

• Our administrator defines a STARTD ClassAd HAS_ICC on each exec node that provides a software ICC.
• ICC users then attach REQUIREMENTS = HAS_ICC == TRUE to their job description files in order to make sure that their jobs are forwarded to ICC nodes.

This approach is easy and flexible. But if you have to provide multiple versions of a certain software, you end up with countless ClassAds such as HAS_ICC_VER_16, HAS_ICC_VER_17, etc. It feels that there should be a better way to do that.

Question 2

Is there an easy way for a job executable to access/read the "its own" ClassAds such as REQUIREMENT?

Regards,
Lukas

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