OGSA-DAI TWO (DAIT)
Project Proposal
Prof. Malcolm Atkinson
Director
www.nesc.ac.uk
28th April 2003
1
OGSA-DAI Partners
IBM
USA
EPCC & NeSC
Glasgow
Newcastle
Belfast
Daresbury Lab
EPCC & NeSC
IBM UK
IBM USA
Manchester e-SC
Newcastle e-SC
Oracle
Manchester
Oxford
Oracle
Cambridge
Hinxton
RAL
Cardiff
London
IBM Hursley
Southampton
18 months, started February 2002
2
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
Diagnosis
Authorisation
Scheduling
Accounting
Transformation
Transport
Naming
Caching
Structured Data
Integration
Structured Data Access
Grid Infrastructure
Compute, Data & Storage Resources
Structured Data
Relational
Distributed
Virtual Integration Architecture
DAI
OGSA
OGSI
Monitoring
XML Semi-struct.
3
23
-A
-A
-A
pr
pr
pr
pr
ar
ar
ar
350
16
09
b
b
b
b
ar
-A
-M
-M
02
26
19
-M
-M
-F
e
-F
e
-F
e
-F
e
-J
an
-J
an
-J
an
250
12
05
26
19
12
05
29
22
15
OGSA-DAI Downloads vs Time
Release 2
300
Release 1.5
200
150
Release 1
100
50
0
DAI basic Services
1a. Request to
Registry for sources
of data about “x”
SOAP/HTTP
Registry
1b. Registry
responds with
Factory handle
service creation
API interactions
2a. Request to Factory for
access to database
Factory
Client
2c. Factory returns
handle of GDS to
client
3a. Client queries GDS
with XPath, SQL, etc
3c. Results of query returned to
client as XML
2b. Factory creates
GridDataService to manage
access
Grid Data
Service
XML /
Relational
database
3b. GDS interacts with database
5
1a. Request to Registry
for Factories with
required capability
DAI Composed Services
SOAP/HTTP
Registry
1b. Registry
responds with
Factory handle
service creation
API interactions
2a. Requests to each Factory
for a GridDataService
Factory
Factory
Factory
3b. Client
tells
analyst
Analyst
Client
2c. Factories return
handles of GDSs to
client
3a. Client queries GDS
with XPath, SQL, etc
2b. Factory creates
GridDataService to
manage access
3c. Results of query
returned to client as XML
3b. GDSs interact
with databases
Relational
database
Grid Data
Service
Grid Data
Service
Grid Data
Translation
Service
Both XML or
Both Relational
Relational
database
6
DAIT basic Services
1a. Request to Registry for
sources of data about “x” &
“y”
1b. Registry
responds with
Factory handle
Data
Registry
SOAP/HTTP
service creation
API interactions
2a. Request to Factory for access and
integration from resources Sx and Sy
Factory
2c. Factory
returns handle of GDS to client
3b. Client
tells
analyst
Client
2b. Factory creates
GridDataServices network
3a. Client submits sequence of
scripts each has a set of queries
to GDS with XPath, SQL, etc
GDTS1
Analyst
GDS
GDTS
GDS2
3c. Sequences of result sets returned to
analyst as formatted binary described in
a standard XML notation
Sx
GDS
GDS1
XML
database
Sy
GDS3
GDS
GDTS2
Relational
database
GDTS
7
www.ogsadai.org.uk
www.nesc.ac.uk
8