1

The Portal Expedition

Beth Plale, Dennis GannonIndiana University – Project Leads

Jay AlamedaNCSA – Project Coordinator

The Alliance Portals Expedition

2

Participating Individuals• Geoffrey Fox, Pervasive Technology Labs, Indiana• Marlon Pierce, Pervasive Technology Labs, Indiana• Gregor von Laszewski, Argonne National Labs• Shawn Hampton, NCSA• Al Rossi, NCSA• Liang Fang, Indiana Univ.• Gopi Kandaswamy, Indiana Univ.• Sriram Krishnan, Indiana Univ.• Chris Johnson, Univ of Utah• Yarden Livnat, Univ of Utah• Ray Plante, NCSA• Bob Wilhelmson, NCSA (unsupported)• Many others! …

3

The Big Picture

• Portal – where Grid is collection of distributed Services that unify wide area resources into a single system, the Portal is door and entrance hall to Grid– For most users, primary interaction with Grid will be through

a portal

Portal Server

SecurityServices

MetadataDirectoryService(s)

Directory& indexServices

ApplicationFactoryServices

Messagingand group

collaboration

Event andlogging

Services

Users persistentstate (context)

4

Portal Interaction Model• How does user interact with Grid using portal?

– Logging onto portal brings up person’s current Grid Context; set of portlets used to access Grid resources.

• “portlet” interfaces with client-side and remote Grid services. Portlets can provide:– simple and secure access to Grid applications and

resources– persistent references to files, metadata, applications,

event and message histories, and experiment logs– Secure sharing of applications and data within group– Access to group collaboration desktop applications

5

A Portlet Based Architecture • Portlet Concept

– Display organized in tabbed pages

– Each page is set of panes– Portlet is back-end code that

manages one pane– Standard design for Apache

Jetspeed, IBM Websphere & others

– Soon to be Java standard

• Portal is a portlet container– User configures portlets.– Portal container retains user

configuration and state– Portlets can communicate with

each other.

• Portlet as Grid service interface– A Grid service bound to portlet

so user can interact with service.

See http://www.extreme.indiana.edu/xportlets

A Portlet talking to a MyProxy certificate server

6

Portal Architecture

Secure WebServer &

Portlet Container

Secure WebServer &

Portlet Container

The Grid

Persistent user State

select, storefetch

Grid SecurityGrid Security

Browserineractions

Grid Info ServGrid Info Serv

Grid interface via Java COG Kit

Launch ServLaunch Serv File Mgmt ServFile Mgmt Serv

Message ArchiveMessage Archive

Desktop viz component

Grid User Contextdatabase

Grid User Contextdatabase

TransientApplication

Service

PersistentApplication

FactoryService

PersistentApplication

FactoryService

Most Grid Services are reflected as Portlet in portal server.

7

Existing Grid Portlets: see demo!

Provided Capability– Management of user proxy

certificates– Remote file management

via GridFTP– News/Message systems

• for collaborations– Event/Logging service– Personal directory of

services, metadata and annotations.

– Access to LDAP services– Specialized application

factories• MEAD, Earthquake science,

Particle Physics (Atlas)– Tool for testing

performance of grid information servers.

– Shared collaboration tools • Including shared

Powerpoint– Access and control of

desktop Access Grid

See http://www.extreme.indiana.edu/alliance

8

MyGridContext• A Portal service; provides each user a simple

directory of their favorite Grid “stuff”.– Each directory item can be

• An user interface to remote web service• Application execution histories (event logs)• External metadata catalog service reference

– Users can add annotations (HTML) to directory entry.

9Citation Metadata

Topic List

Citation Entry Wizard

RSS Citation Catalogue

XML Metadata Management

10

Web Services for Collaboration

Portlets collect interfaces to AV control services for merging H323, SIP, and AG.

0

5

10

15

20

25

0 200 400 600 800 1000 1200 1400 1600 1800 2000

Jitte

r (

Mill

ise

co

nd

s)

Packet Number

Average jitter/packet for 12 (of the 400 total) video clients. NaradaBrokering Avg=13.38 ms, JMF Avg=15.55 ms

NaradaBrokering-RTP JMF-RTP

Universal access to P2P, PDA, Cell Phone, Polycom, RealOne, Access Grid,…

Scalable messaging supports1000’s of Clients.

11

Links to desktop Apps for Vis

12

Current Applications

13

NCSA Grid Desktop (MEAD)•GridDesktop – Java Application container for science interface (in this case MEAD input screen, plus output monitor)

•Malleable interface to facilitate submission of hundreds of jobs

•Screenshot shows submission of one job, running of another.

Grid TaskFlow Engine – XML-based “workflow”, can monitor progress in GridDesktop

•Viewer on shows successfully completed “targets” in workflow

•Support services (metadata catalogs) track hundreds of runs

14

GRAPPA

• Atlas Experiment– Large Hadron Collider

• 100 MB/sec (10PB/year)

• Grid Access Portal for Physics Apps– To provide Atlas physicists

with an point of access to Grid resources

• Manage submission of Athena and AtlSim jobs to condor cluster

• Manage interaction of analysis with physics data and grid services

events

detector

histogram

Mesg servc

Job op servc

Particle prop

Analysismodule

Grappa NotebookApp ManagerGrappa

This is a scientificnotebook examplethere is text andthere is also some interesting graphics

and some scripts

15

Radio Astronomy: The BIMA Image Pipeline

Pipeline automatically processes data from BIMA telescope

• Integrate use of Globus Java CoG into Pipeline software

• Convert components into secure grid services– Queue Manager is

underway.

• Develop portlets for monitoring, administrating, and sending new processing requests.

16

A Collaboration on a Grid Portal Standard

• A standard for reusable Grid Portal Components– Portlet architecture modified for Grid Security– OGSI/OGSA compatible

• Partners – – NASA IPG– DOE SciDac CCTTSS

• CCA Components are OGSI Grid Services– Grid Lab (EU)– NPACI via Univ. of Texas– NEES Grid via Univ of Michigan– Argonne

• On Grid Software Repository (for services and components)• OGSA interfaces for components

16