Convert generic gUSE Portal into a science gateway

1. Convert generic gUSE Portal into a science gateway Akos Balasko 02/07/2012

2. Outline • General Session: • Goal • gUSE orchestrationWay from application to service • Comparison • Terminology • Basic Idea • Concept of ASM

3. Goal End users 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. gUSE orchestration Client side Remote access client Application Specific Interface 60% access of internal services WS-PGRADE 90% access of internal services Limited access20% Full access ASM gUSE Remote access API Server side

5. Way from application to service Usage Types Own Research Our Suggestions Personal generalgUSE SimpleApplication ComplexWorkflow Remote API Community ApplicationSpecificModule

6. Remote API vs. ASM • Remote API: • Pro: • Servlet-technology • Language-independent • Hidden complexity • Easy API • Cont: • Workflow must be on „client side” • No workflow management • Tight range of functionalities

7. Remote API vs. ASM • ASM API: • Pro: • Wide range of functionalities • Covers whole workflow-lifecycle • Workflow management • Hidden complexity • Easy API • Cont: • Language-dependent (Java)

8. 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

9. Terminology • Portal Administrator: • installs gUSE • 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 • execute a copy of the exported application with custom input parameters

10. 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

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

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

13. 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

14. 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

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

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

17. 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 ws-PGrade Developed web-interface ASM Storage Workflow Interpreter Repository User space Grid Application Information Submitter Workflow Storage DCI systems

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 << import >> Storage Workflow Interpreter Repository User space Grid Application Information Submitter Workflow Storage DCI systems

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

20. 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

21. 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

22. Introduction • Sample application: Output Input file Shell-script: Read and count numbers from input file and command line

23. Introduction • Would like to have :

24. End of General Session! • Questions? • Knowledge about JAVA+web-technologies are needed for followings! • Otherwise: feel free to have longer coffee-break and discussion