Fwd: [Globus-discuss] GTbuild - a tool to automate GT2 bundle build/install/management

Robert Olson olson at mcs.anl.gov
Mon Feb 24 06:57:15 CST 2003


>From: Jeff Forys <jeff.forys at hp.com>
>To: discuss at globus.org
>Subject: [Globus-discuss] GTbuild - a tool to automate GT2 bundle 
>  y>ae4YeW'vR8^``RE-Qs(XcIXJxZ8hlQF%}J?L7t)VX9);"6RrXNN)ptIC0>Z1+R_lY1aL(ojp%
>X-Url: http://surf.to/forys
>Date: Fri, 21 Feb 2003 17:41:49 -0500
>X-Mts: smtp
>X-Spam-Status: No, hits=1.2 required=5.0 tests=MSG_ID_ADDED_BY_MTA_3 
>X-Spam-Level: *
>Sender: owner-discuss at globus.org
>Hi folks,
>In talking to people at GlobusWorld, there seemed some admins out
>there who wanted an easier way to build/install the GT2 bundles
>and deal with maintaining multiple versions on the same system.
>One of the tools we developed to manage our HP Internal Grid
>("Ingrid") is "GTbuild", a Bourne shell script, which features:
>    o Prerequisite build checks (for perl, GNU tar, etc).
>    o Automated/unattended GPT, Globus build (from source or binary
>      bundles), post-install, GSI-setup.
>    o Automated removal of GPT, Globus, source and/or install dirs.
>    o Everything configurable through a config file (although the
>      defaults usually suffice).
>    o Registration feature (see below).
>    o A manual page!
>So now, to configure a new system, we effectively untar any
>machine-specific prerequisite apps, run the command:
>    % GTbuild -Gprv std
>edit the services/inetd files, request the certificates and were
>done (actually, for Ingrid, all of these steps are automated).
>The registration feature is especially useful.  When used, every
>Globus installation on a system is registered under a common
>directory (default is "/globus").  The currently running version
>(i.e., that which inetd spawns) is identified by the "current"
>symlink in the registration directory.
>When a user arrives on a system, they blindly run the command:
>    % source /globus/current/gridinit.csh
>To set up their environment (including GLOBUS_LOCATION, etc) and
>auto-source the version-specific Globus "globus-user-env" script.
>They are now ready to run Globus.  Similarly, a user who wants
>to use a specific Globus release could run:
>    % source /globus/gt-2.2.2-1/gridinit.csh
>Even better, when the admin installs a new version somewhere,
>they simply change the "/globus/current" simlink to point to
>it and -- since the inetd config file uses the symlink -- the
>system is automatically running the new (or old) version.
>There's more information on this feature in the manual page.
>GTbuild currently supports Linux, HP-UX, Tru64, and Solaris;
>porting it to other systems should be trivial.  It's been
>used for GT2.2.{2,3,4}.
>HP is making this available under a BSD-style license in the hopes
>that others will find it useful.  While GTbuild is not officially
>supported by HP, comments/questions/fixes/ports may be sent to us
>at <globus.support at hp.com>.  Incidentally, we are still trying to
>determine how/if GTbuild fits into GT3.
>You can snarf GTbuild from our web site:
>    http://www.hp.com/products/globus
>Or, directly at these URLs:
>    http://www.tru64unix.compaq.com/globus/gt22/GTbuild
>    http://www.tru64unix.compaq.com/globus/gt22/GTbuild-man.html
>Hope this helps,
>P.S. We also just updated our HP-UX and Tru64 Globus build notes
>      for the GT 2.2.4 release.

More information about the ag-dev mailing list