Grid Services

The replica location service (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.

http://www.globus.org/toolkit/data/rls/

GridFTP is a protocol defined by Global Grid Forum Recommendation GFD.020, RFC 959, RFC 2228, RFC 2389, and a draft before the IETF FTP working group. The GridFTP protocol provides for the secure, robust, fast and efficient transfer of (especially bulk) data. The Globus Toolkit provides the most commonly used implementation of that protocol, though others do exist (primarily tied to proprietary internal systems).

http://www-unix.globus.org/toolkit/docs/4.0/data/gridftp/

mike4.cct.lsu.edu

helix2.cct.lsu.edu

santaka.cct.lsu.edu

gumbogrid.cct.lsu.edu

gridhub.cct.lsu.edu

RFT is a Web Services Resource Framework (WSRF) compliant web service that provides “job scheduler"-like functionality for data movement. You simply provide a list of source and destination URLs (including directories or file globs) and then the service writes your job description into a database and then moves the files on your behalf. Once the service has taken your job request, interactions with it are similar to any job scheduler. Service methods are provided for querying the transfer status, or you may use standard WSRF tools (also provided in the Globus Toolkit) to subscribe for notifications of state change events.

http://www-unix.globus.org/toolkit/docs/4.0/data/rft/

The Monitoring and Discovery System (MDS) is the information services component of the Globus Toolkit and provides information about the available resources on the Grid and their status.

http://www.globus.org/toolkit/mds/

While there are numerous technologies for providing information about resources in a grid environment, none of the current tools provide the complete set of data required for comprehensive grid-enabled Web portals. The goal for GPIR is to aggregate and cache grid and portal related data collected by other technologies (e.g., MDS, NWS, etc.) and make it available via a single tool using standard Web service queries. GPIR also includes some ‘custom providers’ to provide data not collected by any current grid information system but needed by grid portals and applications developers. GPIR is currently used in production by the TACC User Portal, UTGrid User Portal, and other portals

http://tacc.utexas.edu/projects/gpir/

GridLab Resource Management System (GRMS) is an open source meta-scheduling system, developed under the GridLab Project, which allows developers to build and deploy resource management systems for large scale distributed computing infrastructures. GRMS provides developers of user-level functionalities with a more abstract view of low level and complex Grid technologies. Based on dynamic resource selection and discovery, mapping and advanced scheduling methodology, combined with a feedback control architecture and support from other GridLab Middleware Services, it deals with dynamic Grid environment and resource management challenges, e.g. load-balancing among clusters and various work-load systems, remote job control or file staging support. Therefore, the main goal of GRMS is to manage the whole process of remote job submission and control to various queuing systems (e.g. Condor, PBS, LSF, N1 Grid Engine), clusters systems or resources directly.

http://www.gridlab.org/WorkPackages/wp-9/

MyProxy is open source software for managing X.509 Public Key Infrastructure (PKI) security credentials (certificates and private keys). MyProxy combines an online credential repository with an online certificate authority to allow users to securely obtain credentials when and where needed. Users run myproxy-logon to authenticate and obtain credentials, including trusted CA certificates and Certificate Revocation Lists (CRLs).

http://grid.ncsa.uiuc.edu/myproxy/