[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Fresh install from a newbie
- Date: Wed, 18 May 2005 09:00:29 -0400 (EDT)
- From: Leslie Groer <groer@xxxxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Fresh install from a newbie
As a recent newbie and having gone through some of the same steps you are
going through I can let you know what I did for some of the parameters.
Don't consider these definitive answers though as I may have got some of
On Wed, 18 May 2005, Nicolas GUIOT wrote:
> OK, now everything seems fine : I tried some settings with the global
> config file, then tried to install an execute machine, but had
> especially problems with directories used (like RELEASE_DIR, LOCAL_DIR,
> etc...), that's why I'm now asking to those of you who understand my
> Here are the questions :
> In the Global config file :
> - RELEASE_DIR : is by default set to /usr/local/condor : should I set it to the /home/condor (location of condor user's home) or /nfs/condor (the same, but accessible through NFS), or something else ?
I have this common to all nodes in our cluster installed under
/home/condor/dist. This means I don't need a separate installation on
> - LOCAL_DIR : as is it linked to RELEASE_DIR, if it's on the NFS, that means I need a huge place (to store spool ??), right ?
This is one place the Condor manual is not explicit enough in my opinion.
This directory really should be *LOCAL* i.e. not an NFS mounted disk. It
also should be separate for each node. I have ours set to /condor/ but
will probably move it to /scr/condor soon as we have a local scratch area
on each worker node.
> - LOCAL_CONFG_FILE : seems to be automatically set during install...
> must it be accessible through NFS ? (in this case I have to change
Again, all the software is linked to the /home/condor/dist area so config
files are in /home/condor/dist/etc (which means the cluster NFS server has
to be up, but nothing else will work anyway if this is down!).
> - USE_NFS : IMHO, should be True...
> - LOCK : as my LOCAL_DIR (might) is on the NFS, I should set it as
> something like /tmp/condor, right ? or any better idea ?
Again should not be on NFS but really is local. We have /var/lock.
> - DEFAULT_DOMMAIN_NAME : should I set it to mylab.myfirm.com, or myfirm.com, or let it by default ?
Really is just a string but ensures conscistency across the nodes.
> Now, what about the local config file :
> - RELEASE_DIR : does this have to refer to /nfs/condor (the home of the condor user on the manager), or must it be a local file, or anything else ?
> - LOCAL_DIR : same question
The head nodes (CM and schedulers) use the same config files as the local
for our cluster.
> - CONDOR_ADMIN : this was automatically set to
> root@xxxxxxxxxxxxxxxxxxxxxxxx, but it doesn't exist !! (or never
> checked...) : should I change it with the email address of condor (my
> email) ?
Set this to whatever e-mail you want to receive mail at. Check that the
CM can actually send you mail there!
> The final question is, when I setup other machines than the manager : do
> I have to create each time a /home/condor directory, and setup the
> condor client there ? do I have to configure also each time the Global
> Config file AND the Local Config file again ? Will some settings be
> automatically set by the installer ?
This is where the beauty of a single install area comes in if you have a
shared file system. There is almost zero setup to add a node. Just make
sure it has the /etc/condor_config set up and start up the daemons in
init.d or whatever and the machines automatically are part of your pool.
/ | ' \ groer@xxxxxxxxxxxxxxxxxxx Department of Physics
( ) 0 Tel: +1-416-978-2959 University of Toronto
\_/-, ,----' Fax: +1-416-978-8221 60 St. George Street
==== // Toronto, ON M5S 1A7
/ \-'~; /~~~(O) Canada
/ __/~| / | Office: McLennan Physics Lab Room 911
=( _____| (_________| http://home.fnal.gov/~groer
Leslie S. Groer