Software Links
Getting Started
- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide (coming soon)
- Migrating from GT2
- Migrating from GT3
Reference
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces (coming soon)
- Resource Properties
- Samples
- Glossary
- Performance Studies (coming soon)
Manuals
Common Runtime
Security
- Non-WS (General) Security
- WS Java Security
- Message-level
- Authz Framework
- CAS
- Delegation Service
- MyProxy
- GSI-OpenSSH
- SimpleCA
- SGAS
Data Mgt
MDS4
Execution Mgt
Table of Contents
The Replica Location Service (RLS) is a standalone server (i.e., it is not deployed in a Web services container) that provides for the registration and lookup of replica information. Within the RLS, there are two types of services, a catalog service and an index service.
The Local Replica Catalog (LRC) maintains a catalog of replica information. Replica information in the RLS is maintained in the form of mappings 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.
In addition to the LRC, the RLS also exposes the Replica Location Index (RLI). The RLI maintains an index of logical names which indicates the LRC services(s) that have mappings for the specific logical names. The LRC generates an index of its logical names and pushes the index to one or more RLI services.
In a typical deployment, the RLS will be deployed in conjunction with one or more Storage Elements (SE). The LRC will be used to store mappings from logical names for data sets to the physical file locations as managed by the SEs. The LRC then sends an index of its contents to its associated RLI service as well as multiple remote RLI services at collaborating sites. Clients interested in a particular logical name will first query a RLI service to find the LRC services, then they will query one or more LRC services to find the target names (which may correspond to storage location URLs).
Features New in GT 4.1.3
- A Web service interface for RLS has been developed and is seperately distributed as WS-RLS (see WS Replica Location Service (WS RLS) for more information).
Other Supported Features
- Comprehensive C and Java library for replica registration, replica lookup, replica attributes, 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
The following changes have occurred for RLS since the last stable release, 4.0.5:
- Revised documentation with particular focus on build and configuration procedures.
- Updated setup package to eliminate mysql specific references and include unixODBC settings.
- Added odbc.ini file to setup package and provided default settings to work with the psqlodbc driver now included with the GT bundle.
- Minor bug fixes.
The following problems and limitations are known to exist for RLS at the time of the 4.1.3 release:
- Threading/Libc Problems: set LD_ASSUME_KERNEL=2.2.5 in your environment and see Section 2, “Debian” for more information.
- Bug 2601: Missing 'sigset' linking error
- Bug 2821: GT3.9.5: jni.h not found when compiling RLS on MacOS X
- Bug 3253: GT4 build fails on Mac OS X 10.4 Tiger
- Bug 3656: ACLs cannot be modified dynamically
- Bug 3828: RLSClient crashes when a null parameter is passed to a method
- Bug 4114: Support needed for Java RLS Client APIs on 64-bit platforms (patch available)
- Bug 4141: regexec call in auth.c's auth_getperms allows wrong perms on localuser acls
- Bug 4142: globus-rls-admin -s always indicates RLI does not exist
- Bug 4512: rls query returns incomplete result on 64bit system (patch available)
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: unixODBC, iODBC
- ODBC driver: MyODBC, psqlODBC, or Oracle
Tested platforms for RLS include most 32-bit flavors of Linux and UNIX, including RedHat, Solaris, and others.
Protocol changes since GT 4.0.5
- None
API changes since GT 4.0.5
- None
Exception changes since GT 4.0.5
- None
Schema changes since GT 4.0.5
- None
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.
See Replica Location Service (RLS) for more information about this component.