Скачать презентацию Steering and Interactive Visualization on the Grid Using Скачать презентацию Steering and Interactive Visualization on the Grid Using

691209b5efb6e425990e833903ded965.ppt

  • Количество слайдов: 19

Steering and Interactive Visualization on the Grid Using the UNICORE Grid Middleware K. Benedyczak Steering and Interactive Visualization on the Grid Using the UNICORE Grid Middleware K. Benedyczak 1, 2, A. Nowiński 1, K. S. Nowiński 1, P. Bała 1, 2 (1) (2) ICM, Warsaw University, Poland Faculty of Mathematics and Computer Science, N. Copernicus University, Torun, Poland

Unicore middleware o o o o Well known Very stable Message based protocol No Unicore middleware o o o o Well known Very stable Message based protocol No streaming at all Very good security model Intensive SSL usage Good firewall passing

Unicore architecture Single entry point Client SSL Firewall Gateway NJS UUDB TSI USpace Unicore architecture Single entry point Client SSL Firewall Gateway NJS UUDB TSI USpace

Vis. It – a visualization toolkit o o o o Well known protocol for Vis. It – a visualization toolkit o o o o Well known protocol for remote visualization and steering Easy to use Reversed connection direction – simulation connects to visualization Service registry and specific protocol – SEAP Very well developed binary data conversion procedures No java binding May use multiple connections for single session

Vis. It - architecture Visualization (Visit server) Data (may use Multiple connections) SEAP server Vis. It - architecture Visualization (Visit server) Data (may use Multiple connections) SEAP server Simulation (Visit client) Example session: o Simulation starts o Simulation queries SEAP poeriodically o Visualization starts and registers on SEAP server o Simulation gets visualization address from the SEAP o Simulation connects to the Visualization o Data is exchanged

IVis o o o Streaming extension for Unicore developed in ICM Uses Unicore gateway IVis o o o Streaming extension for Unicore developed in ICM Uses Unicore gateway extension feature Developed as system for access to groving files Easily extendable Very good performance Authorization done separately

IVis architecture Still single entry point Client Firewall Gateway IVis Extension NJS UUDB TSI IVis architecture Still single entry point Client Firewall Gateway IVis Extension NJS UUDB TSI USpace IVis server

UVisit o o o Support for running Vis. It over Unicore infrastructure Does not UVisit o o o Support for running Vis. It over Unicore infrastructure Does not require changes in simulation and visualization Implements most important parts of the protocol Require SEAP usage by both simulation & visualization Implementation using IVis server and Unicore client extension plugins.

UVisit - schema Visit Server (Visualization) SEAP UVisit plugin Data Gateway Unicore Client Firewall UVisit - schema Visit Server (Visualization) SEAP UVisit plugin Data Gateway Unicore Client Firewall IVis Extension IVis server NJS TSI Run job SEAP UVisit module Visit client (simulation) Data

UVisit – seap split o Seap server has to be split: n n o UVisit – seap split o Seap server has to be split: n n o o o Client part included into UVisit plugin Server part in the UVisit. Server, module of IVis server Seap data has to be modified (destination address) Endpoint created on the request Data on the server valid only as long as the client is connected

UVisit implementacja - tunnel o o Single secure (SSL) connection to the gateway used UVisit implementacja - tunnel o o Single secure (SSL) connection to the gateway used to transfer SEAP and data Very simple message-based protocol used to separate streams on the endpoints (client&server) Small overhead Multiple visualization streams can be run through the single tunnel

UVisit – plugin o o o Runs at UVisit ‘server’ (visualization) endpoint Implemented as UVisit – plugin o o o Runs at UVisit ‘server’ (visualization) endpoint Implemented as the Unicore extension plugin Can connect to multiple sites at once User can see registered SEAP entries Only. visitrc setup required

UVisit - setup o o o Working IVis installation required (gateway and server) On UVisit - setup o o o Working IVis installation required (gateway and server) On the user endpoint valid. visitrc pointing to the client host is required On the server config file must be edited to define server location On the job server valid. visitrc pointing to the server required That’s all…

UVisit limitations: o o o Requires forcing of single connection for control and data UVisit limitations: o o o Requires forcing of single connection for control and data Requires SEAP usage Problems with multiple users on the same server – Visit security is limited

UVisit demo application o o UVisit lacks nice graphic demo Application created for UVisit, UVisit demo application o o UVisit lacks nice graphic demo Application created for UVisit, but works with plain visit as well Simulation of diffusion and advection in the complex velocity field defined by randomly moving vortices Simple steering included

UVisit demo application o o o Visualization in java stand-alone application Minimal proxy in UVisit demo application o o o Visualization in java stand-alone application Minimal proxy in C required (no java binding for Visit!) Available in UVisit package

Conclusions o o UVisit is a successful implementation of streaming in unicore Does not Conclusions o o UVisit is a successful implementation of streaming in unicore Does not require changes in the legacy code (or minor changes only) Good performance No changes required in unicore

Future development o o Currently we are working on mechanism similar to the IVis/UVisit Future development o o Currently we are working on mechanism similar to the IVis/UVisit for unigrids environment - UGSF We develop Web-Service integrated streaming in the new infrastructure

Thank you! Thank you!