# Presentation: 160433

## Computational Grid Portals

- Marlon Pierce
- Community Grids Lab
- Indiana University

## Open Grid Computing Environment Collaboratory

- Funded by NSF’s National Middleware Initiative
- University of Chicago
- Gregor von Laszewski
- University of Illinois/NCSA
- Jay Alameda
- Joe Futrelle
- Indiana University/Community Grids Lab and CS
- Marlon Pierce
- Geoffrey Fox
- Dennis Gannon
- Beth Plale
- University of Michigan
- Charles Severance
- Joseph Hardin
- University of Texas/TACC
- Mary Thomas
- Jay Boisseau

## What Are Grid Portals?

- Computing portals provide ubiquitous, browser-based access to grid resources.
- No special client software or platform needed
- Access information in visually intuitive form
- Provide services to support user interactions
- Job archivingportal metadata management services
- Combine core grid services into custom services
- Launch multistage jobs with dependencies
- Couple execution, file transfer, visualization/analysis
- Many, many such projects
*Concurrency and Computation: Practice and Experience’s* special issue described more than two dozen in 2001.
- GCE Research Group of the GGF is the community forum.
- Thomas, Gannon, and Fox are chairs.

## What Are the Problems?

- Problems are always the same:
- How do we share portal services?
- How do we reuse components between projects and groups?
- Can we provide a standard abstraction for portal services and interfaces?
- Can we provide an architecture that allows services and user interface components to be added in a standard way?
- Need to shorten the “standard service” deployment phase so that we can concentrate on harder problems, specific sophisticated services
- Fusion Grid needs very interactive, visual interface for setting up problems
- Need to be able to deploy standard components like MyProxy, GridFTP, etc interfaces quickly

## General Portal Architectures

## Portal Service ComponentsSciDAC Fusion Grid Example

- Grid
- Auth

- GRAM

- Grid
- FTP

- GRIS/
- GIIS

- TRANSP

- MDSPlus

- SRB

- IDL
- Services

- WSDL

- WSDL

- GPIR

- WSDL

- ...

- WSDL

- SRB
- Client

- Portlet Container

- GridPort

- Portal
- Login

- Java COG

- TRANSP
- Submit

- WSDL

- GPIR

- COG/GP

- Proxy
- Manager

- Java COG

- LDAP
- Browser

- WSDL

- File
- Manager

- WSDL

- IDL
- Clients

**FG Hardware**

**FG Applications**

- ...

## SERVOGrid Codes, Relationships

- Elastic Dislocation

- Pattern Recognizers

- Fault Model BEM

- Viscoelastic Layered BEM

- Viscoelastic FEM

- Elastic Dislocation Inversion

## Problems: Data Access and Sharing, Code Integration

- Codes all use custom text formats for describing input and output.
- Input and output data often combined with code-specific information.
- Number of iterations, array sizes, etc.
- Data files often created by hand from journals, online repositories
- Online repositories themselves use differing formats
- Challenges are to develop common data formats, access services, and client query tools.

## RIVA

- DB Service 1

- JDBC

- DB

- Job Sub/Mon
- And File
- Services

- Operating and
- Queuing
- Systems

- Browser Interface

- Viz Service

- Host 1

- Host 2

- Host 3

## Web Services for Data Access and Computing Service Invocation

- Service-oriented architecture
- Web services:
- WSDL: Interface definition language, describes your service
- “GeoFEST may be invoked with these input types”
- SOAP: Transport envelope for remote procedure calls/messages
- “Invoke GeoFEST with this set of input”
- Together, WSDL and SOAP are useful for manipulating, returning XML data values
- WSDL and SOAP are platform independent
- C/C++, Java, Python, Perl bindings.
- So you can build a variety of clients that use the same backend services
- Browsers and more sophisticated workbench GUIs.
- Turn the problem on its head: embed service calls in legacy code
- Better data access methods
- I want to use your mesh generator

## GML Schemas as Data Models for Services

- Fault and GPS Schemas are based on GML-Feature object.
- Seismicity Schema is based on GML-Observation object.
- Working schema available from _[http://](http://grids.ucs.indiana.edu/~gaydin/schemas/)__[grids.ucs.indiana.edu/~gaydin/schemas](http://grids.ucs.indiana.edu/~gaydin/schemas/)__[/](http://grids.ucs.indiana.edu/~gaydin/schemas/)_

## Grid Testbed for Portal Demo

- complexity.ucs.indiana.edu
- Solaris Sunfire web server
- Web server for portal
- Danube.ucs.indiana.edu
- Duel processor linux server
- Runs AKRIA,GeoFEST, GMT
- Grids.ucs.indiana.edu:
- Sun Ultra 60
- Runs Disloc
- Infogroup.usc.edu
- Linux box
- Runs Mysql fault database
- Jabba.jpl.nasa.gov:
- SGI Origin(?)
- Runs RIVA for movies