GT 4.0 Component Fact Sheet: Replica Location Service (RLS)

1. Brief component overview

The Replica Location Service (RLS) allows the registration and discovery of replicas. An RLS maintains and provides access to mapping information from logical names for data items to target names. These target names may represent physical locations of data items, or an entry in the RLS may map to another level of logical naming for the data item.

2. Summary of features

Features New in GT 4.0

  • Bulk exists API to check existence of LFN, PFN or LRC entries.
  • globus-rls-cli exists and bulk exists commands.
  • Rename and bulk rename API to rename LFN or PFN entries in LRC. Renaming LFNs causes an LRC to RLI update to reflect changes at the RLI.
  • globus-rls-cli rename and bulk rename commands.
  • globus-rls-aggregatorsource.pl script that queries an RLS site's statistics and returns a well-formed XML record for use as a MDS aggregator source.

Other Supported Features

  • Comprehensive C and Java library for catalog manipulation, index queries, and administrative tasks.
  • Command line (globus-rls-cli) tool for client operations on catalogs and indexes.
  • Command line (globus-rls-admin) tool for administrative tasks.

Deprecated Features

  • None

3. Usability summary

Usability improvements for RLS:

  • The RLS user interface has remained unchanged from previous releases. The primary improvements made to RLS have been in the area of the stability and reliability of the service. It has been tested thoroughly in wide area environments and shown to withstand various adversities.

4. Backward compatibility summary

Protocol changes since GT 3.2

  • None

API changes since GT 3.2

  • globus_result_t globus_rls_client_lrc_exists_bulk (globus_rls_handle_t *h, globus_list_t *keylist, globus_rls_obj_type_t objtype, globus_list_t **str2bulk_list) added to support bulk exists on the LRC catalog.
  • globus_result_t globus_rls_client_rli_exists_bulk (globus_rls_handle_t *h, globus_list_t *keylist, globus_rls_obj_type_t objtype, globus_list_t **str2bulk_list) added to support bulk exists on the RLI index.
  • globus_result_t globus_rls_client_lrc_renamelfn (globus_rls_handle_t *h, char *oldname, char *newname) added to support rename of LFN in the LRC catalog.
  • globus_result_t globus_rls_client_lrc_renamelfn_bulk (globus_rls_handle_t *h, globus_list_t *str2_list, globus_list_t **str2bulk_list) added to support bulk rename of LFNs in the LRC catalog.
  • globus_result_t globus_rls_client_lrc_renamepfn (globus_rls_handle_t *h, char *oldname, char *newname) added to support rename of PFN in the LRC catalog.
  • globus_result_t globus_rls_client_lrc_renamepfn_bulk (globus_rls_handle_t *h, globus_list_t *str2_list, globus_list_t **str2bulk_list) added to support bulk rename of PFNs in the LRC catalog.
  • ArrayList org.globus.replica.rls.RLSClient.LRC.existsBulk(ArrayList strlist, int objtype) added to support bulk exists on the LRC catalog.
  • ArrayList org.globus.replica.rls.RLSClient.RLI.existsBulk(ArrayList strlist, int objtype) added to support bulk exists on the RLI index.
  • void org.globus.replica.rls.RLSClient.LRC.renameLFN(String name, String newname) added to support rename of LFN in the LRC catalog.
  • ArrayList org.globus.replica.rls.RLSClient.LRC.renameLFNBulk(ArrayList str2list) added to support bulk rename of LFNs in the LRC catalog.
  • void org.globus.replica.rls.RLSClient.LRC.renamePFN(String name, String newname) added to support rename of PFN in the LRC catalog.
  • ArrayList org.globus.replica.rls.RLSClient.LRC.renamePFNBulk(ArrayList str2list) added to support bulk rename of PFNs in the LRC catalog.

Exception changes since GT 3.2

  • None

Schema changes since GT 3.2

  • None

5. Technology dependencies

RLS depends on the following GT components:

  • globus_core
  • globus_common
  • globus_io
  • globus_gssapi_gsi
  • globus_usage

RLS depends on the following 3rd party software:

  • RDBMS: MySQL, PostgreSQL, or Oracle
  • ODBC manager: iODBC
  • ODBC driver: MyODBC, psqlODBC, or Oracle

6. Tested platforms

Tested platforms for RLS include most 32-bit flavors of Linux and UNIX, including RedHat, Solaris, and others.

7. Associated standards

Associated standards for RLS:

  • The RLS is implemented as a conventional service and, as such, does not conform to the WSRF or other WS set of specifications.

8. For More Information

Click here for more information about this component.