1. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I WP2 - Data Management L.M.Barone Università di Roma & INFN

2. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I WP Goals...to permit the secure access of massive amounts of data...to move and replicate data at high speed from one site to another and to manage the synchronisation of remote data copies (dal Technical Annex di DataGrid)

3. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Keywords Automation Caching Generic Interface MetaData Data Mover Replica Manager Security

4. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I People SEDENOMEFTE Bari: L.Silvestris0.3 G.Zito0.5 (0.3) Pisa:S.Arezzini0.3 (0.3) A.Controzzi0.5 F.Donno0.2 (0.2) F.Schifano0.2 Roma1:L.M.Barone0.3 (0.3) A.Lonardo0.3 A.Michelotti0.3 G.Organtini0.2 D.Rossetti0.2 (0.2)

5. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Deliverables Requirements for Data Location Broker 5/2001 Definition of a metadata syntax7/2001 Replica Management at file level12/2001

6. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I An Example Ideas for a Replica Manager: –Management of production in a distributed environment: Data produced in many sites Data collected in a single reference site Data analyzed in many sites Data sometimes are moved, sometimes may be accessed via network A case study with Objectivity/DB –can be extended to any kind of file

7. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I CERN CERNFD DB1 DB2 DB3 DBn CERN Boot RC1FD RC1 Boot RC2FD RC2 Boot Cloning federations Clone FD DB_a DB_b

8. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Productions CERN CERNFD DB1 DB2 DB3 DBn CERN Boot RC1FD RC1 Boot RC2FD RC2 Boot DBn+1 DBn+m DBn+m+1 DBn+m+k GDMP

9. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Analysis CERN CERNFD DB1 DB2 DB3 DBn CERN Boot RC1FD RC1 Boot RC2FD RC2 Boot DBn+1 DBn+m DBn+m+1 DBn+m+k DBn+m+k DBn+m+1 DBn+m DBn+1

10. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Logical vs Physical Datasets Dataset: H 2 Dataset: H 2e Hmm.1.hits.DB Hmm.2.hits.DB Hmm.3.hits.DB Hee.1.hits.DB id=12345 id=12346 id=12347 id=5678 Hee.2.hits.DB id=5679 Hee.3.hits.DB id=5680 pccms1.bo.infn.it::/data1/Hmm1.hits.DB shift23.cern.ch::/db45/Hmm1.hits.DB pccms1.bo.infn.it::/data1/Hmm2.hits.DB shift23.cern.ch::/db45/Hmm2.hits.DB shift23.cern.ch::/db45/Hmm3.hits.DB pccms5.roma1.infn.it::/data/Hee1.hits.DB shift49.cern.ch::/db123/Hee1.hits.DB pccms5.roma1.infn.it::/data/Hee2.hits.DB shift49.cern.ch::/db123/Hee2.hits.DB shift49.cern.ch::/db123/Hee3.hits.DB pccms5.roma1.infn.it::/data/Hee3.hits.DB pccms3.pd.infn.it::/data3/Hmm2.hits.DB

11. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Logical vs Physical Datasets Each dataset is composed by one or more databases –datasets are managed by application-sw Each DB is univocally identified by a DBid –DBid assignment is a logical-db creation The physical-db is the file –zero, one or more instancies The GIS manages the link between a dataset, its logical-dbs and its physical- dbs

12. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I RC1Prod DB4 DB4 RC1Ref pc.rc1.net CERN CERNFD DB1 DB2 DB3 DB4 0001 DB1.DB shift.cern.ch::/shift/data 0002 DB2.DB shift.cern.ch::/shift/data 0003 DB3.DB shift.cern.ch::/shift/data 0004 DB4.DB pc.rc1.net::/pc/data shift.cern.ch::/shift/data 0005 Database creation DB5 DB5 DB5 DB5 0001 DB1.DB shift.cern.ch::/shift/data 0002 DB2.DB shift.cern.ch::/shift/data 0003 DB3.DB shift.cern.ch::/shift/data 0004 DB4.DB pc.rc1.net::/pc/data shift.cern.ch::/shift/data 0005 DB5.DB pc.rc1.net::/pc.data 0001 DB1.DB shift.cern.ch::/shift/data 0002 DB2.DB shift.cern.ch::/shift/data 0003 DB3.DB shift.cern.ch::/shift/data 0004 DB4.DB pc.rc1.net::/pc/data shift.cern.ch::/shift/data 0005 DB5.db pc.rc1.net::/ps.data shift.cern.ch::/shift/data shift.cern.ch

13. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I 0001 DB1.DB shift.cern.ch::/shift/data pc1.bo.infn.it::/data 0002 DB2.DB shift.cern.ch::/shift/data 0003 DB3.DB shift.cern.ch::/shift/data 0001 DB1.DB shift.cern.ch::/shift/data pc1.bo.infn.it::/data 0002 DB2.DB shift.cern.ch::/shift/data pc1.bo.infn.it::/data 0003 DB3.DB shift.cern.ch::/shift/data Replica Management CERN CERNFD DB1 DB2 DB3 BORef shift.cern.ch pc1.bo.infn.it PDRef pc1.pd.infn.it DB1 DB2

14. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Example Summary Basic functionalities of a Replica Manager for production will be tested by end of 2000 on CMS production (GDMP) Next comes an Information Server to allow easy synchronization of federations and optimized data access during analysis The same functionalities shown for Objectivity/DB may/should be implemented for other kind of files

15. L.M.Barone – INFN Rome 13 Settembre 2000 Commissione Nazionale I Conclusions Data Management Tools are needed to face the complexity of new generation experiments (not only LHC) The GRID projects (INFN and EU) are already providing solutions to real life problems Milestones and objectives are well defined (to meet them will not be trivial)