Re: [Condor-users] Copying job attrs into slot attrs

[William Henry <whenry@xxxxxxxxxx>]

Thanks I'll look at that and see what I can do with it. I'll let you know.

What I'm looking at is this:

If I have a machine with four slots but it has only two local resources (e.g. two graphics cards) I want to make sure that only two jobs requiring the graphics cards will run but that the other slots are free for other work.  

I'll try tinkering with the STARTD_JOB_EXPRS. Thanks!

William

----- "Dan Bradley" <dan@xxxxxxxxxxxx> wrote:

> I think Ian meant to write STARTD_JOB_EXPRS rather than STARTD_EXPRS.
> 
> --Dan
> 
> Ian Chesal wrote:
> >> Is there a way for copying a Job attribute over to the slot
> >> that it is running?
> >>     
> >
> > You bet. STARTD_EXPRS is what you want. See:
> >
> >
> http://www.cs.wisc.edu/condor/manual/v7.2/3_3Configuration.html#16323
> >
> >   
> >> I'm trying to configure a job policy that depends on how many
> >> slots are using a local resource.
> >>
> >> I've looked at STARTD_SLOT_ATTRS but I can't see a way of
> >> updating a slot attribute without using START_CRON_ etc.
> >> dynamic updates. The problem here is that I then depend on
> >> update intervals I might miss an update.
> >>
> >> By copying a job attribute over the policy can then simply
> >> count how many jobs on that machine are using a resource.
> >> Any thoughts?
> >>     
> >
> > You'll have to look at the value of this attribute for each slot.
> Each slot will get a unique instance of this attribute. You can
> cross-advertise these values in each slot using STARTD_SLOT_EXPRS.
> This makes a value that's slot specific appear in every other slot,
> prefixed with the string "slot#_".
> >
> > So if you had:
> >
> > STARTD_EXPRS = ClusterID
> > STARTD_SLOT_EXPRS = ClusterID
> >
> > Then on a 2 slot machine, Slot 1 would have:
> >
> >         ClusterID = 8908
> >         slot2_ClusterID = 123
> >
> > And Slot 2 would have:
> >
> >         ClusterID = 123
> >         slot1_ClusterID = 8908
> >
> > - Ian
> >
> > Confidentiality Notice.
> > This message may contain information that is confidential or
> otherwise protected from disclosure. If you are not the intended
> recipient, you are hereby notified that any use, disclosure,
> dissemination, distribution,  or copying  of this message, or any
> attachments, is strictly prohibited.  If you have received this
> message in error, please advise the sender by reply e-mail, and delete
> the message and any attachments.  Thank you.
> >
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
> with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> > The archives can be found at: 
> > https://lists.cs.wisc.edu/archive/condor-users/
> >   
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/