Bringing Grid & Web Services Together Globus World San Francisco, CA Tuesday, January 20th, 2004 Dr. Daniel Sabbah Vice President of Strategy & Technology IBM Software Group

The Best of Both Worlds Web Services & Grid Requirements share manage When the IBM team responsible for defining an architecture for grid computing started it’s work about 18 months ago they observed an interesting intersection between the requirements that were driving the definition of web services and those that they found relevant to grid computing. (CLICK) Web service seemed to be about breaking down applications into composable services that share manage access Applications on demand Resources on demand Secure and universal access Global Accessibility Business integration Vast resource scalability Web Services Grid Protocols

What we are announcing today Proposals to extend to Web services Driven by requirements from: Grid computing Systems Management Business computing Key to infrastructure for IBMs On Demand Initiative Grid Computing Systems Management Web Services business on demand Business Computing

What we are announcing today Why we developed these proposals To have an architecture that is more clearly aligned with the general evolution of Web services To provide a collection of related specifications that can be used either individually or in combinations… …. and will integrate more effectively with other Web services standards To more closely align with existing language and platform programming models and application development tools

What we are announcing today A family of Web services specification proposals Introduces a design pattern to specify how to use Web services to access “stateful” components Introduce message based publish-subscribe to Web services Introduced Today WS-Notification WS-Resource Properties WS-Resource Lifetime Modeling Stateful Resources with Web Services WS-Service Group WS-Base Faults To be developed WS-Renewable References

What we are announcing today WS-Notification Provides a publish-subscribe messaging capability for Web Services WS-Resource framework A family of Web services specifications that clarify how “state” and Web services combine Both: Build upon existing Web services specifications and technology Help align Grid computing, Systems Management and Web services Contributed to by: WS-Resource Framework: IBM, Globus, HP WS-Notification: IBM, Globus, Akamai, HP, SAP, Tibco, Sonic

OGSA Architected Services How these proposals relate to OGSA WS-Resource Framework & WS-Notification are an evolution of OGSI Lets build up a taxonomy of the components of OGSA. There are four main layers which comprise the OGSA architectural view. (CLICK) The lowest layer is comprised of the basic IT resources such as processors, storage systems, and network subsystems and the hardware specific support software in operating systems, subsystems and components that control them. For the most part these resources are made “visible” to the OGSA structure by adding function to that software to “virtualize or abstract” the hardware and system resources as “services”. (CLICK) Just above these is a layer of function like file systems, databases, messaging software, directories, etc. which are typically implemented as general purpose middleware. This middleware generally exploits the lower layer of physical resource and also provides function that can be “abstracted” and “virtualized” as services in OGSA. (CLICK) As a “Service Oriented Architecture” OGSA is Fundamentally an extension of the existing Web Services infrastructure defined by standards like XML, WSDL, SOAP, etc. OGSA takes advantage of middleware application servers that provide programming support and hosting for web services implementations. (CLICK) OSGA Then “sits” on top of this support for web services. (CLICK) And Grid Applications in turn exploit the services that OGSA defines to manage and exploit the distributed resources of the grid. OGSA Services can be defined and implemented as Web services OSGA can take advantage of other Web services standards OGSA can be implemented using standard Web services development tools Grid applications will NOT require special Web services infrastructure Applications OGSA Architected Services WS-Service Group WS-Renewable References WS-Notification Modeling Stateful Resources with Web Services WS-Base Faults WS-Resource Properties Lifetime Web Services Web Services OGSI – Open Grid Services Infrastructure Security OGSA Enabled Workflow OGSA Enabled Database OGSA Enabled File Systems OGSA Enabled Directory OGSA Enabled Messaging OGSA Enabled Servers OGSA Enabled Storage OGSA Enabled Network OGSA Enabled

WS-Renewable References How these proposals relates to other Web services standards: Service Composition WS-Service Group WS-Notification BPEL4WS Quality of Experience (QoX) WS-Reliable Messaging WS-Transaction WS-Security WS-Resource Lifetime Description WS-Resource Properties WS-Base Faults XSD WSDL WS-Policy WS-Metadata Exchange Messaging XML SOAP WS-Addressing WS-Renewable References Transports HTTP/HTTPS SMTP RMI / IIOP JMS

WS-Resource Framework Capabilities Specifies how to use XML to describe and access a resource’s properties Clarifies how stateful resources are addressed Defines how a resource is created and messages to destroy resources Provides a message subscription and notification mechanism for Web services Outlines how to organize groups of resources and services Adds a fault tolerance capability to WS-Addressing Defines a standard, extensible format for Web services error messages

Web Services and Stateful Resources “State” appears in almost all applications Data in a purchase order Current usage agreement for resources on a grid Metrics associated with work load on a Web server There are many possible ways Web services might model, access and manage state The WS-Resource framework proposes to standardize this capability for Web services

The WS-Resource framework model Web Service Run-time environment WSDL Interface Web Service

The WS-Resource framework model Invoking a Web Service Endpoint Reference Run-time environment message Interface Web Service address message

