Overview
grid.ramscommunity.org is currently a Condor Execute node. Since it is on a busy titan.melcoe.mq.edu.au, it is not suitable to be an Execute note.
On the other hand, the current Submit node, grid2.ramscommunity.org, is better left alone as a manager machine to avoid adding additional users or other grid executables.
For this reason, grid1 will be made a Submit node and grid4 will be made an Execute node.
Also, the Submit node requires certain Globus binaries, e.g. MyProxy and GridFTP (client*). These are installed on this node already, so this is convenient.
* GridFTP server is required if the data needs to be transferred back.
Kerberos client
Kerberos client package is installed on the client host as system default, but it has to be configured as detailed as Kerberos client earlier.
Before NFS and LDAP can be used, host key and NFS servic key must be created on KDC (or via Kerberos clinet kadmin on the client) and installed on the client host.
LDAP client
LDAP client package is installed on the client host as system default, but it has to be configured as detailed as LDAP client earlier.
It has to be prepared before networks shared accounts and PAM can be used.
Network shared accounts
This has been detailed in LDAP Client section earlier.
Remove local accounts and home directories for those who are going to use network accounts and home directories.
Before mounting /home via NFS, the system must be configured to use network accounts and passwords.
NFS
This also has been detailed in the LDAP Client section earlier.
Mount /nfs and /home.
Test.
Condor
Condor binaries are on /nfs/software/condor/7.0.1/. Mount the /nfs first.
This node probably only requires Condor-G (GRAM2 client).
Refer to details on "Condor - 2nd node" earlier.
Briefly:
Copy the /etc/init.d/condor script (which points to /nfs/software/condor/7.0.1/etc/condor_config).
Copy also the /scratch/condor/condor_config.local from the first Condor node to local /scratch/condor/.
# mkdir 1777 /scratch/condor # mkdir 1777 /scarrtch/condor/log # mkdir 1777 /scarrtch/condor/exec # mkdir 1777 /scarrtch/condor/spool # scp root@grid2.ramscommunity:/scratch/condor/codor_config.local /scratch/condor/ # vi /scratch/condor/condor_config.local -- modify -- DAEMON_LIST = MASTER, SCHEDD
# service condor stop # rm /scratch/condor/log/* # service condor start
Globus
This has been already installed. Refer to install 2nd Globus earlier.
This node requires MyProxy, GridFTP, /etc/grid-security.
Installing Pegasus Mapper
Pegasus Mapper is installed from nightly build, since the one used before (VDT bundle) apparently had some bug. Downloaded a nightly build from http://pegasus.isi.edu/mapper/nightly.php. A CentOS 4.2 package was chosen because it is supposed to be compatible with CentOS 5.2 we are using. CentOS 5.2 was chosen for VDT initially, although we no longer use it.
# wget http://pegasus.isi.edu/mapper/download/nightly/pegasus-binary-2.2.0cvs-x86_cent_4.2.tar.gz
# tar -xzvf pegasus-binary-2.2.0cvs-x86_cent_4.2.tar.gz
# chown globus:globus pegasus-2.2.0cvs
# mkdir /usr/local/pegasus
# mv pegasus-2.2.0cvs /usr/local/pegasus/2.2.0
Add env to user, e.g. /etc/profile on this machine, but not ~yoichi/.bash_profile (since it is shared with other hosts which may not have installed Pegasus Mapper):
export PEGASUS_HOME=/usr/local/pegasus/2.2.0 unset CLASSPATH source $PEGASUS_HOME/setup.sh
# su - yoichi $ pegasus-version -f 2.2.0cvs-x86_cent_4.2-20081002052524Z
Add Comment