OGSA-DAI
Render Demo
NeSC Review
18 March 2004
Description and Aims
The OGSA-DAI Render demo is intended
to demonstrate both the Process and Data
aspects of a Grid
Flight path data is stored in a relational
database (MySQL)
Models are stored in flat files
With thanks to Andrew Borley, Jonathan
Davies, Neil Hardman and George Hicken
of IBM UK.
Initial set-up
Render Node
Render Node
Render Node
Registration
Render Node
Registry
Registration
Registration
Flightpath
Factory
Models
Factory
Flightpaths
Models
Next
Data Flow
Render Node
Render Node
Render Node
Render Node
User
selects
Demo
Flightpath
Web
Model
page
Registry
Query Registry
Service
Handles for
Render from
Nodes,
returned
the
Flightpaths
and
Registry
Models
Create the
Flightpath GDS
Web Client
Flightpaths
All
available are
returned
flightpaths
are
queried
Flightpath
Factory
Create the
Models GDS
All available
All available Models
models are
are returned
queried
Models
Factory
Grid Data
Service Creation
Grid Data
Service Creation
GDS
Flightpaths
GDS
Models
Next
Data Flow
Render Node
Render Node
Render Node
Render Node
Registry
Perform Documents
sent to Render Nodes
Render Nodes query
GDS for the Flightpath
Flightpath
Factory
Render Nodes query
GDS for the Model
Web Client
Models
Factory
GDS
Flightpaths
GDS
Models
Next
Data Flow
Render Nodes
process the images
Render Node
Render Node
Render Node
Render Node
Registry
Rendered images returned
to the Web Client
Web Client
Animator
Flightpath
Factory
The Animator Process
composes the movie from
the rendered images
Models
Factory
GDS
Flightpaths
GDS
Models
Next
Conclusions
OGSA-DAI can be used for both
Data access
Process driven environment
Extensible
POV Ray process initiated by an OGSA-DAI
Activity
Facilitates the integration of different data
sources
Databases
Files
Choosing a model + flightpath
Editing flightpath
Load flightpath data
from database
Edit camera path and
points
Save data back to
flightpath database
Models loaded from
flat files
Rendering scenes
Dispatch scenes to
rendernodes
Progress notification
allows tracking of
each scene’s status
RenderNode
Each RenderNode gets
a scene
Custom written OGSADAI activity to start
POVRAY using data
from flightpath and
models databases
After rendering scene,
RenderNode sends
back data
Assemble movie
Each individual
rendered scene is
assembled into a
movie by the web
client