1. INFSO-RI-508833 Enabling Grids for E-sciencE www.eu-egee.org gLite Data Management and Interoperability Peter Kunszt (JRA1 DM Cluster) 2 nd EGEE Conference, 24 th November 2004

2. Enabling Grids for E-sciencE INFSO-RI-508833 2 nd EGEE Conference The Hague 2 Aim Medium term goals (Sophie): –To allow current users of LCG-2 to run their current software on gLite –Allow them to compare the performance of LCG-2 and gLite Medium term goals (gLite) –Be ‘better’ than LCG-2

3. Enabling Grids for E-sciencE INFSO-RI-508833 2 nd EGEE Conference The Hague 3 Catalogs Current deployed solution : –AliEn File Catalog Development : –gLite File and Replica Catalog interfaces –Combined Catalog interface (Fireman)  Deployed on prototype: Oracle implementation of Fireman  Deployed on DM testbed: MySQL implementation of Fireman  Working with LCG on Fireman interface on LFC –3 implementations!! Deployment possibilities: –Local Fireman instances at major sites –Storage Index nodes for WMS resolver –AliEn File Catalog as Central Instance –Messaging mechanism between local catalogs and SI/AFC  Being deployed/tested on DM testbed

4. Enabling Grids for E-sciencE INFSO-RI-508833 2 nd EGEE Conference The Hague 4 Some Answers How can a user –find data in either the LCG-2 catalogs or the gLite catalogs using both the LCG-2 and gLite tools?  Explicit mechanism – use both tools  Or gLite client if LCG-2 catalog exposes a Fireman interface –access data produced already and stored in LCG-2 SE using gLite tools?  Easy if LCG catalogs have a Fireman interface  Migration is also possible – need to clarify exact semantics How is data –on LCG-2 Classic SEs available to gLite clients?  Set up a glite IO server  Migrate data –on gLite SEs available to LCG-2 clients ? –on gLite SEs available to local clients, not using the gLite I/O mechanism?  Update LCG-2 clients  Without change to LCG-2 clients: Only on SRMs having ACL capability.

5. Enabling Grids for E-sciencE INFSO-RI-508833 2 nd EGEE Conference The Hague 5 Some Answers How can the WMS –matchmaking against both gLite and LCG-2 catalogs, if the appropriate SEs are available?  LCG catalogs may be also connected into the StorageIndex  Use the StorageIndex interface –Find available catalogs for LCG-2 and gLite data?  Again easy if LCG catalogs have a Fireman interface and are hooked up through the StorageIndex.  If not, this is a service discovery issue.

6. Enabling Grids for E-sciencE INFSO-RI-508833 2 nd EGEE Conference The Hague 6 Data Currently : –“Classic SE” LCG DPM (Disk Pool Manager) –Provides SRM interface dCache will be used at Tier-1s and sites with MSS Advantage : –Data accessible for gLite –‘Metadata-only’ migration : no need to move/copy files to go to gLite

7. Enabling Grids for E-sciencE INFSO-RI-508833 2 nd EGEE Conference The Hague 7 Security Catalogs store ACLs –DN –VOMS Role –Owner / Group ‘gproduct’ user owns the data in the SRM Only FPS and IO-Server have access to the local data Direct access to SRM possible if SRM has ACL functionality –Add more ACLs – other than gproduct Implementation status today –ACL enforcement tested in Oracle – untested in MySQL –Catalogs are secured themselves –Test VOMS certificates work – need to test with real certificates now

8. Enabling Grids for E-sciencE INFSO-RI-508833 2 nd EGEE Conference The Hague 8 Client Access glite – IO –Posix and a more rich (thread safe) API –Basic put and get command liners through glite-IO Transfer-CLI –Replication and locality requests On the UI: shell having access to glite data –Starting bash, tcsh, etc. using parrot (from Condor) – integrating glite-IO seamlessly into the shell  Navigate glite (ls)  Standard unix commands just work: mkdir, cp, rm, cat, less, tail etc.  Complex applications (acroread) have been seen to work but are not expected to be used. Planned command liners for ACL control