Remarks on Web and Grid Services: OGSA and OGSI

1. Remarks on Web and Grid Services:OGSA and OGSI e-Science All Hands Meeting September 4 2003 Geoffrey Fox, Indiana University

2. Summary Remarks • Do we need to support OGSI and non OGSI e-Science Services? • e.g. DAIS and “Job Submit” standards should have non OGSA/OGSI service and OGSA/OGSI versions • Does OGSA imply OGSI or a set of Service functionalities or both? i.e. what is OGSA? • Is a Grid Service a Web Service? Both yes and no can be argued depending on whether need for particular technology (OGSI) is or is not a “generic” Web Service • It would be useful to have a tentative agreement on process - which standards come out of • GGF OGSA Working Group • GGF Function-specific Research/Working Group • OASIS • W3C • Application consortia • Do we want “ultimate” standards or maybe rapid prototyping agreements for next 2-3 years • Lightweight process • Some potential critical standards like WSAddressing are still under discussion • “Gap Analysis” identified many services (being) built and ripe for both standardization and productization

3. 1: Architecture and Style 2: Basic Technology Runtime and Hosting Environment 10: PortalsPSE’s 7: Information 8: Compute/File Grid Services: Application Specific Resource Specific Generic 3: Security 4: Workflow 5: Notification 6: Meta-data 9: Other Information Compute Resources 11: Network Categorization of Technical Gaps and Grid Services Area of Grid Services

4. WS WS WS WS 1: Hosting Environment “Central” Architecture/Functionality/Style Gaps • Agreement on Web Services but • Hosting Environment and component model (OGSI) uncertain • What is OGSA and what is application uncertain 6: Domain-Specific (Application) Grid Services Some GGFApplication area overlaps 5: OGSA-compliant System Grid Services e.g. submit job 4: Key OGSA Services e.g. security 3: Permeating Principles and Policies “Central Services And Architecture”Some GGFW3C OASISOverlaps 2: OGSI Web service Enhancements

5. Types of Grid R3 Lightweight P2P Federation and Interoperability Core Infrastructure and Hosting Environment Service Management Component Model Service wrapper/Invocation Messaging Security Services Certificate Authority Authentication Authorization Policy Workflow Services and Programming Model Composition/Development Languages and Programming Compiler Enactment Engines (Runtime) Notification Services Metadata and Information Services Basic including Registry Semantically rich Services and meta-data Information Aggregation (events) Provenance Information Grid Services OGSA-DAI/DAIT Integration with compute resources P2P and database models Compute/File Grid Services Job Submission Job Planning Scheduling Management Access to Remote Files, Storage and Computers Replica (cache) Management Virtual Data Parallel Computing Other services including Grid Shell Accounting Fabric Management Visualization Data-mining and Computational Steering Collaboration Portals and Problem Solving Environments Network Services Performance Reservation Operations Categories of Worldwide Grid Services

6. Many Gaps in Generic Services • Some gaps like Workflow and Notification are to make production versions of current projects • Appendix shows workflow from DAME, DiscoveryNet, EDG, Geodise, ICENI, myGrid, Unicore plus Cardiff, NEReSC …. • RGMA and Semantic Grid offer improved meta-data and Information services compared to UDDI and MDS (Globus) • Need comprehensive federated Information service • Security requires architecture supporting dynamic fine-grain authorization • UK e-Science has pioneered Information Grids but gap is continuation of OGSA-DAI, integration with other services and P2P decentralized models • Functionality of Compute/File Grids quite advanced but services probably not robust enough for LCG or Campus Grids