This action might not be possible to undo. Are you sure you want to continue?
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 (firstname.lastname@example.org) at
Centre for Advanced Computing Research and Education,
Department of Information & Technology, Madras Institute of Technology,
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 .
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 .……………… 7 Copyrights reserved CARE@MIT 2 ..……………… 3 (ii) Verification of Globus Toolkit .
0.gz tar zxvf GTAI1.1 – Installation steps (i) Download the software bundle GTAI1.5) GTAI1.0. FC8.tar.0.1.0.1.cfg (c) GTAI_install.tar. change to the directory /usr/local cd /usr/local (b) Untar the GTAI1. FC6.1 Globus Toolkit Auto Installation – User Guide Tested Platform (a) Fedora Core (FC3.1.gz (iv) GTAI uses the configuration file (auto.0.cfg) for the automatic installation of Globus toolkit. FC9) (b) CentOS (Version 5) (c) Scientific Linux (SL4.GTAI 1.tar. The configuration file should be suitably modified for the globus installation.gz (iii) Make sure that the following files are present in the directory /usr/local (a) README (b) auto.sh (d) GridSoftware.gz and copy the bundle to the location /usr/local (ii) Untar the bundle using the following steps (a) As 'root' user. SL5) (d) RHEL (4.tar. FC4. Here is the sample of GTAI configuration file with comments Copyrights reserved CARE@MIT 3 .
Copyrights reserved CARE@MIT 4 .g LRMS:SGE LRMS:PBS #GLOBUS_VERSION: Version of Globus Tool Kit #e.0.g IP_ADDRESS: 10.16.1” or “globus4.g GLOBUS_VERSION:globus4.2.2.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.0.g USERNAME:guser01 USERNAME:guser01 #LRMS: Name of the Local Resource Management System. (PBS or SGE ) #e.0.1 IP_ADDRESS:172.0.Sample “auto.0” or “globus 4.7” or “globus4.0.3 GLOBUS_VERSION:globus4.16.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.51 #USERNAME: Name of the third party user for getting user certificate #e.10.10.0.2.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.7 #GLOBUS_CONFIG_OPTION: Globus Tool Kit Configuration Options #e.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.8” or “globus4.
5.0. repeat the previous step ( (vi) (a)) and modify accordingly.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.6. JAVA_HOME=/usr/java/jdk1.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.(vi) Globus installation requires the setting of Environment variables .1 PBS_HOME=/var/spool/PBS GLOBUS_LOCATION=/usr/local/globus4.27 JUNIT_HOME=/usr/local/junit3. 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” .4 CATALINA_HOME=/usr/local/tomcat5.jar:$CLASSPATH:$JUNIT_HOME/junit.8.0 ANT_HOME=/usr/local/ant1. Copyrights reserved CARE@MIT 5 .
globus.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. Trouble shooting : It is recommended for the users to subscribe for gtautoinstalluser groups (http://dev.gz (4) README (viii) Run the script GTAI_install. 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. Registered users can mail to email@example.com. A complete log information of the Globus installation can be obtained from file “/tmp/log. (1) auto.sh (3) GridSoftware.cfg (2) GTAI_install. Ensure the following files are present in this location.txt”.tar.sh as shown below /bin/sh GTAI_install.(vii ) Go to the location /usr/local (cd /usr/local).org for any queries and errors.txt” (ix) After the installation complete.org/wiki/Incubator/GT_Auto_Install) for any kind of support regarding the globus toolkit installation. a message is displayed about the status of the installation. Copyrights reserved CARE@MIT 6 . This can be done using the command "ls" in the location /usr/local.
52:8443/wsrf/services/AdminService : https://220.127.116.11:8443/wsrf/services/mds/test/usefulrp/IndexService : https://172.16.10.10.52:8443/wsrf/services/CASService : https://172.52:8443/wsrf/services/CounterService * * * * : https://172.16.10.52:8443/wsrf/services/AuthzCalloutTestService : https://172.16.Verification of Globus Toolkit Verification of Globus toolkit requires the following steps (i) Testing of Globus container (a) As root user.52:8443/wsrf/services/ContainerRegistryEntryService : https://172.52:8443/wsrf/services/mds/test/usefulrp/IndexServiceEntry Note : Globus services may vary depending upon the versions.16.16.52:8443/wsrf/services/mds/test/httpsource/IndexService : https://172.16.10.10.10.52:8443/wsrf/services/AttachmentTestService : https://172.16.52:8443/wsrf/services/mds/test/httpsource/IndexServiceEntry : https://18.104.22.168.52:8443/wsrf/services/mds/test/subsource/IndexService : https://22.214.171.124.16.52:8443/wsrf/services/mds/test/subsource/IndexServiceEntry : https://172.16.16.10. Copyrights reserved CARE@MIT 7 .52:8443/wsrf/services/ContainerRegistryService : https://172. 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 : https://172.16.
.org/metadata/2005/02" .2.org/glue/ce/1.1" ns1:HostName="autoinstall2.1" xmlns:metric="http://mds. <ns9:AggregatorData> <ns1:GLUECE xmlns:ns1="http://mds. 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.grid" ns1:LRMSType="Fork" ns1:LRMSVersion="1.globus. Sample output <ns0:IndexRP xmlns:glue="http://mds. .globus.(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.org/glue/ce/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 .1"> <ns1:ComputingElement ns1:Name="default" ns1:UniqueID="default"> <ns1:Info ns1:GRAMVersion="4.globus. .
grid f /tmp/rft.(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.grid:2811/etc/group gsiftp://autoinstall2.txt” is similar to that of the one “/etc/group” Copyrights reserved CARE@MIT 9 .xfr with the following contents true 16000 16000 false 1 true 1 null null false 10 gsiftp://autoinstall2.txt Note: Replace the content “autoinstall2.grid” with your hostname.xfr Note: Replace the content “autoinstall2.grid:2811/tmp/rftTest.grid” with your hostname. (d)Run the command rft h autoinstall2. (e) Verify the contents of the destination file “rftTest.
Done...(iv)Verification of globus component GRAM. Note : (i) Make sure that globus container is running.....Done.Done. Cleaning up any delegated credentials.grid” Copyrights reserved CARE@MIT 10 ..Done. Submitting job. (ii)Your should obtain the hostname of your machine as of the output “autoinstall2..grid Current job state: CleanUp Current job state: Done Destroying job. (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. Job ID: uuid:35489900e85811dd9fab001e908e0d8b Termination time: 01/22/3009 07:42 GMT Current job state: Active Current job state: CleanUpHold autoinstall2.