1. UlabGrid Framework for Computationally Intensive Remote and Collaborative Learning Laboratories O. Ardaiz, L. Díaz de Cerio, R. Meseguer, A. Gallardo, K. Sanjeevan Computer Architecture Department Politecnic University Catalunya, Spain

2. Outline Out botton-up approach. Taking advantage of grid. Ulab framework. Experimentation. Future Work.

3. Our Botton-up approach Objetive: “develope new collaborative learning applications of grid technology” First step: deploy Grid testbed.  Linux resources, GTK2.4, GT3.0, mini-CA. Second step: evaluate grid technology capabilities.  Test demo application, develop small scientific application. Third step: Look for collaborative learning applications that can benefit for grid.  In our teaching (programming, computer networking), in nearby schools (aeronautics engineering school). Fourth step: Implement and evaluate.

4. Taking advantage of Grids ¿New educational applications, methods,…? ¿Students learning to use scientist new grid tools, or learning while using them?  Grid.edu Workshop. Equal benefits as scientists:  Resource sharing for “cost” sharing: Reducing education costs is good.  Computationally intensive applications: Computer network simulator, (but to learn networking, only small simulations are required) 3D flight simulator, graphical 3D simulations consume 100% CPU ---->Lets try it!!!!

5. Ulab Framework We are not interested in a particular application, but to provide support for multiple collaborative application ->  Design a framework, “generic libraries to develop applications”. Requirements:  Built on “de facto” grid standards: -> Use GTK2.4.  Use some existing application code: -> Gridification of applications.  “thin” clients for remote visualization and interaction: -> Use VNCviewer.  Support for collaborative learning groups: ->Implement session manager.

6. GSIFTPServer Globus-Gatekeeper Pentium IV pcmartino.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc3.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc5.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc4.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc6.ac.upc.es ULab Grid VNC Protocol Grid-Proxy GassServer GlobusPortal User Directory File Server Pcribes.ac..upc.es ReplicaMgr MetadataDirector yServer Session Manager Grid Manager GSIFTPServer avant.upc.es GSIFTP Protocol GRAM Protocol Session Control Protocol Ulab Framework (I): VNC for app access Student 1 VNC client Session client App1 App2 App3 Student 2 VNC client Session client App1 App2 App3 %VNC-server:1 %FS &

7. GSIFTPServer Globus-Gatekeeper Pentium IV pcmartino.ac.upc.es %Vnc-server:1 %FS & GSIFTPServer Globus-Gatekeeper Pentium IV pc3.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc5.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc4.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc6.ac.upc.es ULab Grid VNC Protocol (Session 1) Grid-Proxy GassServer GlobusPortal User Directory File Server Pcribes.ac..upc.es ReplicaMgr MetadataDirector yServer Session Manager Grid Manager GSIFTPServer avant.upc.es GSIFTP Protocol GRAM Protocol Session Control Protocol Ulab Framework(II): Multiple application access Student 1 VNC client Session client App1 App2 App3 Student 2 VNC client Session client App1 App2 App3 %VNC-server:1 %FS & VNC Protocol (Session 2) %VNC-server:1 %Net-Sim-2 &

8. GSIFTPServer Globus-Gatekeeper Pentium IV pcmartino.ac.upc.es %Vnc-server:1 %FS & GSIFTPServer Globus-Gatekeeper Pentium IV pc3.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc5.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc4.ac.upc.es GSIFTPServer Globus-Gatekeeper Pentium IV pc6.ac.upc.es ULab Grid VNC Protocol (Session 1) Grid-Proxy GassServer GlobusPortal User Directory File Server Pcribes.ac..upc.es ReplicaMgr MetadataDirector yServer Session Manager Grid Manager GSIFTPServer avant.upc.es GSIFTP Protocol GRAM Protocol Session Control Protocol Ulab Framework (III): Visual Session Sharing Student 1 VNC client Session client App1 App2 App3 Student 2 VNC client Session client App1 App2 App3 %VNC-server:1 %FS & VNC Protocol (Session 2) %VNC-server:1 %Net-Sim-2 & Student 1 Co-pilot Observe

9. Implementation Session manager:  Several applications available to each student,  Students can share applications,  Several students on same session, Resource manager:  All grid resources available to each student,  Controls resource status and implements resource scheduling,  Control resources used by each student, “Comunication between Rsc Mgr and Session Mgr permits to share sessions”.

11. Experiment Results (I) Globus Toolkit:  GTK2.4 is OK,  GTK3.0 takes upto 20 seconds to launch processes. Gridification Flight Simulator :  only required an scriptable configuration file.  Special VNC server for OpenGL application: xf4vnc. Resource usage:  High network traffic: peaks of 12 Mbits, average of 1Mbit.  CPU consumption: VNCserver requires CPU to compress data.

12. Experiment Results (II) Collaborative learning sessions:  Session manager also provides chat rooms.  VNC permits to share screen.  Mouse sharing modes: 1 user controls, shared control. 2 students piloting same aircraft. 1 student piloting + 1 instructor observing.

13. Further Work (I) Scheduling algorithm for interactive applications:  Network latency and BW between grid nodes and clients has to be taken into account. Session migration:  If a node fails, state of flight session must be transfered. Pedagogical evaluation:  Experiments with students in a real course.  Problems they find.

14. Further Work (II) Servidor 1Servidor 2 Servidor 4 Servidor 3 Client 1 VNC Divide rendering between “n” grid nodes:  Paralelise application.  VNC client receiving “n” screens.

15. Further requirements (after talking with some teachers) Demand resources in advance:  “Tomorrow there will be a session at 9 AM”. Save student sessions and logs for:  Re-playing sessions to learn from previous errors.  Student evaluation. Only for flight learning:  Coordination among several planes on same air space.

16. Other applications grids for bio-chemistry students.  Molecular docking,  and remote 3-D visualization.

17. Conclusions Some work need for a functional framework:  Interactive scheduling algorithm, A lot more work for an operational system:  Students are very demanding: if something fails, learning session has to post-pone. To collaborate, email us: oardaiz@ac.upc.esoardaiz@ac.upc.es  Your students use a CPU-intensive app.  Find educational applications of your grid. Thanks for your attention !!!!