Grid Computing Environments GCE Discussion Meeting June 26 2003 Seattle GGF8

1. Grid Computing Environments GCEDiscussion MeetingJune 26 2003 SeattleGGF8 Geoffrey Fox Dennis Gannon Pervasive Technology Laboratories Computer Science Indiana University, Bloomington IN http://www.infomall.org gcf@indiana.edu gannon@cs.indiana.edu

2. Themes for Next 18 Months ( 4-5 Meetings) • Currently we are NOT involved in formal standards work – areas (job related metadata) we discussed in past are probably best done by OGSA (in collaboration with GCE) • We are involved in identifying best practice, documenting this and collaborating to advance • In GGF documents • Journal Special issues (and book chapters) • Tutorials and other outreach • Hold formal GGF Workshops as at GGF7 on Portal Architectures • Roughly one workshop per meeting? • Meetings like this are for discussion and not (any longer) for technology presentations (change as of GG7)

3. Source of Overview of Grid Computing Environments GGF Information Document • Last Half of 2001: Call from GCE RG for Papers for Journal special issues – 28 papers submitted and reviewed • Published in Concurrency and Computation: Practice and Experience Vol. 14, Grid Computing Environments Special Issue 13-15, Fall 2002 • http://aspen.ucs.indiana.edu/gce/gce2001index.html • Augmented by chapters (about 14) in Fran Berman, Geoffrey Fox and Tony Hey, ‘Grid Computing: Making the Global Infrastructure a Reality’, ISBN 0-470-85319-0, John Wiley & Sons Ltd, Chichester, 2003. See http://www.grid2002.org • Other key papers which we knew about

4. Three Major Themes • Portal Architecture and Technology (continuation of work at GGF7) • GGF Information Document • Journal Special Issue • Workflow or “Service Orchestration”, “Service or Process Coordination”, “Service Conversation”, “Web or Grid Scripting”, “Application Integration”, “Software Bus” or perhaps best • “Web or Grid Programming” • The GCE Shell topic of previous meetings can be included here (UNIX Shell simple “classic computing” workflow) • Integration of Problem Solving Environments and GCE’s

5. > file6 a.out < file5 a) UNIX Shell Nugget Nugget OGSA-DAI Nugget b) Database Nugget JDBC Nugget3 Nugget4 c) Workflow linking Nuggets Nugget1 Nugget2 Data Two-level Grid Programming Model; Nuggets wrapped as Web Services

6. Components of Workflow • Composition/Development: This is the top level and corresponds to the workflow IDE (Integrated Development Environment) and often has a graph editor to be able to visually form the graph of “linked” nuggets. • This editor allows one to choose from a palette of available services with ports that one can choose to link. • This paradigm is familiar from visualization and image processing where systems like AVS, Khoros and SCIRun • Languages and Programming: There is usually an underlying formal language describing the workflow and the workflow is expressed as some sort of program in terms of it. • Compiler/Interpreter: This part of the workflow system translates the result of the first two steps, composition and/or program, into the executable form. • Enactment Engines (Runtime):This corresponds to the components of the execution environment supporting the execution of the workflow.

7. PSE’s and GCE’s • Most PSE’s consists of a set of services or nuggets just like GCE’s • PSE’s may or may not involve linking of distributed (Grid) resources • GCE services are ALL message based for input and output between clients, resources and other services • GCE’s should inherit PSE services wrapped as Grid Services • PSE’s could use workflow technology as their software bus?

8. GGF7 Grid Portal Architecture Workshop • Organized by Dennis Gannon, Geoffrey Fox and Mary Thomas • These are co-chairs of GCE working group – this topic is a rather focused subset of GCE mandate • Grid Information document and C&C:P&E special issue of 28 papers describes “full” GCE activities • 8 am to 1.50 pm Thursday March 6 2003, 50 attendees • 9 Presentations followed by discussion • Talks were asked to address a set of questions prepared ahead of time • This differentiated workshop from earlier meetings with “project updates” • Appropriate because broad area reasonably well covered • Final discussion agreed to produce a Grid Forum Information Document entitled Portal Component Architecture

9. Questions Addressed by Speakers • Are the current portal frameworks, such as Jetspeed, sufficient for all our requirements? • Is the portlet model the right one for Grid applications? • When is the Web “pull” model insufficient for Grid applications? • What Grid services are needed to make Grid portals useful? • Are the proposed OGSA core Grid services appropriate and useable by Grid portals? What other Grid middleware implications are there for Grid portal interoperability? • What are the requirements for a messaging and notification model to be used by Grid portals? • How do we build a GridShell? How does one create a user’s Grid Context? • How do we design a Grid portal architecture that best supports collaboration? • Two important standard have emerged: WSIA (Web Services for Interactive Applications) and WSRP (Web Services for Remote Portals). Are these sufficient for the requirements of Grid Applications?

10. Typical Jetspeed Portal Each Tab displays multiple Portal ComponentEach user interface component maps to aGrid Service

11. Workshop Speakers • Introduction and Workshop Charge Dennis Gannon • Overview of GCE and Grid Portal Issues Geoffrey Fox • Background: OGSA, WSIA and WSRP and Grid Contexts Dennis Gannon • GridLab Portal Technology Michael Russell • GridPort Technology Mary Thomas • The CHEF Portal Charles Severance • The Grid Portal Generator Toyotaro Suzumura • GENIUS and EnginFrame: GRID Portal across Research and Industry • Roberto Barbera and Andrea Rodolico • Mississippi Portal Tom Haupt

12. Portal Component Architecture Document • GGF Information Document based on workshop • 1 Overview/motivation • 2 Portal Component Architecture (examples, general issues) • 3 Using Component-based Portals Today • 4 Futures of Portal Component Paradigms • 4.1 New paradigms • 4.2 Enhancing current paradigms • 4.3 Portal Component Design issues • 4.4 Security Considerations • Appendix: Examples of use of current Component-based Portals • Draft should be completed by GGF8 where it be discussed in a GCE meeting

13. GGF-GCE: GGF6 Summary • Charter • Revised to reflect current GGF research group definitions and proposed activities • Volunteers: Secretary-- Jay Alameda; Webmaster-- Shawn Hampton, Brooke Carlson • Proposed Activities for 2003 • Planned Activities for GGF7: Workflow Specifications & Management (Piyush, Haupt) • Considering holding with Applications testbed • Others: Portal technologies (Marlon, Mike); GCE Shell (Fox, Cezary Mazurek)); Grid Applications & testbed (future considerations • Informational Docs in progress • C&C:P&E Summary (Thomas, Fox, Gannon) • GCE Shell (Fox, Pierce) • Workflow/Metadata Current Practices, summary, survey (Mehrotra) • Previous external workshop activities (seeking volunteers) Done!!!

14. GGF5 Grid Computing Environments RG • Sessions 1&2: Grid Jobs: Metadata and Management • 10 presentations, 50-80/session • “Best Practices” survey, produce GGF Info doc by GGF7 • Session 2: Organizational issues/discussions (>40 attendees) • Revised charter, plans to update website • Defined current ‘targeted areas’ for RG and current activities: 28 publications on portals, Grid Job metadata survey, interoperable web services demo@SC02, experiment with schemas needed for interoperable web services • Identified new targeted activities to study portlets, OGSA-based Grid services, experiments technologies in a testbed fashion Topic to OGSA!