Convert generic gUSE Portal into a science gateway

1. Convert generic gUSE Portal into a science gateway Akos Balasko

2. Outline • Motivation • Terminology • Basic Idea • Concept of ASM • Classification of API methods 2

3. Goal Community members want to: Execute scientific applications Using distributed systems to: • decrease time cost • Exploit storage & computational capacities use complex systems totally hidden Do not want to : learn any techniques that don't fit with scientific area of them → would like to use web-interfaces based on gUSE

4. Example gateways for Scientific Communities

5. Where are we now? WS-PGRADE workflow UI WS-PGRADE UI ASM API Customized UI Other, existing UI 6

6. Terminology Grid Application Developer • would like to have a Portal customized for the application and end user community • knows how to develop a grid application in gUSE/ws-PGrade or how to port a legacy application to the grid with gUSE/ws-PGrade Grid Portal Developer • He knows the Java language and JSP (Java Server Pages) or other techniques (IceFaces etc) • He does not need to know thesource code of gUSE • He and also the end users have user certificates to access the grid

7. Terminology Grid Application Developer • Develops a grid application with gUSE • Exports it to the local repository of gUSE Grid Portal Developer • Develops an interface (in general a portlet) that fits to the application I/O pattern and the end users’ needs and associate it with the role • Connects the GUI to gUSE using the programming API of Application Specific Module(ASM) End Users, Scientists • execute a copy of the exported application with custom input parameters

8. Basic idea • A new module called “Application Specific Module” has been developed for gUSE thatease the creation of Application Specified Portlets • The moduleprovides programmingAPI to control applications developed using gUSE • The moduleprovides programmingAPI to access inner gUSE services • Any kind of Graphical interface can be developed on top of this module • GUI written in JSP, JSTL (Java Servlet Tag Library ) and Java • GUI can be customized for the grid application • GUI can be customized for end users

9. Concept Client Webbrowser ws-PGrade Internal components gUSE submitter Desktop or Service grids / cloud / Clusters DCIs 11

10. Concept Client Webbrowser We will focus on this! ws-PGrade Developed web-interface Internal components gUSE submitter Desktop or Service grids / cloud / Clusters DCIs 12

11. Concept in details Client Webbrowser You develop it Web pages (JSP, JSF or other) Developed web-interface Configuration files (wsdd) You develop it JAVA event handler, and inner classes Application Specific Module API 13

12. Concept Client Webbrowser ws-PGrade Developed web-interface Internal components gUSE Placing web-app as gUSE component submitter Desktop or Service grids / cloud / Clusters DCIs 14

13. gUSE ws-PGrade Storage Workflow Interpreter Repository User space Information Submitter Workflow Storage Concept in details DCI systems 15

14. gUSE ws-PGrade Grid Application Storage Workflow Interpreter Repository User space Information Submitter Workflow Storage Concept in details Grid Application Developer creates own Grid Application via ws-PGrade and export it to the local repository DCI systems 16

15. ws-PGrade Developed web-interface ASM Storage Workflow Interpreter Repository User space Grid Application Information Submitter Workflow Storage Concept in details Then the Grid Portal Developer creates a new web-application (mainly an web-interface) which fits to the user community's needs, and connects it to the gUSE using ASM API gUSE DCI systems 17

16. Concept in details Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet gUSE ws-PGrade Developed web-interface ASM << import >> Storage Workflow Interpreter Repository User space Grid Application Information Submitter Workflow Storage DCI systems 18

17. Concept in details Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet gUSE ws-PGrade Developed web-interface ASM Storage Workflow Interpreter Repository User space Information Grid Application Submitter Workflow Storage DCI systems 19

18. Concept in details Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet gUSE ws-PGrade Developed web-interface ASM Storage Workflow Interpreter Repository User space Information Submitter Workflow Storage DCI systems Grid Application 20

19. Concept in details Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet gUSE ws-PGrade Developed web-interface ASM Storage Workflow Interpreter Repository User space Information Grid Application Submitter Workflow Storage DCI systems 21

20. Classification of API methods • Methods are provided for full scale of • Workflow/Job Configuration • Uploading inputs • Settings input values • Setting mysql query results as inputs • Setting execution resources • Execution management • Submission/Resume/Abort • Output retrieving • possibilities offered by WS-PGRADE/gUSE • But note: nothing for changing the workflow structure itself 23

21. Technical details and try-out tomorrow... Thanks for your attention! Questions?