80 likes | 208 Views
OGSA-DAI TWO (DAIT) Project Proposal Prof. Malcolm Atkinson Director www.nesc.ac.uk 28 th April 2003. OGSA-DAI Partners. IBM USA. EPCC & NeSC. Glasgow. Newcastle. Belfast. Manchester. Daresbury Lab. Cambridge. Oxford. EPCC & NeSC IBM UK IBM USA Manchester e-SC
E N D
OGSA-DAI TWO (DAIT) Project Proposal Prof. Malcolm Atkinson Director www.nesc.ac.uk 28th April 2003
OGSA-DAI Partners IBM USA EPCC& NeSC Glasgow Newcastle Belfast Manchester Daresbury Lab Cambridge Oxford EPCC & NeSCIBM UK IBM USA Manchester e-SC Newcastle e-SCOracle Oracle Hinxton RAL Cardiff London IBM Hursley Southampton 18 months, started February 2002
Infrastructure Architecture Data Intensive X Scientists Data Intensive Applications for Science X Simulation, Analysis & Integration Technology for Science X Generic Virtual Data Access and Integration Layer Monitoring Diagnosis Authorisation Structured Data Integratio n OGSA Accounting Transformation Scheduling Structured Data Access Caching DAI Transport Naming OGSI Grid Infrastructure Compute, Data & Storage Resources Structured Data Relati onal XML Semi - struct. Distributed Virtual Integration Architecture
Release 2 Release 1.5 Release 1
1a. Request to Registry for sources of data about “x” SOAP/HTTP service creation API interactions Registry 1b. Registry responds with Factory handle 2a. Request to Factory for access to database Factory Client 2c. Factory returns handle of GDS to client 2b. Factory creates GridDataService to manage access 3a. Client queries GDS with XPath, SQL, etc XML / Relational database Grid Data Service 3c. Results of query returned to client as XML 3b. GDS interacts with database DAI basic Services
1a. Request to Registry for Factories with required capability DAI Composed Services SOAP/HTTP service creation API interactions Registry Factory Factory Factory Client Relational database Relational database Grid Data Service Grid Data Service Grid Data Translation Service 1b. Registry responds with Factory handle 2a. Requests to each Factory for a GridDataService 3b. Client 2c. Factories return handles of GDSs to client tells 2b. Factory creates GridDataService to manage access analyst 3a. Client queries GDS with XPath, SQL, etc Analyst 3c. Results of query returned to client as XML Both XML or Both Relational 3b. GDSs interact with databases
SOAP/HTTP service creation API interactions DAIT basic Services 1a. Request to Registry for sources of data about “x” & Data “y” Registry 1b. Registry responds with Factory handle 2a. Request to Factory for access and integration from resources Sx and Sy Factory 2c. Factory returns handle of GDS to client 3b. Client 2b. Factory creates tells GridDataServices network analyst Client 3a. Client submits sequence of scripts each has a set of queries GDTS to GDS with XPath, SQL, etc 1 XML Analyst GDS GDTS database GDS 2 S x GDS S 3c. Sequences of result sets returned to y Relational analyst as formatted binary described in GDTS GDS GDS 2 3 a standard XML notation 1 database GDS GDTS
Comments & Questions Please www.ogsadai.org.uk www.nesc.ac.uk