1 / 12

The Replica Management Services: Reptor

The Replica Management Services: Reptor. Replica Management Services Framework. Replica Manager component glossary. ERM: EDG Replica Manager client interface and API Entry point for all clients ROS: Replication Optimization Service Replica selection based on network metrics (WP7)

bsally
Download Presentation

The Replica Management Services: Reptor

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Replica Management Services: Reptor

  2. Replica Management Services Framework

  3. Replica Manager component glossary ERM: EDG Replica Manager client interface and API • Entry point for all clients ROS: Replication Optimization Service • Replica selection based on network metrics (WP7) RSH: Replication Storage Handler • Subscription-based replication RLS: Replica Location Service • Local Replica Catalog services LRC: Logical to Physical file mappings • Replica Location Index services RLI: index on Logical names RMC:Replication Metadata Catalog • An instance of Spitfire with RDBMS backend and specialized schema

  4. VOMS ERM ROS RGMA RMC RSH RLS Replica Management Services for TB2 VO Membership Service Replica Management Services Replica Manager Client Optimization Information Service Replica Metadata File Transfer: GridFTP Subscription Replica Location Service

  5. Implementation ERM: client-side replica manager. Contains all coordination logic. ROS: very lightweight web service (no DB backend) – calls upon WP7 monitors RSH, RLS, RMC: heavyweight web service (with DB backend)

  6. Why not a Manager Service? • Delegation. Current implementation has most logic at the client side ERM. Would like to move to a model where the logic is performed by an RMS service VO Membership Service Replica Manager Service Replica Management Services Replica Manager Client Optimization Information Service Replica Metadata File Transfer: GridFTP Subscription Replica Location Service

  7. ERM implementation • edg-reptor module provides the ERM. • Layout: src/org/edg/data/ • reptor/ • reptor/storage • reptor/catalog • reptor/optimization • reptor/naming • reptor/info • reptor/client

  8. Usage of Factory Pattern • Generic interfaces to functional blocks • If there are several implementations, a factory is provided info/InfoService.java implements info/RGMAInfoService.java info/InfoServiceStub.java info/InfoServiceFactory.java InfoService info = InfoServiceFactory.create(className);

  9. Interfaces • storage/FileHandle • storage/StorageElement • storage/GridFTP * • storage/GlobusURLCopy * • info/InfoService * • naming/NameGenerator * • catalog/ReplicaCatalog * • client/Command • /ReplicaManager • /Configuration * * : With corresponding Factory

  10. Tests • In general, each module must have unit tests for their classes. • Unit tests are collected in • org/edg/data/module/AllTests.java • Functionality tests currently collected in • org/edg/data/module/AllFuncTests.java • Integration tests – ad hoc.. All ERM functionality tests are sort of integration tests. Needs proper integration testing • Validation tests – still missing

  11. Documentation • Javadoc • Help from code • Manpages • User Guide • Installation Guide

  12. Extensions • Immediate: • Collections • Sessions • Mid-term • Pre- Post- Processing • As soon as delegation is solved • Request management (‘transactions’)

More Related