The WS-Resource framework model What is a WS-Resource Examples of WS-Resources: Physical entities (e.g.. processor, communication link, disk drive) or Logical construct (e.g.. agreement, running task, subscription) Real or virtual Static (long-lived, pre-existing) or Dynamic (created and destroyed as needed) Simple (one), or Compound (collection) Unique - Has a distinguishable identity and lifetime Stateful - Maintains a specific state that can be materialized using XML May be accessed through one or more Web Services resource

The WS-Resource framework model Using a Web service to access a WS-Resource Endpoint Reference Run-time environment id context resource message Interface Web Service address message id

The WS-Resource framework model Using a Web service to access a WS-Resource Endpoint Reference Endpoint Reference Run-time environment id resource message Interface Web Service message context address id resource

The WS-Resource framework model Creating / Locating a WS-Resource Endpoint Reference Run-time environment Endpoint Reference id resource message address Interface Web Service address message Web Service either locates or creates a WS-Resource

The WS-Resource framework model WS-Resource Properties Resource state and metadata “Projected” as an XML document Query and Set operations WS-Resource LifeTime Explicit destruction or “Soft state” time-to-live Provides for cleanup of resource instances resource <ProcessorProperties> <ProcID>5A34C1DE03</ProcID> <ProcArchitecture>Power6.2</ProcArchitecture> <ProcSpeedMIPS>400</ProcSpeed> <ProcCacheMB>256<ProcCache> <ProcRunning>1</ProcRunning> </ProcessorProperties>

The WS-Resource framework model Architecture rationale WS-Resource framework exploits WS-Addressing Web services and WS-Resources are referenced using an “Endpoint Reference” Services that create or locate WS-Resources return Endpoint References Web service and WS-Resource are separate: A Web service is stateless A WS-Resource provides a context for stateful execution Different entities, different lifetimes, different capabilities

WS-Notification WS-Notification Brings enterprise quality publish and subscribe messaging to Web services Loosely coupled, asynchronous messaging in a Web services context WS Notification exploit WS Resource framework and Web services technologies

WS-Notification Subscriber indicates interest in a particular “Topic” by issuing a “subscribe” request Broker (intermediary) permits decoupling Publisher and Subscriber “Subscriptions” are WS-Resources Various subscriptions are possible Publisher need NOT be a Web Service Notification may be “triggered” by: WS Resource Property value changes Other “situations” Broker examines current subscriptions Brokers may “Transform” or “interpret” topics Federate to provide scalability Subscriber subscribe notify Broker notify subscribe notify S S S Publisher notify

WS-Notification Characteristics of WS-Notification: Web services integration of traditional enterprise publish/subscribe messaging patterns Composes with other Web services technologies Facilitates integration between different messaging middleware environments Standardizes the role of Brokers, Publishers, Subscribers and Consumers Provides two forms of publish/subscribe: direct publishing and brokered publishing Standardizes Web service message exchanges for publishing, subscribing and notification delivery Defines XML model of Topics and TopicSpaces to categorize and organize notification messsages

WS-Resource framework & WS-Notification Scenario: Grid Resource Management & Scheduling Grid “Jobs” and “tasks” are also modeled using WS-Resources and Resource Properties Grid Scheduler is a Web Service Local processor manager is “front-ended” with A Web service interface Other kinds of processors are also “modeled” as same type of WS-Resources J Grid Scheduler A Service Level Notification WS-Resource used to “model” physical processor resources Service Level Agreement is modeled as a WS-Resource Blades R Cluster R Mainframe R WS-Notification can be used to “inform” the scheduler when processor utilization changes Lifetime of SLA Resource tied to the duration of the agreement WS-Resource Properties “project” processor status (like utilization)

IBM Support for WS-Notification & WS-Resource Framework As standards mature and are broadly adopted IBM WebSphere Family and related Rational tools Provide a runtime environment that supports WS-Resource Framework and WS-Notification WS-* standards and Service Oriented Architecture (SOA) exploited: Including WS-Security, WS-Reliable Messaging, WS-Resource Framework, WS-Notification etc. Fundamental to IBM’s OnDemand operating environment System Management, Autonomic Computing Data Management and Storage Management Knowledge Management and Collaboration Business Computing Services

WS-Resource framework & WS-Notification Value: To software developers: Reduced cost / time to develop software Use of existing WS development tools Reuse of common components Permit interoperation with other vendors components To customers Increased solution flexibility & interoperability Support heterogeneous distributed computing environment Create solutions from multiple vendor components Interoperability with partners using other software Open reference implementations available

WS-Resource Framework & WS-Notification NEXT STEPS WS-Renewable References Begin Public Comment Process WS-Base Faults WS-Service Group WS-Resource Properties WS-Lifetime WS-Notification WS-Addressing WS-Security

WS-Resource Framework & WS-Notification NEXT STEPS Interoperability Demonstration WS-Renewable References Begin Public Comment Process WS-Base Faults WS-Service Group WS-Notification WS-Resource Properties WS-Lifetime

WS-Resource Framework & WS-Notification NEXT STEPS Standards Body Interoperability Demonstration WS-Renewable References Begin Public Comment Process WS-Base Faults WS-Service Group

WS-Resource Framework & WS-Notification NEXT STEPS Standards Body Interoperability Demonstration WS-Renewable References Begin Public Comment Process WS-Base Faults WS-Service Group