Globus Toolkit 3.9.5: Migrating from GT2 to GT4

Introduction

This guide provides information for migrating from GT2 to GT 3.9.5.

Migrating to Globus Toolkit 3.9.5

[include porting information that applies to the overall toolkit]

Migrating by component

Common Runtime Components

C WS Core

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]

Java WS Core

Not applicable. This component did not exist in GT2.

Security: WS Authorization & Authentication

Authorization framework

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]

CAS

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]

Delegation Service

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]

Message/Transport-level Security

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]

Data Management

GridFTP

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]

RFT

This does not apply to RFT.

RLS

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]

Information Services

WS MDS (MDS4)

Although the basic functionality remains the same for MDS in GT4, the architecture, standards used, and implementation have changed significantly in GT2. The following table shows a mapping of some GT2 concepts to GT4 concepts.

Description GT2 Version GT4 Version
Format of data describing a resource LDAP data hierarchy XML data document
Query language LDAP queries XPath queries
Wire protocol for queries LDAP WS-ResourceProperties
APIs used for queries LDAP APIs WS Core APIs
Command-line clients used for queries grid-info-search wsrf-get-property, wsrf-get-properties, wsrf-query
Available GUIs Various LDAP browsers WebMDS (tech preview)
Wire protocol for subscription/notification Not supported WS-Notification
APIs used for subscription/notification Not supported WS Core APIs
Security support SAML-based security using X.509 user, proxy and host certificates HTTPS-based security using X.509 user, proxy and host certificates
Queryable index of aggregated information GIIS, which publishes data using the LDAP-related standards listed above WS MDS Index Server, which publishes data using the WSRF-related standards listed above
Queryable source of non-aggregated information GRIS, which uses information providers to gather data from services and then publishes that data the LDAP-related standards listed above Individual web services, which publish data about their own resources using WSRF-related standards listed above.
Index registration mechanism MDS servers (GRIS's and, in some cases, GIIS's) register themselves with a GIIS. An MDS server is configured to register itself to a remote index by editing the local MDS server's grid-info-resource-register.conf file, providing information about the location of the remote index to register to and timeout values for the registration WS MDS Index servers maintain aggregating service groups that include registration information (timeout values, the mechanism to use to acquire information, and additional mechanism-specific parameters) The registration is accomplished by adding an entry to an aggregating service group via the mds-servicegroup-add command.
Mechanism used by an index to collect information GIIS's send LDAP queries to remote serves. WS MDS Index servers use a plugin-based architecture to support several mechanisms to collect information. The Globus Toolkit supplies plugins that support collecting information via polling (resource property queries), subscription/notification, and by program execution.

Execution Management

WS GRAM (GRAM4)

[Describe how to migrate your component from GT2 to GT4. If this does not apply to your component because it did not exist or is relatively the same, please explicitly state that.]