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 Flightpaths Registry Flightpath Factory Models Registration Render Node Registration Models Factory Registration Next

Data Flow Registry Flightpath Factory Render Node Models Factory Web Client Query Registry for Render Nodes, Flightpaths and Models Service Handles returned from the Registry All available flightpaths are queried All available models are queried Flightpaths are returned All available Models are returned User selects Demo Web page User selects Model GDS Grid Data Service Creation User selects Flightpath GDS Grid Data Service Creation Models Flightpaths Create the Models GDS Create the Flightpath GDS Next

Data Flow Registry Flightpath Factory Render Node Models Factory Web Client GDS Models Flightpaths Perform Documents sent to Render Nodes Render Nodes query GDS for the Flightpath Render Nodes query GDS for the Model Next

Animator Data Flow Registry Flightpath Factory Render Node Models Factory Web Client GDS Models Flightpaths Rendered images returned to the Web Client Next Render Nodes process the images The Animator Process composes the movie from the rendered images

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 scenes status

RenderNode Each RenderNode gets a scene Custom written OGSA- DAI 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