[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] pseudo-dedicated machine

On Wed, 7 Jun 2006, Michael Thomas wrote:

I have a cluster of 50 nodes, 4 vms per node.  On all but one node I
have a certain directory mounted via read-only nfs.  On the remaining
node the directory is mounted read-write.

Every user coming into the system only needs read-only access to the
certain directory.  But one special user always needs read-write access.

How can I guarantee that this special user always gets sent to the one
node that has read-write access to this directory?  Note that I don't
mind if other users also get sent to this read-write node.

First, define the one node to have an extra attribute in its machine

[root@fnpcsrv1 root]# grep IO /opt/condor/local/condor_config.local
MachineClass = "IO"
Class = "IO"
START = JobClass =!= UNDEFINED && JobClass == "IO"

On a non-grid job, then the user should just add
+JobClass = "IO"
requirements = (MachineClass =!= UNDEFINED && MachineClass == "IO")

to his condor submit file.

You can force a inbound grid job for that user to do that
by hacking condor.pm to add these extra two lines to the
submit script file it writes.


I've heard that that this can be done by making changes to my globus job
manager file "condor.pm", but I haven't done much condor.pm hacking, so
I'm not sure what I can put in there to make this happen.


Steven C. Timm, Ph.D  (630) 840-8525  timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team