GT 5.0.0 Release Notes


1. Introduction

The GT development team is pleased to make a new stable release of the Globus Toolkit available for download. Most components of GT5 are incremental updates (numerous bug fixes and new features) over their GT4 counter-parts (e.g. GridFTP, RLS, MyProxy, GSI-OpenSSH). Some components of GT4 are not included in GT5 (e.g. GT4 Java Core, WS-GRAM4, RFT), to be replaced by new software under development (e.g. Crux, Globus.org Service). And GRAM has been vastly improved by returning to the pre-ws GRAM2 code base and making substantial backward-compatible improvements.

GT4.x releases will continue to be maintained and supported at least through the end of 2010. New users should immediately adopt 5.0.0. Existing users are encouraged to begin evaluating and migrating to GT5. Please contact us if you have questions or problems along the way.

[Note]Note

GT5 does not include any of the Web Service components from GT4.

For highlights of changes in each component, see Section 7, “Summary of Changes Since 4.2.x (by component)”.

2. Obtaining and Installing Software

To download this release, go to the 5.0.0 Download page.

For information on installing this release, go to the 5.0.0 Installation Guide.

2.1. Java Client API Download

GT 5.0.0 does not include any of the CoG JGlobus Java APIs that were included in the GT4 release series.   But, the JGlobus APIs can still be used with the GT5 services.  You can get them directly from the CoG JGlobus releases; see the following link:

http://dev.globus.org/wiki/CoG_jglobus

Consider the following when determining which version of CoG JGlobus to use:

  • The GRAM development team used CoG JGlobus version 1.6.0 for performance testing.

  • The BIRN project used CoG JGlobus version 1.6.0 (plus patches) for GridFTP testing. All patches are included in 1.8.0.

  • At the time of the GT 5.0.0 release, 1.8.0 was the recommended version.  In general, the latest recommended CoG JGlobus version should be used.

3. Documentation

Use the documentation which starts at here.

Feel free to offer any suggestions or feedback using JIRA (the "Documentation" project). Note at the time of release, the documentation feedback box that used to appear at the bottom of each page is not functioning after the recent website redesign. We are working on the matter and will have the feedback box available as soon as possible. Please note that this box is intended for feedback and suggestions only - for support, please read the following section.

4. Support

An overview on GT support can be found here.

5. Licensing

The Globus Toolkit is distributed and licensed for use under the terms of the Apache License, Version 2.0.

To view the licenses of the 3rd party software used by the developers of the Globus Toolkit, click here.

6. Usage Statistics

For full information about usage statistics collected by GT 5.0.0 and how to opt-out, see Usage Statistics Collection by the Globus Alliance.

7. Summary of Changes Since 4.2.x (by component)

7.1. Common Runtime Components

7.1.1. Summary of Changes in XIO

  • The TCP driver has been modified to randomize the selection of ephemeral ports.
  • Minor code cleanups.

7.1.2. Summary of Changes in C Common Libraries

No significant changes have happened for C Common Libraries since GT 4.2.x. See Feature Summary for some minor changes.

7.2. Security

7.2.1. Summary of Changes in GSI

7.2.2. Summary of Changes in MyProxy

GT 5.0.0 contains MyProxy v5.0. MyProxy support for managing trust roots (CA certificates and CRLs) has improved, including a new myproxy-get-trustroots command. See the MyProxy Release Notes for more details on this and other MyProxy versions.

7.2.3. Summary of Changes in SimpleCA

Other than bugfixes, no changes have occurred for SimpleCA since the last stable release, 4.2.x.

7.2.4. Summary of Changes in GSI-OpenSSH

GT 5.0.0 contains GSI-OpenSSH version 4.7. GSI-OpenSSH clients now attempt only GSI authentication by default, rather than the confusing behavior of attempting other SSH authentication methods when GSI authentication fails. (The GSI-OpenSSH server still supports both GSI and non-GSI authentication methods by default, for compatibility with both GSI and non-GSI clients.) See the GSI-OpenSSH Release History for more details on this and other GSI-OpenSSH versions.

7.3. Data Management

7.3.1. Summary of Changes in GridFTP

  • The default flavor of the GridFTP server has been changed to non-threaded.

7.3.2. Summary of Changes in RLS

  • Streamlined startup for RLS.

    When the RLS server was started, initialization previously took anywhere from several seconds to minutes, depending on the number of entries in the RLS database. During this time, users could not issue queries to the RLS database.

    The streamlined startup feature allows users to issue read-only queries to the RLS, during initialization. This is achieved by creating Bloom filters during the initialization, in a seperate thread, and disallowing queries that update the database, so as not to interfere with the Bloom filter creation.

  • Improved support for 64-bit operating systems and better compliance with ODBC specifications.

  • Backward compatible with GT 4 RLS protocols, APIs, command-line interfaces, and databases.

7.4. Execution Management

7.4.1. Summary of Changes in GRAM5

GRAM5 represents a significant improvement from GRAM2 and GRAM4 service implementations. GRAM2's limitation is scalability. GRAM4's is reliability. GRAM5 is both reliable AND scalable. It is important to note that GRAM5 is GRAM2 compatible. There are other improvements as well, like completely rewritten service logging based on the CEDPS logging best practices, Teragrid Gateway Identity support for job auditing, support for job exit codes, and usage stat support.

We have been very encouraged by our performance results, which shows greater than 10x scalability than GRAM2 and roughly 10x reduction in resource consumption on the service host. We welcome your feedback as you integrate GRAM5 into your production grids.

8. Release Notes by Component