90 likes | 188 Views
DataTAG-WP4 EU-US GRID Interoperability. Cristina Vistoli INFN-Cnaf. DataTAG-WP4. GOAL:
E N D
DataTAG-WP4EU-US GRID Interoperability Cristina Vistoli INFN-Cnaf
DataTAG-WP4 GOAL: Setup an “experimental transatlantic grid ” based on European and US interoperable GRID Middleware, to provide transparent access to distributed computing infrastrastructure needed by data intensive application.
Framework EU Part US Part DataTAG-WP4 iVDGL HICB GLUE DataGRID Griphyn/PPDG HEP experiments and LCG
iVDGL and GLUE programme • iVDGL (middleware VDT) • The iVDGL is a global Data Grid that will serve experiments Its computing, storage and networking resources provide laboratory that will test and validate Grid technologies at international and global scales. • The Grid Laboratory Uniform Environment (GLUE) initiative was created in Feb. 2002 to provide a focused effort to achieve interoperability between the core GRID services: • Authorisation • Information System • Data movement
Interoperability approach(Deliverable 4.1) • The common grid scenario brought the EU and US middleware projects to define very similar requirements for their plans. • One result of this scenario is the adoption of common software for the basic services like Globus e Condor • http://grid.infn.it/datatag/wp4/doc/D4.1.pdf • This situation made easier the approach adopted to study interoperability: • Definition and standardisation of a minimum set of core services that must be adopted by all the Grid • Integration or coexistance solutions for the high level services
Interoperability approach • Basic requirements to guaranteeinteroperability accessing GRID resources: • common protocols • common authentication and authorisation mechanism • common schema describing GRID resources • Common protocols are: • GRAM • GSI
DataTAG: Resource discovery • GLUE: • Definition of a common Schema to descrie GRID resources in the Information Systen • Computing Element: agreed/implemented • Storage Element: agreed/implemened • Glue Schema included in standard MDS2.2 release • Collaboration with EDG to implement Information Provider to fill the agreed schema • EDG Information Providers included in VDT 1.1.3 • Transatlantic testbed • Resource Broker “Glue-aware”
Practical Experimentation • What we learned? • Interoperability solution based on common grid services is feasible. • EDG in the European grid, VDT in the US grid • Testing phase still to be completed why? • New JDL parameters • New schema attributes: are they good enough to represent the Grid Nodes and give correct monitoring information? • Performance: different set of query to find the proper nodes: is this too bad for performance? • Is a relational information system for monitoring information really needed? • In this case we will have common information schemas but not common information system, is this feasible, what are the impacts in interoperability? • RGMA-GLUE in EDG Middleware and MDS-GLUE in VDT • EDG v2.0 will have GLUE support, but with R-GMA, how this will impact interoperability with VDT based on MDS? • Test of CE Information Provider not yet completed for the whole set of fields • Test of SE Information Provider : very early deployment.
Practical Experimentation: Next Steps • Test-bed activity • RB-Glue Aware 1.4 .2 (the same identical version used for Stress Tests) • Glue Test-bed Upgrade to EDG 1.4.2 (Cnaf, Padova,Milan) • Glue Info Provider installed in INFN-GRID nodes. • Operational activity: • Verify to correctly address and control and recover input/output from US nodes with pure VDT 1.1.3 software or later and EU nodes • VDT 1.1.3 should contains Glue schema and EDG CE Info providers, Ruth agreement • Submit real application jobs to experiment new JDL parameters • Verify the performance of the new information system queries • Prepare the set up for the project review in 19/3/2002 • Next steps: support/collaborate with R-GMA, this should be transparent for the Resource Broker but no information about performances and information system Relational/Jeararchical coexistance.