The following is an example installation for Condor 6.8.8. This is required to use the Condor and Condor-G portlets. Additional configuration is required to enable Birdbath and Condor-G, so see the portlet notes at www.collab-ogce.org.
Note also that this version of Condor will not work on newer RHEL and Fedora releases, so you will need to get the libstdc++.so.5 library. Do the following as root:
[shell> yum install libstdc++.so.5
Now do the following in the condor-6.8.8 release directory.
[shell> condor_install
Press enter to begin Condor installation
***************************************************************************
STEP 1: What type of Condor installation do you want?
***************************************************************************
Would you like to do a full installation of Condor? [yes]
Press enter to continue.
***************************************************************************
STEP 2: How many machines are you setting up for Condor?
***************************************************************************
Are you planning to setup Condor on multiple machines? [yes] no
Press enter to continue.
***************************************************************************
STEP 3: Install the Condor "release directory", which holds
various binaries, libraries, scripts and files used by Condor.
***************************************************************************
It looks like you've installed a Condor release directory in:
/usr/local/condor
Do you want to use this release directory? [yes] no
Have you installed a release directory already? [no] no
Where would you like to install the Condor release directory?
[/home/mpierce/condor]
That directory doesn't exist, should I create it now? [yes]
Installing a release directory into /home/mpierce/condor ...
[------------------------------Stuff deleted------------------------------]
done.
Using /home/mpierce/condor as the Condor release directory.
Press enter to continue.
***************************************************************************
STEP 4: How and where should Condor send email if things go wrong?
***************************************************************************
If something goes wrong with Condor, who should get email about it?
[mpierce@gw12.quarry.iu.teragrid.org]
What is the full path to a mail program that understands "-s" means
you want to specify a subject? [/bin/mail]
Using /bin/mail to send email to mpierce@gw12.quarry.iu.teragrid.org
Press enter to continue.
***************************************************************************
STEP 5: Filesystem and UID domains.
***************************************************************************
To correctly run all jobs in your pool, including ones that aren't relinked
for Condor, you must tell Condor if you have a shared filesystem, and if
so, what machines share it.
Please read the "Configuring Condor" section of the Administrator's manual
(in particular, the section "Shared Filesystem Config File Entries")
for a complete explaination of these (and other, related) settings.
Do all of the machines in your pool from your domain ("quarry.iu.teragrid.org")
share a common filesystem? [no]
Configuring each machine to be in its own filesystem domain.
Do all of the users across all the machines in your domain have a unique
UID (in other words, do they all share a common passwd file)? [no]
Configuring each machine to be in its own uid domain.
Press enter to continue.
***************************************************************************
STEP 6: Java Universe support in Condor.
***************************************************************************
Enable Java Universe support? [yes] no
OK, Java Universe will be left unconfigured.
Press enter to continue.
***************************************************************************
STEP 7: Where should public programs be installed?
***************************************************************************
The Condor binaries and scripts are already installed in:
/home/mpierce/condor/bin
If you want, I can create some soft links from a directory that is already
in the default PATH to point to these binaries, so that Condor users do not
have to change their PATH. Alternatively, I can leave them where they are
and Condor users will have to add /home/mpierce/condor/bin
to their PATH or explicitly use a full pathname to access the Condor tools.
Shall I create links in some other directory? [yes] no
Press enter to continue.
***************************************************************************
STEP 8: What machine will be your central manager?
***************************************************************************
What is the full hostname of the central manager?
[gw12.quarry.iu.teragrid.org]
Your central manager will be on the local machine.
Press enter to continue.
***************************************************************************
STEP 9: Where will the "local directory" go?
***************************************************************************
Condor will need to create a few directories for its own use
You have a "condor" user on this machine. Do you want to put all the
Condor directories in /home/condor? [yes] no
Do you want to put all the Condor directories in
/home/mpierce/condor/home? [yes]
Creating all necessary Condor directories ... done.
Press enter to continue.
***************************************************************************
STEP 10: Where will the local (machine-specific) config files go?
***************************************************************************
Condor allows you to have a machine-specific config file that overrides
settings in the global config file.
You must specify a machine-specific config file.
Should I put a "condor_config.local" file in /home/mpierce/condor/home?
[yes]
Creating config files in "/home/mpierce/condor/home" ... done.
Configuring global condor config file ... done.
Created /home/mpierce/condor/etc/condor_config.
Press enter to continue.
Setting up gw12.quarry.iu.teragrid.org as your central manager
What name would you like to use for this pool? This should be a
short description (20 characters or so) that describes your site.
For example, the name for the UW-Madison Computer Science Condor
Pool is: "UW-Madison CS". This value is stored in your central
manager's local config file as "COLLECTOR_NAME", if you decide to
change it later. (This shouldn't include any " marks).
gw12condorthing
Setting up central manager config file /home/mpierce/condor/home/condor_config.local ... done.
Press enter to continue.
***************************************************************************
STEP 11: How do you want Condor to find its config file?
***************************************************************************
Condor searches a few locations to find it main config file. The first place
is the envionment variable CONDOR_CONFIG. The second place it searches is
/etc/condor/condor_config, and the third place is ~condor/condor_config.
/home/condor/condor_config exists.
Renaming to: /home/condor/condor_config.old.
Should I put in a soft link from /home/condor/condor_config to
/home/mpierce/condor/etc/condor_config [yes]
Press enter to continue.
***************************************************************************
Condor has been fully installed on this machine.
***************************************************************************
/home/mpierce/condor/sbin contains various administrative tools.
If you are going to administer Condor, you should probably place that
directory in your PATH.
To start Condor on any machine, just execute:
/home/mpierce/condor/sbin/condor_master
Since this is your central manager, you should start Condor here first.
Press enter to continue.
You should probably setup your machines to start Condor automatically at
boot time. If your machine uses System-V style init scripts, look in
/home/mpierce/condor/etc/examples/condor.boot
for a script that you can use to start and stop Condor.
Please read the "Condor is installed... now what?" section of the INSTALL
file for things you should do before and after starting the Condor daemons.
In particular, you might want to set up host/ip access security. See the
Adminstrator's Manual for details.
Subscribe to:
Post Comments (Atom)
5 comments:
I wonder what do you do to allow for other users other than you to use/submit to this pool?
Do you run the daemon as root or as the condor user?
Also, the installation was it done as root or as condor?
Do everything as a non-root user--we recommend installing condor with the same account that runs the portal.
The portlet code just shows how to run self-contained jobs,so everything at the unix level is run by the "condor" user.
Hey, I am getting really confused. The condor manual recommend the installation to be as root and running the deamons as root also. The installation is planned to be used by a large group of people. We have one installation that is done with condor user and only this user can submit jobs. I attributed this to installation as non-root since it is hard to give permission on files properly this way, right?
Right--if you are using condor from the command line and want multiple people to have access to it with their regular accounts, you should run as root.
But you don't need to worry about file permissions if you are letting the portal submit jobs. You do need to worry about file permissions if condor needs to access a file or executable in the user's directory.
I think you should effectively ignore my comments. I didn't get to see your portal and I wasnot talking about your portal. I was only talking about condor only. Not your whole portal.
Post a Comment