1 / 8

Grid Systems: What is Needed from Web Service Standards?

This panel discussion explores the relationship between the Grid and the Web, and examines the requirements for web service standards in Grid systems. Topics covered include distributed resource management, performance, security, and more. The discussion also highlights the importance of standards in integration and federation across heterogeneous environments.

kgertrude
Download Presentation

Grid Systems: What is Needed from Web Service Standards?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICSOC2004Panel Discussion:Grid Systems: What is needed from web service standards? Jeffrey Frey IBM

  2. Grid Systems • Inherently distributed • Inherently Heterogeneous • Dynamic resource discovery, allocation, and usage bindings • Loosely coupled, Late Binding • Modular Composition • Virtualized Resources • Negotiated, agreement based relationships • Cross Organizational Boundaries

  3. The Grid and the Web • Is the Grid and the Web the same thing? Or is one an extension of the other? • Is the Grid a particular behavioral personality of the Web? • What is a Web Service? What is a Grid Service? Are they the same thing? If not, what distinguishes them? • What does it mean to ask what the Grid needs from Web Service Standards? • We Know that Integration and federation across the heterogeneous, multi-vendor environment is key. Therefore, standards are key. • Is a standardized interface, behavior, or schema a "Web Service Standard" simply because it is expressed in terms of WSDL and XML? • Or is it a Web Service standard if it is named WS-*? Does it really matter?

  4. Some thoughts on distinguishing the Grid • A large scale distributed resource management system • Deployment • Discovery • Access • Allocation and Provisioning • Reservation • Scheduling • Performance • Availability • Security • Problem determination • Measured usage, accounting, rating, and billing • Etc.

  5. Mediation, Messaging, Events Business Performance Management Enterprise Service Bus Business Connections Utility Business Services Metering Services Rating Billing Peering Settlement BusinessService Service Level Automation and Orchestration Data Placement Problem Management Security Services Workload Services Configuration Services Availability Services … BusinessService Resource Virtualization Services Server Storage Network Resource Mapping Information … Infrastructure Services IBM’s On Demand Management Infrastructure

  6. Web Services Infrastructure Base layer distributed system definition • Interface Definition (WSDL, XML schema) • Expressing Metadata (WS-Resource Metadata Descriptor ?) • Accessing Metadata (WS-Metadata Exchange) • Communication protocols and bindings (SOAP/HTTP, others) • Resource property definition and access (WS-Resource Properties) • Resource Identity (?) • Query (Xpath and XQuery) • Security interfaces and protocols (WS-Security, WS-Trust, WS-Federation, SAML, WS-Secure Conversation, etc) • Naming (?) • Registries (WS-Service Group) • Workflow (BPEL4WS) • Transactional behavior and compensation (WS-Coordination and WS-Transaction) • Execution context propagation (WS-Coordination, WS-Context) • Reliable messaging (WS-Reliable Messaging) • Message mediation (?) • Event notification (WS-Notification) • Addressing and support for multi-protocol (WS-Addressing) • Relationships (?) • Policy grammar and attachment (WS-Policy) • Versioning (?) • Dynamic extension of interface and implementation (?)

  7. We have only scratched the surface The problems we have tackled to this point may have been the easy ones. A Partial List of what else is needed: • A way to represent the resources to be managed • jobs, data, servers, network, storage, application servers, database, users • base resource model, model extensions, and profiling • resource compositions • A way to express resource capabilities and usage constraints • A way to express formal relationships between resources • A way to express and scope resource management policy • A way to establish normative agreements that express the terms and conditions of the relationships between managed resources • A common management event schema • Common approaches for resource monitoring • Interfaces and protocols for each of the service level management disciplines • Interfaces and orchestration protocols for allocation, reservation, scheduling, provisioning • Interfaces data management and replication • Protocols for policy conflict detection, arbitration, and resolution • …….

  8. Some of the Standards Organizations • W3C - Base Web Service description and XML Schema • DMTF - Resource Modeling, Resource Profiles, and WS-CIM • OASIS – WS-*, Management of Web Services, Management Using Web Services • GGF - OGSA, Data Access, Data Management, Job Scheduling and Execution • We have seen proposals for cross organization collaboration • Are the Big Gorillas helping or hurting ? • Prioritization of the standards work should be use case and scenario driven

More Related