Convert generic gUSE Portal into a science gateway

Akos Balasko02/07/2012

1

Outline

General Session:GoalgUSE orchestrationWay from application to serviceComparison TerminologyBasic IdeaConcept of ASM

2

GoalEnd 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

gUSE

WS-PGRADE

ASM

Application Specific Interface

Remote access

API

Client side

Server side

Remote access client

Full access

90% access of internal services

60% access of internal services

Limited access20%

Way from application to service

Simple Application

Complex Workflow

Personal

Community Application Specific Module

Remote API

general gUSE

Own Research

Usage Types

Our Suggestions

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

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)

TerminologyGrid 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 the source code of gUSE

– He and also the end users have user certificates to access the grid

TerminologyPortal Administrator:

• installs gUSE

Grid Application Developer• Develops a grid application with gUSE• Exports it to the local repository of gUSE

End Users• execute a copy of the exported application with custom input parameters

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)

Basic idea• A new module called “Application Specific Module” has been

developed for gUSE that ease the creation of Application Specified Portlets – The module provides programming API to control applications

developed using gUSE– The module provides programming API 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

Concept

ws-PGrade

Internal components

submitter

Desktop or Service grids / cloud / ClustersDCIs

gUSE

Web browserClient

12

Concept

ws-PGrade

Internal components

submitter

Desktop or Service grids / cloud / ClustersDCIs

gUSE

Web browserClient

Developed web-interface

13

We will focus on this!

Concept in detailsWeb browserClient

Developed web-

interface

Web pages (JSP, JSF or other)

JAVA event handler, and inner classes

Application Specific Module API

Configuration files (wsdd)

You develop it

You develop it

14

Concept

ws-PGrade

Internal components

submitter

Desktop or Service grids / cloud / ClustersDCIs

gUSE

Web browserClient

Developed web-interface

15

Placing web-app as gUSE

component

DCI systems

gUSE

ws-PGrade

Submitter

Workflow Interprete

rRepository

Workflow Storage

Storage

Information User space

Concept in details

16

DCI systems

Grid Application Developer creates own Grid Application via ws-PGrade and export it to the local repository

gUSE

Repository

ws-PGradeGrid Application

Submitter

Workflow Interprete

r

Workflow Storage

Storage

Information User space

Concept in details

17

gUSE

DCI systems

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

ws-PGrade Developed web-interface

ASM

Repository

Grid Application

Submitter

Workflow Interprete

r

Workflow Storage

Storage

Information User space

Concept in details

18

gUSE

DCI systems

Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet

ws-PGrade Developed web-interface

ASM

Repository

Submitter

Workflow Interprete

r

Workflow Storage

Storage

Information User spaceGrid Application

Concept in details

<< import >>

19

gUSE

DCI systems

Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet

ws-PGrade Developed web-interface

ASM

Repository

Submitter

Workflow Interprete

r

Workflow Storage

Storage

Information User space

Grid Application

Concept in details

20

gUSE

DCI systems

Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet

ws-PGrade Developed web-interface

ASM

Repository

Grid Application

Submitter

Workflow Interprete

r

Workflow Storage

Storage

Information User space

Concept in details

21

gUSE

DCI systems

Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet

ws-PGrade Developed web-interface

ASM

Repository

Submitter

Workflow Interprete

r

Workflow Storage

Storage

Information User space

Grid Application

Concept in details

22

IntroductionSample application:

24

Input file

Output

Shell-script:Read and count numbers from input file and command line

IntroductionWould like to have :

25

End of General Session!

Questions?

Knowledge about JAVA+web-technologies are needed for followings!

Otherwise: feel free to have longer coffee-break and discussion