1. 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)ICM, Warsaw University, Poland (2)Faculty of Mathematics and Computer Science, N. Copernicus University, Torun, Poland

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

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

4. VisIt – a visualization toolkit  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

5. VisIt - architecture Example session:  Simulation starts  Simulation queries SEAP poeriodically  Visualization starts and registers on SEAP server  Simulation gets visualization address from the SEAP  Simulation connects to the Visualization  Data is exchanged Simulation (Visit client) Visualization (Visit server) SEAP server Data (may useMultiple connections)

6. IVis  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

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

8. UVisit  Support for running VisIt 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.

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

10. UVisit – seap split  Seap server has to be split: Client part included into UVisit plugin Server part in the UVisitServer, 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

11. UVisit implementacja - tunnel  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

12. UVisit – plugin  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

13. UVisit - setup  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…

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

15. UVisit demo application  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

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

17. Conclusions  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

18. Future development  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

19. Thank you!