Install Prerequisites
From UGP-Wiki
Contents |
[edit] I. Prerequisites
UGP has been tested under Linux Fedora Core 4, 5, 6, and 8. While UGP should work under any version of Linux because most of the code is written in Java, we haven't tested it there. The clusters that are connected together into the Grid can run any operating system and the operating systems don't have to be the same.
When you install the Linux Operating System, make sure you install the development package, because you will need the following required software: tar, sed, zlib, gnu make, perl, sudo, postgresql, ant, gcc 2.95, 3.2 or the latest (but not gcc 4.1 because it has a bug). Please disable SELINUX as it interferes with several applications.
UGP will work with either the SGE or Torque job scheduler. Different clusters connected to the Grid can run different schedulers. However, for SGE you must run version 6.0 or higher. Versions below 6.0 do not properly report back the status of jobs to the Index Service of the Globus Toolkit, and thus the Grid Portal cannot display the job status to the users.
[edit] Before you can install either a Grid Appliance or the Grid Portal
1. As root create login id globus in group globus to use for the installation:
groupadd globus
useradd -d /home/globus -g globus globus
passwd globus
2. Make sure that /home/globus is readable by everyone:
chmod 755 /home/globus
We recommend using userid globus and group globus. Certainly you can install this software as any user except root. However, note that UGP functions are run by this userid, and that you must use the same userid for the Portal and all the Appliances. If you use an id or group other than globus, replace globus with the one you used in the instructions below.
[edit] Before you can install a Grid Portal
1. MySQL
You must install and configure MySQL database. MySQL comes with Fedora and may or may not be installed as part of the system installation. You must be logged in as root to enter these commands:
a. If the MySQL server is not installed, install it as follows:
yum install mysql mysql-server
Remove existing (if any) /var/lib/mysql directory:
mv /var/lib/mysql /var/lib/mysql.old
Start MySQL:
/etc/init.d/mysqld start
b. Set the MySQL root password:
/usr/bin/mysqladmin -u root password 'new-password'
Replace new-password with the new MySQL root password that you will
use. Enclose new-password with single quotes as shown above.
If you are unable to set the MySQL root password or forget the MySQL
root password, you should try entering the following commands as root:
user]$/etc/init.d/mysqld stop
user]$mysqld_safe --skip-grant-tables -u root &
user]$ mysql -u root
mysql>UPDATE mysql.user SET Password=PASSWORD('newpwd') WHERE User=
'root';
mysql>FLUSH PRIVILEGES
mysql> \q;
user]$ /etc/init.d/mysqld stop user]$ /etc/init.d/mysqld start
c. UGP and GridSphere work with various database tables in a database the
is named gridsphere. To create the database named gridsphere, login as
globus and enter:
mysqladmin -u root -p create gridsphere
d. Grant the UGP and GridSphere software access to the MySQL database
named gridsphere that you have just created. They will access the
database via the MySQL non-root user named dbadmin. To start MySQL
enter:
mysql -u root -p
In response to the MySQL password prompt enter the mysql root password
you created in a previous step. At the mysql> prompt enter:
grant all privileges on gridsphere.* to dbadmin@localhost
identified by 'userpass';
grant all privileges on gridsphere.* to
dbadmin@localhost.localdomain identified by 'userpass';
In Fedora Core 6, the database will not work if don't have the
following line in the file: /etc/hosts:
127.0.0.1 localhost
Replace dbadmin and userpass with the username and password that UGP
will use to access the database. Make note of the username and password
you specify as you will either have to enter them in the
portal.properties file for UGP command line installation (db.username=
and db.password= ) or in the Installer GUI for UGP GUI installation.
Enter:
\q
to end the MySQL session.
e. Re-start MySQL (as root):
/etc/init.d/mysqld restart
f. Make sure that My SQL will be started each time the machine is
rebooted:
/sbin/chkconfig --level 35 mysqld on
2. Update /etc/hosts to include the following two lines:
127.0.0.1 localhost
YOURIP youhost.edu
One or the other of them may already be there. Replace YOURIP with the numerical IP address of the machine and yourhost.edu with its alphabetical equivalent.
If you don't have the line beginning with 127.0.0.1 in /etc/hosts, mysql will not work. This will cause the installation of UGP to fail.
3. Download and unpack the UCLAGridPortal package:
tar -xvfz UCLAGridPortal.tar.gz
4. Ant
In order to compile, you must have the file /usr/share/ant/lib/ant.jar
A copy has been included in the UGP distribution for you. If you do not have this file, as root copy 3rdParty/ant.jar to /usr/share/ant/lib. If you do not have a /usr/share/ant/lib directory, issue the following commands as necessary:
mkdir -p /usr/share/ant
mkdir -p /usr/share/ant/lib
and then copy ant.jar and ant-contrib-0.3.jar:
cd UCLAGridPortal
cp 3rdParty/ant.jar /usr/share/ant/lib
cp 3rdParty/ant-contrib-0.3.jar /usr/share/ant/lib
[edit] Before you can install a Grid Appliance
1. User's Home Directories
Cross-mount the filesystem containing user's home directories on the Grid Appliance.
2. Then, login to the Grid Appliance as user globus and set either the SGE_ROOT and SGE_CELL or PBS_HOME environment variable(s) according to the scheduler in use. For example, if globus' shell is bash, you can add lines like the following to the file .bash_profile in the user globus home directory:
export SGE_ROOT=/Volumes/systems/SGE6U1
source $SGE_ROOT/default/common/settings.sh
3. SGE
You must run SGE 6.0 or higher for job status to appear on the Grid Portal.
a. If the architecture of the Grid Appliance differs from the architecture
of the cluster head node, an appropriate SGE executable for the
appliance has to be installed in the $SGE_ROOT/bin directory on the
cluster head node.
b. Cross mount the filesystem in which SGE has been installed on the
cluster head node to the Grid Appliance.
c. As the SGE root user, on the cluster head node, execute the following
command to activate SGE reporting:
$SGE_ROOT/bin/lx24-x86/qconf -mconf
lx24-x86 is the SGE architecture name for x86 machines. Replace this
with the appropriate SGE architecture name for your hardware.
Issuing this command will place you in the vi editor, edititing a
single line file. Edit that file to look like:
reporting_params accounting=true reporting=true flush_time=00:00:15
joblog=true sharelog=00:00:00
and save it back. This will create a file named:
$SGE_ROOT/$SGE_CELL/common/reporting
Check to see that it is accessable from the Grid Appliance.
4. Torque
a. You must install Torque, as a client, on the Grid Appliance in the same
path as it is installed in on the cluster head node.
b. You must cross-mount the directory containing Torque's server log file:
$PBS_HOME/server_logs
and this directory only, on the Grid Appliance in order for the job
status reporting to work.
5. Firewall
You must configure iptables so that the Grid Appliance can communicate with the Grid Portal within the Globus Toolkit port range. See the section titled Firewall Setup in this document or the document: www.globus.org/ toolkit/security/firewalls/Globus-Firewall-Requirements-9.pdf. Note that we are using Globus Toolkit 4.x.
6. You must know the Grid Portal hostname (for command line installation, see the instructions below to edit the build.properties file).
7. Set up the CA trust relationship:
(If you are from a campus of the UC system, you will use the CA running on portal.ucgrid.org. Skip these instructions about setting up the CA trust relationship. )
a. Copy the file named something like:
.globus/simpleCA/globus_simple_ca....tar.gz
from the home directory of the user running the CA on the machine
running the CA (probably the /home/globus on the Grid Portal) to the
3rdParty/TrustedCA subdirectory of the UGP distribution. You must do
this for each CA you will use. Normally only a single CA is used, but
as shipped the UGP comes with the ability to use two in the 3rdParty/
build.xml file.
☆ If you are installing a stand-alone Grid Portal or the
highest-level Grid Portal in a Grid hierarchy, check the box in the
GUI installer to have it install the CA with your Portal
installation. That is the CA that you will use.
☆ If you are installing a campus GRID Portal or a lower-level Grid
Portal, you should install it without a CA. You should copp the
globus_simple_ca....tar.gz file from portal.ucgrid.org, if a
University of California Campus, or from your highest-level Grid.
☆ If you are installing a Grid Appliance, copy the file from Grid
Portal that has the CA. The Grid Portal must be completely
installed before you can configure the CA trust relationship on any
of the Appliances.
b. Now modify the file build.xml and modify the property whose name is
simpleca.file.1 and set the value to the name of the file you copied.
8. On Fedora core 6 systems and above, modify /etc/sudoers and comment out the line that reads:
Defaults requiretty
GRAM (batch) jobs cannot be submitted under the users' login ids unless you do this.
