Beruflich Dokumente
Kultur Dokumente
1
Globus Toolkit Auto Installation
Latest version of 1.0.1 published on February 2009
This utility has been developed by the Research team headed by
Prof. S.Thamarai Selvi (stselvi@annauniv.edu) at
Centre for Advanced Computing Research and Education,
Department of Information & Technology, Madras Institute of Technology,
Anna University,
Tamil Nadu,
INDIA.
Introduction
The Development of Globus Toolkit Auto Installation aims at the
creation of Grid Environment setup with ease and comfort which performs
the automation of various versions of globus toolkit installation and
configuration. This version support the installation and configuration of
lrms of type PBS and SGE .
Acknowledgement
The Globus Toolkit Auto Installation Utility is a part of the research
activities of Centre for Advanced Computing Research and Education
(CARE) which is funded by Ministry of Communication and Information
Technology, Department of Information Technology, New Delhi, INDIA.
Copyrights reserved CARE@MIT
Table of Contents
Page No
(i) User’s Guide ..……………… 3
(ii) Verification of Globus Toolkit .……………… 7
Copyrights reserved CARE@MIT 2
GTAI 1.0.1
Globus Toolkit Auto Installation – User Guide
Tested Platform
(a) Fedora Core (FC3, FC4, FC6, FC8, FC9)
(b) CentOS (Version 5)
(c) Scientific Linux (SL4, SL5)
(d) RHEL (4,5)
GTAI1.0.1 – Installation steps
(i) Download the software bundle GTAI1.0.1.tar.gz and copy the bundle to the
location /usr/local
(ii) Untar the bundle using the following steps
(a) As 'root' user, change to the directory /usr/local
cd /usr/local
(b) Untar the GTAI1.0.1.tar.gz
tar zxvf GTAI1.0.1.tar.gz
(iii) Make sure that the following files are present in the directory /usr/local
(a) README
(b) auto.cfg
(c) GTAI_install.sh
(d) GridSoftware.tar.gz
(iv) GTAI uses the configuration file (auto.cfg) for the automatic installation of
Globus toolkit. The configuration file should be suitably modified for the globus
installation. Here is the sample of GTAI configuration file with comments
Copyrights reserved CARE@MIT 3
Sample “auto.cfg” file
#IP_ADDRESS: Ip Address of your host machine & should not be empty
#Make sure that the same IP address has been present in /etc/hosts file
#e.g IP_ADDRESS: 10.2.0.1
IP_ADDRESS:172.16.10.51
#USERNAME: Name of the third party user for getting user certificate
#e.g USERNAME:guser01
USERNAME:guser01
#LRMS: Name of the Local Resource Management System. (PBS or SGE )
#e.g LRMS:SGE
LRMS:PBS
#GLOBUS_VERSION: Version of Globus Tool Kit
#e.g GLOBUS_VERSION:globus4.0.3
GLOBUS_VERSION:globus4.0.7
#GLOBUS_CONFIG_OPTION: Globus Tool Kit Configuration Options
#e.g GLOBUS_CONFIG_OPTION:enableprewsmds enablewsgram
pbs enablei18n enabledrs enablegridway with
gridwayargs="withdb=no"
#Default Config will be enabled if not set
GLOBUS_CONFIG_OPTION:
(a) Replace the value “172.16.10.51” with your IP address in the line “IP_ADDRESS:”
(b) Specify the third party user name “guser01” (OPTIONAL)
(c ) Specify the LRMS name “PBS” or “SGE”
(d) Specify the globus version needed for the installation “globus4.2.0” or “globus
4.2.1” or “globus4.0.8” or “globus4.0.7” or “globus4.0.3” in the line
“GLOBUS_VERSION:”
(e) Globus configuration option can be of customized one by specifying the variable “
GLOBUS_CONFIG_OPTION:” or it can be left blank for the default configuration to take
place.
Copyrights reserved CARE@MIT 4
(vi) Globus installation requires the setting of Environment variables . The setting of variables
can be made using the following steps
(a) Add the following environment variables in the file named “/etc/profile” before the line
“export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC” .
JAVA_HOME=/usr/java/jdk1.5.0
ANT_HOME=/usr/local/ant1.6.4
CATALINA_HOME=/usr/local/tomcat5.0.27
JUNIT_HOME=/usr/local/junit3.8.1
PBS_HOME=/var/spool/PBS
GLOBUS_LOCATION=/usr/local/globus4.0.7
GRID_SECURITY_DIR=/etc/gridsecurity
GRIDMAP=/etc/gridsecurity/gridmapfile
GLOBUS_HOSTNAME=`/bin/hostname`
SGE_ROOT=/usr/local/sge
PATH=$JAVA_HOME/bin:/bin/tar:$ANT_HOME/bin:$PATH:$CATALINA_HOME/bin:
$GLOBUS_LOCATION/bin:$GLOBUS_LOCATION/sbin:/usr/local/bin
CLASSPATH=$JAVA_HOME/lib/tools.jar:$CLASSPATH:$JUNIT_HOME/junit.jar
LD_LIBRARY_PATH=$GLOBUS_LOCATION/lib:$LD_LIBRARY_PATH
export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC
JAVA_HOME CLASSPATH ODBCINI CATALINA_HOME JUNIT_HOME PBS_HOME
GLOBUS_LOCATION GRID_SECURITY_DIR GRIDMAP GLOBUS_HOSTNAME
ANT_HOME LD_LIBRARY_PATH SGE_ROOT
(b) Comment the line “export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE
INPUTRC” as shown below
“#export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC”
(c ) Verify the environment variable by using the following commands
source /etc/profile
echo $JAVA_HOME
echo $ANT_HOME
echo $CATALINA_HOME
echo $JUNIT_HOME
echo $PBS_HOME
echo $GLOBUS_LOCATION
echo $GLOBUS_HOSTNAME
if any variable have not set, repeat the previous step ( (vi) (a)) and modify accordingly.
Copyrights reserved CARE@MIT 5
(vii ) Go to the location /usr/local (cd /usr/local). Ensure the following files are present
in this location. This can be done using the command "ls" in the location /usr/local.
(1) auto.cfg
(2) GTAI_install.sh
(3) GridSoftware.tar.gz
(4) README
(viii) Run the script GTAI_install.sh as shown below
/bin/sh GTAI_install.sh
( Make sure that you are in the location /usr/local)
This script automatically sets up the globus environment and the installation may run for
one hour and forty five minutes depending on the system.
Note : Any error which occurs during this running of script may stop the installation process
and the reason for the failure of the GT installation can be obtained from the file
“/tmp/log.txt”
(ix) After the installation complete, a message is displayed about the status of the installation. A
complete log information of the Globus installation can be obtained from file “/tmp/log.txt”.
Trouble shooting :
Copyrights reserved CARE@MIT 6
Verification of Globus Toolkit
Verification of Globus toolkit requires the following steps
(i) Testing of Globus container
(a) As root user, start the postgres database as follows
service postgresql start
(b) Login as globus user as follows
su globus
(c ) Start the globus container using the following command
globusstartcontainer
(d) You may find a set of services running as follows
Sample Output
[1]: https://172.16.10.52:8443/wsrf/services/AdminService
[2]: https://172.16.10.52:8443/wsrf/services/AttachmentTestService
[3]: https://172.16.10.52:8443/wsrf/services/AuthzCalloutTestService
[4]: https://172.16.10.52:8443/wsrf/services/CASService
[5]: https://172.16.10.52:8443/wsrf/services/ContainerRegistryEntryService
[6]: https://172.16.10.52:8443/wsrf/services/ContainerRegistryService
[7]: https://172.16.10.52:8443/wsrf/services/CounterService
*
*
*
*
[63]: https://172.16.10.52:8443/wsrf/services/mds/test/httpsource/IndexService
[64]: https://172.16.10.52:8443/wsrf/services/mds/test/httpsource/IndexServiceEntry
[65]: https://172.16.10.52:8443/wsrf/services/mds/test/subsource/IndexService
[66]: https://172.16.10.52:8443/wsrf/services/mds/test/subsource/IndexServiceEntry
[67]: https://172.16.10.52:8443/wsrf/services/mds/test/usefulrp/IndexService
[68]: https://172.16.10.52:8443/wsrf/services/mds/test/usefulrp/IndexServiceEntry
Note :
Globus services may vary depending upon the versions.
Copyrights reserved CARE@MIT 7
(ii)Testing of Globus component MDS4
(a) Login as third party user using the following command
su guser01
(b) Make sure that this third party user has a valid credential.
gridproxyinfo > for verification of valid proxy certificate
gridproxyinit > for generating proxy credential
(c ) Query the resource information using the following command
wsrfquery s https://YourIP:8443/wsrf/services/DefaultIndexService
Note :
“YourIP” represents the IP address of your machine.
Sample output
<ns0:IndexRP xmlns:glue="http://mds.globus.org/glue/ce/1.1"
xmlns:metric="http://mds.globus.org/metadata/2005/02"
.
.
.
.
<ns9:AggregatorData>
<ns1:GLUECE xmlns:ns1="http://mds.globus.org/glue/ce/1.1">
<ns1:ComputingElement ns1:Name="default" ns1:UniqueID="default">
<ns1:Info ns1:GRAMVersion="4.2.1" ns1:HostName="autoinstall2.grid"
ns1:LRMSType="Fork" ns1:LRMSVersion="1.0" ns1:TotalCPUs="2"/>
<ns1:State ns1:EstimatedResponseTime="0" ns1:FreeCPUs="0"
ns1:RunningJobs="0" ns1:Status="enabled" ns1:TotalJobs="0"
ns1:WaitingJobs="0" ns1:WorstResponseTime="0"/>
<ns1:Policy ns1:MaxCPUTime="1" ns1:MaxRunningJobs="1"
ns1:MaxTotalJobs="1" ns1:MaxWallClockTime="1" ns1:Priority="0"/>
</ns1:ComputingElement>
</ns1:GLUECE>
Copyrights reserved CARE@MIT 8
(iii)Verification of globus component RFT
(a) Login as third party user using the following command
su guser01
(b) Check whether the Grid FTP server is running which can be done using the
following command
netstat an | grep 2811
You should get the output similar to the following line
tcp 0 0 :::2811 :::* LISTEN
(c ) create a file named /tmp/rft.xfr with the following contents
true
16000
16000
false
1
true
1
null
null
false
10
gsiftp://autoinstall2.grid:2811/etc/group
gsiftp://autoinstall2.grid:2811/tmp/rftTest.txt
Note: Replace the content “autoinstall2.grid” with your hostname.
(d)Run the command rft h autoinstall2.grid f /tmp/rft.xfr
Note: Replace the content “autoinstall2.grid” with your hostname.
(e) Verify the contents of the destination file “rftTest.txt” is similar to that of the
one “/etc/group”
Copyrights reserved CARE@MIT 9
(iv)Verification of globus component GRAM.
(a) Login as third party user and run the following command to submit job to
GRAM component
su guser01
globusrunws submit s c /bin/hostname
Sample output:
Delegating user credentials...Done.
Submitting job...Done.
Job ID: uuid:35489900e85811dd9fab001e908e0d8b
Termination time: 01/22/3009 07:42 GMT
Current job state: Active
Current job state: CleanUpHold
autoinstall2.grid
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
Cleaning up any delegated credentials...Done.
Note :
(i) Make sure that globus container is running.
(ii)Your should obtain the hostname of your machine as of the output
“autoinstall2.grid”
Copyrights reserved CARE@MIT 10