Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] What classad attributes are availble when writingthe PREEMPTION_REQUIREMENTS setting?
- Date: Thu, 6 Jan 2005 14:45:32 -0600
- From: Erik Paulson <epaulson@xxxxxxxxxxx>
- Subject: Re: [Condor-users] What classad attributes are availble when writingthe PREEMPTION_REQUIREMENTS setting?
On Thu, Jan 06, 2005 at 03:30:15PM -0500, Ian Chesal wrote:
> I'm not certain what ClassAd attributes I can reference when I'm writing
> my PREEMPTION_REQUIREMENTS setting for my cluster. I know MY lets me
> reference the currently running job
No, it's not the currently running job - it's the machine that the
negotiator is considering for preemption. And remember,
PREEMPTION_REQUIREMENTS must become TRUE for the new job to claim
the machine (it's sometimes hard for me to keep it straight)
> and TARGET is the job vying for the
> resource. But within the MY namespace what attributes are available? All
> the attributes in the MY job's ClassAd I see with condor_q -long or all
> the attributes available for the vm running the when I do condor_status
> -direct -long? Or both? Or a completely different set of attributes?
>
It is everything available in the VM ClassAd. If you want something from
the job ad, you have to export it into the machine ClassAd using
STARTD_JOB_EXPRS.
One caveat - STARTD_JOB_EXPRS is not really VM-aware - so if you export
it from one VM it winds up in the ad of every VM on that machine.
-Erik