Holding slide prior to starting show

1
Holding slide prior to starting show
2
A Portlet Service Model for GECEM

• Maria Lin and David Walker Cardiff University

3
Project Collaborators

• Cardiff University
• Swansea University
• BAE Systems
• HP
• Singapore Institute of HPC

4
Outline

• Project Overview
• Design
• Screenshot
• Future Work
• Conclusion

5
Project Objective

• Integration of mesh generation, large-scale
  linear system solver, and collaborative
  visualization within a Web service framework.
• Problem domain is computational electromagnetics

6
GECEM Prototype Grid
7
GECEM Production Grid
Other locations
8
Design

• Use portal and portlets to provide end-user
  interfaces for using grid services
• Use Globus Reliable File Transfer (RTF) Service
• Use Globus Job Submission Service
• Use MyProxy as a single user log-on

9
GECEM Portal

• GridSphere
• Grid Portlets
• GECEM Portlets

10
GridSphere vs Jetspeed

• http//www.gridsphere.org/gridsphere/gridsphere?ci
  dcomparison

GridSphere Jetspeed
Support for localization y n
Support for third-party portlet packaging and deployment y n
Template project build support for the creation of new portlet web applications y n
Support for "portlet service" model for the development of services to perform portlet business logic y n
Custom tag library for creating higher level visual components y n
Integrated unit testing y n
11
GridSphere

• Provide login service
• Different role base
• Different user
• Provide Portlet subscription
• Provide layout selection
• Allow third-party portlet

12
GridSphere

• Based on IBM Websphere
• Open source
• Developed by people from GridLab
• Based on MVC model
• Compliant with JSR 168
• Use ActionPortlet Model tags, beans and events

13
Grid Portlets

• Registry Resource
• Implement authentication and certification
  management through myproxy
• Provide Job Submission Service
• Reliable File Transfer Portlet

14
Registry Resource

• Hand-written XML registry
• Define Hardware resources
• Define Service resources
• For myproxy-server

15
Specifying resource

• lthardware-resource labelGecem Myproxy machine
• descriptionMyproxy resource
• hostnamemyproxy.grid-support.ac.uk
• ltcredential-repository labelGecem Myproxy
  machine
• port7512
• certfile
• keyfile
• proxyfile/tmp/proxy.pem/gt
• lt/hardware-resourcegt

16
MyProxy

• Store Credential in a MyProxy Server
• Configure GridPortlets to apply single logon
  using myproxy credential
• Retrieve credential using myproxy password
• Next time logon using myproxy password

17
GECEM Portlets

• Select Resources/Machines
• Select Files
• Submit Job to run meshes and solvers simulation

18
Select Files
Data
Meshers
Solvers
Code Swansea
Geometry Files BAES
Code Swansea
19
Job Submission

• View input files
• Use Gridportlets for myproxy authentication,
  Reliable File Transfer and Job Submission
• Run script to automate execution of file transfer
  and job submission
• Use Gnuplot to visualize output

20
Current Version

• Use Gridsphere 1.1.2 as the portlet-based portal
• Use Gridportlets for myproxy authentication,
  Credential Management and Retrieval
• Data Portlets to select files
• Job Submission Portlet
• transfer file using GT3 Reliable File Transfer
  (RFT) Service
• submit jobs for remote execution

21
GECEM portal
File Selection
Job Submission Portlet
RFT
Mesh
Solver
Data
GRAM
gnuplot
GridSphere Portal Tomcat
Credential Management
Logon
MyProxy
OGSA
OGSI (GT3)
22
Deploy and startup

• make sure CATALINA_HOME environment variable is
  set to the rootdir of the tomcat installation
• startup tomcat
• point your browser to http//localhost8080/grids
  phere/gridsphere

23
Gecem Portal Login
24
Gecem Portal
25
Configure GridPortlet
26
Credential Management
27
(No Transcript)
28
Select File
29
Submit Job
30
(No Transcript)
31
Visualize Output
32
Software

• Prerequisite Software
• Java 2 Standard Edition version 1.4.2 or higher. 
• Apache Ant version 1.6
• GridSphere 1.1.2
• Grid portlets web application (CVS)
• Globus Toolkit (GT3)

33
Limitations

• The standards and technology are changing
• Globus 3 was still in development
• GridSphere was still in development
• Grid Portlets web application was still in CVS
  version

34
Limitations

• The codes are not stable
• The codes was not compatible between versions
  especially from Gridportlets
• Credential Management
• File Transfer
• File Browser
• Difficult to integrate the works done from one
  version to the other

35
Advantages of GridSphere

• User interface is great to hide the complexity of
  accessing grid resources
• One single password is needed to access different
  resources
• Portlet API similar to Java Servlet API
• User Interface tag library
• Use of third-party portlet
• JSR-168 compliant

36
Related Work

• Alliance Portal at Indiana University
• Open Grid Computing Environment (OGCE)
• Sakai Project (http//www.sakaiproject.org)
• CHEF
• Gridport 3.0

37
Under Development

• Use GridSphere 2.0 as the portlet-based portal
• GridPortlets
• myproxy authentication, Credential Management and
  Retrieval
• Use GridFTP for file transfer
• Meshes and Solvers as OGSA grid services
• Data Portlet to select files using a file browser
• UDDI Portlet to publish and inquire web services
• Portlets to invoke grid services

38
Future Work

• Integrate with the Web Service provided by
  Swansea
• Use workflow model
• Extend GECEM grid to include all project partners

39
References

• GridSphere
• http//www.gridsphere.org/
• A Web Service Architecture for GECEM
• Maria Lin, David Walker, Yu Chen and Jason Jones
• At AHM2004

40
(No Transcript)