NAME
GTbuild - Globus Toolkit bundle builder/installer
SYNOPSIS
GTbuild [-GPRbgiprv] [-c <cfg>] [-f <flavors>] [-m <mpi>] [<target>]
GTbuild [-c <cfg>] ( -clean | -distclean ) [<target>]
GTbuild -manual
DESCRIPTION
GTbuild manages the intricacies of building, installing, configuring and registering the Globus Toolkit. To easily tailor an installation to a local environment, GTbuild can utilize a configuration file (see CONFIGURATION). Multiple versions of the Globus Toolkit are supported through a registration directory (see REGISTRATION). GTbuild has been tested on HP-UX (IA-64, PA-RISC), Linux (Alpha, IA-32, IA-64), Tru64 (Alpha), and Solaris (SPARC). Other platforms should also work with little or no modification.
The first usage synopsis is used to build and install the Globus Toolkit. A target must be specified to start a build; without one, GTbuild only checks that prerequisite applications are available. To initiate a build, one of the following targets must be specified:
gpt Build the Globus Packaging Toolkit (GPT). This target is automatically invoked when any other target is specified and it has no effect if the GPT has already been installed.
std Build the standard Globus bundles (client, server, and SDK bundles for Data Management, Resource Management, and Information Services).
rep (GT2-only)
Build the replica services bundle.
usr (GT2-only)
Build a user-defined set of bundles.
all Build everything (in the order gpt, std, rep, usr).
In the case of the GPT, the build takes place relative to the BLDDIR_GPT directory [/opt/globus/gpt-2.2.9/src]; all other builds (and post-build procedures) occur relative to the BLDDIR_GTK directory [/opt/globus/globus-2.4.3/src]. Output from each Globus command is saved in a uniquely named file in its respective build directory.
When initiating a build, the following flags are meaningful:
-b Use binary bundles (a source build is the default).
-c <cfg>
Use the named configuration file to override internal default variables. A configuration file specified in this manner takes precedence over all others.
-m <mpi> (GT2-only)
Build the globus-data-management-sdk source bundle using the specified mpi flavor to support a vendor-supplied MPI (e.g., "mpicc32" for HP MPI).
Post-build procedures include running gpt-postinstall, running setup-gsi, and registration. Apart from a few serious errors (e.g., no Globus installation), the post-build runs to completion irrespective of any displayed error messages. The following flags are used to specify post-build procedures:
-g/-G (GT2-only)
For GT2, this flag runs the Globus setup-gsi script. The lowercase variant interactively requests setup information while the uppercase variant uses default answers. These flags may only be used by the superuser.
-g/-G (GT4-only)
For GT4 builds, this flag runs the setup-globus-gram-job-manager command. This is necessary when doing a postinstall before certificates in the "/etc/grid-security" directory are set up. There is no difference between upper and lowercase variants and unprivileged users may use this option.
-p/-P
Run the Globus gpt-postinstall script (GT2) or make postinstall command (GT4). The uppercase variant causes the "-force" flag to be passed to GT2's gpt-postinstall script.
-r/-R
Register (or re-register) an existing Globus installation in the directory specified by GTKREG_DIR [/var/HPgrid/globus]. If the uppercase variant is used, an existing duplicate registration will be removed (rather than reused); this should never be necessary (see REGISTRATION).
-v Run the Globus gpt-verify script.
Here are a couple GTbuild sample commands:
% GTbuild std
Build and install the Globus toolkit standard distribution.
% GTbuild -pr -c /tmp/GTbuildrc
Run gpt-postinstall and register the Globus installation built from the configuration file "/tmp/GTbuildrc".
% GTbuild -cGprv /tmp/GTbuildrc std
Build, install, configure and register the Globus Toolkit distribution without any human intervention. For GT2 builds, since the "-G" option was specified, this command must run as the superuser.
In addition to "-clean", remove the build directory for the named target (BLDDIR_GPT [/opt/globus/gpt-2.2.9/src] and/or BLDDIR_GTK[/opt/globus/globus-2.4.3/src]).
The third usage synopsis displays this manual page formatted for a tty. However, if "raw" is appended to the flag (e.g., "-manualraw"), the unformatted manual page is output and may be formatted for a printer (e.g.,"GTbuild -manualraw | groff -man | lpr").
Exit status is normally 0; if the user specifies an invalid parameter, 1 is returned. If a build error occurs, exit status is 2. Post-build errors are indicated with an exit status of 3.
CONFIGURATION FILE
If all platforms had the same file system layout and system administrator, the Globus Toolkit could be built and installed in the same location on every system. As this is impossible, GTbuild was engineered to be configurable through the use of Bourne shell variables and/or a configuration file. Most of the default values are correct across platforms and any specified variables simply override the default definitions.
There are two ways to override a default: either by setting it as an environment variable (setenv, set/export), or by using a configuration file (mixing these two methods is not recommended). If the "-c" argument is provided, the named configuration file is used. Otherwise, if the $GTBUILDRC environment variable is defined, it must identify the configuration file. Finally, if a ".GTbuildrc" file exists in the users home directory, it will be sourced.
The following example configuration file builds the Globus 2.4.3 release from the Globus-mirrored source tree at "/tmp/globus-2.4.3" and installs it at GT_DEST [/opt/globus]:
VERS_GTK=2.4.3
GT_DIST=/tmp/globus-${VERS_GTK}
This next configuration file builds Globus 2.2.2 using a patched release tree and installs it under "/usr/local/globus":
VERS_GTK=2.2.2
GT_DIST=/grid/gt2/2.2/${VERS_GTK}-patched
GT_DEST=/usr/local/globus
# ensure /usr/local/bin is at head of $PATH
PATH=/usr/local/bin:$PATH
export PATH
This next configuration file builds Globus 4.0.1 using a patched release tree and installs it under "/home/globus":
VERS_GTK=4.0.1
GT_DIST=/grid/gt4/4.0/4.0.1-patched
GT_DEST=/home/globus
GTKREG_DIR=/tmp/globus/regdir
Here is the complete list of commonly used configuration variables, along with their current values (in the brackets).
VERS_GPT
Version of the Globus Packaging Toolkit.
[2.2.9]
VERS_GTK
Version of the Globus Toolkit.
[2.4.3]
GT_DIST
Root of globus distribution tree. This is only used as a convenience when initializing the SRCDIR_* and BINDIR_* variables.
[/tmp/2.4.3]
GT_DEST
Root of target build directory. This is only used as a convenience when initializing the DSTDIR_* and BLDDIR_* variables.
[/opt/globus]
GT4_CONFIG
Specify additional parameters to GT4 "configure" script. The "--with-flavor" and "--prefix" flags are determined automatically, however if they are specified they will override the "-f flavor" flag and DSTDIR_GTK variable, respectively.
[ ]
SRCDIR_GPT
Directory containing Globus Packaging Toolkit source tarball.
[/tmp/2.4.3/gpt]
SRCDIR_STD
Directory containing Globus standard source bundles.
[/tmp/2.4.3/bundles/src]
SRCDIR_REP
Directory containing Globus replica source bundle.
[/tmp/2.4.3/bundles/src]
SRCDIR_USR
Directory containing User-defined source bundle(s).
[/tmp/2.4.3/extra/src]
BINDIR_STD
Directory containing Globus standard binary bundles.
[/tmp/2.4.3/bundles/bin]
BINDIR_REP
Directory containing Globus replica binary bundle.
[/opt/globus/globus-2.4.3]
BLDDIR_GPT
Directory in which GPT build takes place.
[/opt/globus/gpt-2.2.9/src]
BLDDIR_GTK
Directory in which bundles are built and post-build procedures take place.
[/opt/globus/globus-2.4.3/src]
GTKREG_DIR
Globus registration directory.
[/var/HPgrid/globus]
The following configurables are also available but usually do not require modification:
GPTBLD_CMD
Location of the GPT build command.
[/opt/globus/gpt-2.2.9/sbin/gpt-build]
GPTBLD_ARG
Arguments passed to GPTBLD_CMD.
[-install-only]
GPTINS_CMD
Location of GPT install command.
[/opt/globus/gpt-2.2.9/sbin/gpt-install]
GPTINS_ARG
Arguments passed to GPTINS_CMD.
[ ]
UMASK_OPT
Default file mode creation mask.
[022]
BNAM_GTK
Platform-specific binary bundle name.
[alphaev56-dec-osf5.1]
SRC_GPT, SRC_STD, SRC_REP, SRC_USR
Names of files containing the source Globus Packaging Toolkit tarball, standard source bundles, replica source bundle and user-defined source bundle(s), respectively. These all use VERS_GTK and, theoretically, should never have to be changed.
BIN_STD, BIN_REP, BIN_USR
Names of files containing the standard binary bundles, replica binary bundle and user-defined binary bundle(s), respectively. These all use VERS_GTK and BNAM_GTK and, theoretically, should never have to be one that's already registered. The implication here, is that the names of the Globus installation and registration directories should always include the Globus version number to prevent an incorrect re-registration. Alternately, the "-R" flag can be specified to remove any previously existing registration.
Each registration directory contains the following files:
gpt A symbolic link to the installed GPT used for the build.
gtk A symbolic link to the installed Globus directory.
.GTbuildrc
A file that contains a copy of the configuration file that was used to build Globus. If no configuration file was used, this file will contain all the configurables as they were defined at build time. During a re-registration, this initial ".GTbuildrc" is renamed ".GTbuildrc_orig" and never modified again. Any future re-registrations cause the ".GTbuildrc" to be renamed ".GTbuildrc_prev".
gridinit.sh, gridinit.csh
These are the Bourne shell and C shell start-up scripts that correspond to each registered Globus installation. A source of either script causes the $GPT_LOCATION and $GLOBUS_LOCATION environment variables to be correctly initialized and the corresponding Globus globus-user-env script to be sourced. In addition, if the $GLOBUS_HOSTNAME environment variable was set at build time, it will be initialized here. By default, to ensure a common environment, these scripts also hard-code the users $PATH to that which was used at build time. This behavior can be changed by setting the $GTBUILD_PATH_OPT variable to "blend" (prepend build-time path to existing path) or "save" (do not modify path, but save the build-time path in $GTBUILD_PATH_SAV). With GT4, a globus-devel-env script appeared; this Globus Developer initialization script can be automatically sourced by setting the $GTBUILD_DEVEL_OPT variable to "Yes" before sourcing the gridinit script.
On the first registration, GTbuild installs an "active" symbolic link at the root of the registration directory. The GTactive tool maintains the "active" link. The administrator can then configure system files (e.g., "/etc/inetd.conf") using the "GTKREG_DIR/active/gtk" [/var/HPgrid/globus/active/gtk] and simply change the link whenever switching to a new (or old) Globus version.
AUTHOR
GTbuild was developed by Hewlett-Packard Corporation. While it is not officially supported by HP, you may send questions using the Globus Toolkit Feedback form.
SEE ALSO
GTactive(1), sh(1), csh(1), ln(1), rm(1), umask(1),
"http://www.globus.org", "http://www3.niu.edu/mpi/"
|
Versione stampabile
