Installing GT 5.2.2

The GT 5.2.2 release provides source and binary RPM packages for CentOS 4, 5, and 6; Fedora 15, 16, and 17; RedHat Enterprise Server 5 and 6; and Scientific Linux 5 and 6, and a set of .deb packages for several Debian and Ubuntu versions, including Debian 6.0 "squeeze" and 7.0 testing, and Ubuntu 10.04LTS, 10.10, 11.04, 11.10, and 12.04LTS.

This section will show how to set up and use the Globus RPM repository. If your distribution has Globus 5.2.2 packages within its repository, you can skip to "Installing the Toolkit".

The repo configuration packages for the various binary (RPM and deb) repositories can be found at the package download directory. These packages contain the APT or YUM repository definition, the public key used to verify the packages, and a yum group or tasksel group definition file for more easily installing bundles of related packages.

The RPMS in the OS-specific repositories are located at stable repository and testing repository.

The Debian packages in the OS-specific repositories are located at stable repository and testing repository.

The stable repository contains the current release plus all published update packages. The testing repository contains the versions from the latest successful automated build. Packages in the testing repository will be updated more frequently than those in the stable repository.

To install from binary RPMs, get the appropriate configuration rpm from the link above, install it with

# rpm -i Globus-5.2-stable-config.distro.noarch.rpm

To install from binary debs, get the appropriate configuration deb from the link above, install it with

# dpkg -i globus-repository-5.2-stable-distro_0.0.3_all.deb
# apt-get update

The components of the toolkit can be installed separately, or all at once. This section will show how to install various components, on both RPM based and Debian based Linux systems.

# yum install PACKAGENAME

# apt-get install PACKAGENAME

Starting with GT 5.2, the package repositories included with the repo configuration packages will have updates enabled. That means that all major bug fixes and security issues for GT 5.2.2 can be easily installed via yum or apt-get. These updates will be published in the GT 5.2 updates rss feed. Also, this means that when the next point release is made, collecting other minor bug fixes, the upgrade can be done via yum or apt-get without installing a new repository definition package.

	Note
	To disable the automatic update feature for Debian-based distributions, comment out the 5.2.2 Updates deb and deb-src lines in /etc/apt/sources.list.d/globus-stable.list. To disable the automatic update feature for RPM-based distributions, locate the Globus-updates section of the /etc/yum.repos.d/Globus-stable-config.OS.repo file, and modify it so the enable=1 line reads enable=0.

To build the Globus Toolkit from the source installer, first download the source from download page, and be sure you have all of the following prerequisites installed.

This table shows specific package names (where available) for systems supported by GT 5.2.2:

	Note
	In order to use the GNU versions of sed, tar, and make on Solaris, put /usr/gnu/bin at the head of your path. Also, to use all of the perl executables, add /usr/perl5/bin to your path.

Your next step is to setup security, which includes picking a CA to trust, getting host certificates, user certificates, and creating a grid-mapfile. The next three chapters cover these topics.

With security setup, you may start a GridFTP server, and configure GRAM5. You may also start a GSI-OpenSSH daemon, or setup a MyProxy server. The following chapters will explain how to configure these technologies. If you follow the chapters in order, you will make sure of performing tasks in dependency order.

The updates available in the native packages described above are also published as GPT source packages on the updates page. To install update packages, use the command

globus$ gpt-build -update package-name flavors

For the update command, package-name is the full path to the update tarball you've downloaded, and flavors is the list of binary flavors that you have installed (typically gcc32dbg or gcc64dbg.

Your best option is to use an already existing CA. You may have access to one from the company you work for or an organization you are affiliated with. Some universities provide certificates for their members and affiliates. Contact your support organization for details about how to acquire a certificate. You may find your CA listed in the TERENA Repository.

If you already have a CA, you will need to follow their configuration directions. If they include a CA setup package, follow the CAs instruction on how to install the setup package. If they do not, you will need to create an /etc/grid-security/certificates directory and include the CA cert and signing policy in that directory. See Configuring a Trusted CA for more details.

This type of certificate is best for service deployment and Grid inter-operation.

SimpleCA provides a wrapper around the OpenSSL CA functionality and is sufficient for simple Grid services. Alternatively, you can use OpenSSL's CA.sh command on its own. Instructions on how to use the SimpleCA can be found in Installing SimpleCA.

SimpleCA is suitable for testing or when a certificate authority is not available.

This section describes the requirements placed on firewalls at sites containing Globus Toolkit clients. Note that often jobs submitted to sites running Globus services will act as clients (e.g. retrieving files needed by the job, spawning subjobs), so server sites will also have client site requirements.

This section describes firewall policy requirements at sites that host Grid services. Sites that host Grid services often host Grid clients, however the policy requirements described in this section are adequate for clients as well.

Controllable ephemeral ports in the Globus Toolkit can be restricted to a given range. setting the environment variable GLOBUS_TCP_PORT_RANGE can restrict ephemeral ports. The value of this variable should be formatted as min,max (a comma separated pair). This will cause the GT libraries (specifically GlobusIO) to select port numbers for controllable ports in that specified range.

% GLOBUS_TCP_PORT_RANGE=40000,40010
% export GLOBUS_TCP_PORT_RANGE
% globus-gass-server
https://globicus.lbl.gov:40000
^C
%

This environment variable is respected by both clients and servers that are started from within the environment in which it is set. There are better ways, however, to configure a globus-job-manager or a GridFTP server to restrict its port range.

The libtool library is no longer distributed with MacOS in Mountain Lion. Install the latest libtool from the GNU libtool source mirror prior to building Globus from the source installer. To do so in a way that will work, you'll need to configure libtool with --program-prefix=g to cause the libtool script to be named glibtool to avoid conflicts with the OS X libtool program which provides different functionality than GNU libtool.

If you install libtool in a directory other than your Globus installation directory, you'll need to add it to your build environment, by adding CPPFLAGS="-ILIBTOOL-INSTALLDIR/include" and LDFLAGS="-LLIBTOOL-INSTALLDIR/lib" to your environment when compiling with the installer.