This document provides the release notes for all Data Management components for the EDG 2.0 release.

| Local Replica Catalog | Replica Location Index | Replica Metadata Catalog | Replica Manager | Replica Optimization Service | EDG Java Security | VOMS |

Local Replica Catalog (LRC)

Description: One of the two components of the Replica Location Service. The LRC stores GUID to SURL mappings, along with metadata on the physical files and replicas for a given VO

Deployment scenario : One per virtual organization. With the integration of the RLIs in EDG 2.1, the deployment scenario will move to one LRC per SE.

State: Deployed; working stand alone with no interoperation with RLIs

Known Bugs:

• Enforcement of file syntax: Registration of mappings in the catlogs via the RM enforces certain file name formats.
  This is not enforced via the LRC catalog API. How much of the catalog APIs should be exposed is still an open question. Bug # 1007
• Some SQL scripts are deployed to $EDG_LOCATION/etc/ by the configure scripts. They should be in $EDG_LOCATION_VAR/etc. Bug # 1008
• Configuration script depends on R-GMA StreamProducer.props file to publish initial information on service installation. Bug # 1036
• No versioning of SQL schemas. Bug # 1359
• addMapping method throws null pointer after a tomcat restart when the LRC is publishing to RLIs. Bug # 1866
• View all open LRC bugs

Manual Configuration:

• MySQL scripts need to be run after an LCFG based install to create the database schema. One can either recreate entirely the database, which will remove all the entries, or upgrade the schema only, which will maintain all existing entries.

Discrepancies with documentation:

• User guide incorrectly describes the file format for SURLs. The description of PFN,SFN,SURL is unclear in general.

Replica Location Index (RLI)

Description: One of the two components of the Replica Location Service.
It is an index that maintains LRC to GUID mappings for all LRCs in a VO that are configured to publish information to it.

Deployment scenario: Many per VO. Deployment according to the needs of a VO State:

State: Not deployed in EDG 2.0. Will be integrated into EDG 2.1.

Known Bugs: None known (Since the service is not deployed yet)

Manual Configuration: None

Discrepancies with documentation: None known (doesn't mean their aren't any)

Replica Metadata Catalog (RMC)

Description: A catalog that stores LFN (alias) to GUID mapings along with metadata on the GUID for all files in a given VO.

Deployment scenario:One per virtual organization.

State: Deployed; working.

Known Bugs:

• Returned error codes need to be improved. Bug # 907.
• GUID attributes cannot be created unless a LFN is created, i.e a fake alias. Bug # 965.
• No versioning of SQL schemas. Bug # 1359.
• No deleteMapping method. removeAlias is not alligned with the functionality of deleteMapping in the LRC API. Will be fixed in release 2.1. Bug # 1590
• View all open RMC bugs

Manual Configuration:

• MySQL scripts need to be run after an LCFG based install to create the database schema. One can either recreate entirely the database, which will remove all the entries, or upgrade the schema only, which will maintain all existing entries.

Discrepancies with documentation:

• User guide incorrectly describes the file format for SURLs. The description of PFN,SFN,SURL is unclear in general.

Replica Manager

Description: Client tool that integrates all the grid data management components and provides a single entry point to all other grid services and users.

Deployment scenario: Installation on any UI or WN.

State: Deployed, working. The RM client tool can work with R-GMA, MDS and static configuration files to obtain information about grid services.

Known Bugs:

• Error messages need imporvement. Bug # 1413
• Double copies when using copyAndRegisterFile. Bug # 1417,1756
• copyAndRegister leaves file if registration stage fails. Bug # 1676.
• Insecure flag is ignored. Bug #1680
• edg-rm does not give access to metadata. Bug # 1685
• No wildcard operations with edg-rm. Bug # 1687
• Replica manager does not use info in ServiceStatus table to determine if a service is up. Bug # 1690
• Error codes need improvement. Bug # 1719
• Performance is very poor, order of magnitude worse than we should be.Bug #1805
• Core-dumps for url-copy with URIs where no GridFTP server is running. Bug # 1833
• RM has errors working with ROS. Bug #1838,1769
• Errors catching SE exceptions. Bug # 1865.
• View all open RM bugs

Manual Configuration: None

Discrepancies with documentation:

• deleteFile is incorrectly documented, it does not delete entries from the RMC.
  Bug #1077

Replica Optimization Service

Description: A service that optimizes access to data in the grid.

Deployment scenario: As many as needed, stateless service.

State: Deployed on EDG MON nodes, working.
Only the EDG network cost function is currently taken into account in the optimization algorithm.
In principle the SE costs algorithm should be integrated as well. The information returned by the SE cost function at the moment is not a useful metric.

Known Bugs:

• getBestFile only considers 1 close SE, case of > 1 close SE is ignored. Bug # 1841
• Application server logging is hardwired. Bug # 933

Manual Configuration: None

Discrepancies with documentation: None known (doesn't mean their aren't any)