© 2004 IBM Corporation ICSOC2004 Panel Discussion: Grid Systems: What is needed from web service standards? Jeffrey Frey IBM.

Slides:



Advertisements
Similar presentations
Bringing Grid & Web Services Together
Advertisements

Fujitsu Laboratories of Europe © 2004 What is a (Grid) Resource? Dr. David Snelling Fujitsu Laboratories of Europe W3C TAG - Edinburgh September 20, 2005.
Abstraction Layers Why do we need them? –Protection against change Where in the hourglass do we put them? –Computer Scientist perspective Expose low-level.
Hello i am so and so, title/role and a little background on myself (i.e. former microsoft employee or anything interesting) set context for what going.
The Open Grid Services Architecture, Version 1.0 I. Foster, H. Kishimoto, A. Savva, D. Berry, A. Djaoui, A. Grimshaw, B. Horn, F. Maciel, F. Siebenlist,
Internet Technologies (Grid Computing (OGSA, WSRF) )
SOA and Web Services. SOA Architecture Explaination Transport protocols - communicate between a service and a requester. Messaging layer - enables the.
Service Oriented Architecture Concepts March 27, 2006 Chris Armstrong
Independent Insight for Service Oriented Practice Communicating SOA.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
T Network Application Frameworks and XML Service Federation Sasu Tarkoma.
Grid Architecture: Representing NextGRID David Snelling Fujitsu Labs Europe.
Distributed Heterogeneous Data Warehouse For Grid Analysis
SOA with Progress Philipp Walther Consultant. © 2007 Progress Software Corporation2 Agenda  SOA  Enterprise Service Bus (ESB)  The Progress SOA Portfolio.
Latest techniques and Applications in Interprocess Communication and Coordination Xiaoou Zhang.
CSC-8530: Distributed Systems Christopher Salembier 28-Oct-2009.
Introduction and Overview “the grid” – a proposed distributed computing infrastructure for advanced science and engineering. Purpose: grid concept is motivated.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Service-oriented architecture. The Basic main concepts –Service-orientation describes an architecture that uses loosely coupled services to support the.
Secure Systems Research Group - FAU Web Services Standards Presented by Keiko Hashizume.
Assoc. prof., dr. Vladimir Dimitrov University of Sofia, Bulgaria
Just a collection of WS diagrams… food for thought Dave Hollander.
1 Modeling Stateful Resources with Web Services ICE Ph.D lecture Byung-sang Kim.
Initial slides for Layered Service Architecture
Web Service Standards, Security & Management Chris Peiris
“This presentation is for informational purposes only and may not be incorporated into a contract or agreement.”
Web Services and HL7v3 in IHE profiles Vassil Peytchev Epic.
Managing Service Metadata as Context The 2005 Istanbul International Computational Science & Engineering Conference (ICCSE2005) Mehmet S. Aktas
GT Components. Globus Toolkit A “toolkit” of services and packages for creating the basic grid computing infrastructure Higher level tools added to this.
Web Services Security Standards Overview for the Non-Specialist Hal Lockhart Office of the CTO BEA Systems.
© 2002 IBM Corporation IBM Software Group IBM | 2004 © 2004 IBM Corporation BI-ICS Business Integration - Information Conformance Statements And the evolution.
September 12-15, 2004 Philadelphia Marriott Philadelphia, Pennsylvania Web Services Distributed Management Heather Kreger – IBM Igor Sedukhin – CA William.
Web Services Standards. Introduction A web service is a type of component that is available on the web and can be incorporated in applications or used.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Shibboleth Akylbek Zhumabayev September Agenda Introduction Related Standards: SAML, WS-Trust, WS-Federation Overview: Shibboleth, GSI, GridShib.
Semantic Web Technologies Research Topics and Projects discussion Brief Readings Discussion Research Presentations.
GRID Overview Internet2 Member Meeting Spring 2003 Sandra Redman Information Technology and Systems Center and Information Technology Research Center National.
EGA Discussion November 2004 Promoting and Standardizing Grid Computing Complexity Matters Andrew Grimshaw Virginia OGSA Architecture Area Director ICSOC.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE User Forum, Manchester, 10 May ‘07 Nicola Venuti
Kemal Baykal Rasim Ismayilov
Web Service Resource Framework WSMO Presentation Jos de Bruijn Digital Enterprise Research Institute http ://
16/11/ Semantic Web Services Language Requirements Presenter: Emilia Cimpian
OGSA-Basic Services Prof S.Ramachandram. Outline  Introduction  Common Management Model  Policy Architecture  Security Architecture  Metering and.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
Steve Graham WS-ResourceFramework Modeling Stateful Resources With Web services OASIS WSRF TC F2F Wednesday, April 28th, 2004.
Janakiram MSV Sr. Technology Strategist | Microsoft India Development Center.
Reliable Web Service Execution and Deployment in Dynamic Environments * Markus Keidl, Stefan Seltzsam, and Alfons Kemper Universität Passau Passau,
Franco Travostino and Admela Jukan jukan at uiuc.edu June 30, 2005 GGF 14, Chicago Grid Network Services Architecture (GNSA) draft-ggf-ghpn-netserv-2.
WS-Resource Framework University of Amsterdam
Exploring opportunities in the OGSA service model– realising Utility Computing Jeffrin J. Von Reich Chief architect Hewlett Packard Software Global Unit.
Issues in Cloud Computing. Agenda Issues in Inter-cloud, environments  QoS, Monitoirng Load balancing  Dynamic configuration  Resource optimization.
SuperComputing 2003 “The Great Academia / Industry Grid Debate” ?
OGSA Session #1 Execution Management Services
GGF OGSA-WG, Data Use Cases Peter Kunszt Middleware Activity, Data Management Cluster EGEE is a project funded by the European.
The GEMBus Architecture and Core Components
Bringing Grid & Web Services Together
3 Cloud Computing.
W3C Workshop WS-Policy in the Web Service Architecture
Large Scale Distributed Computing
Service Oriented Architecture (SOA)
Resource and Service Management on the Grid
The Anatomy and The Physiology of the Grid
The Anatomy and The Physiology of the Grid
Web Services Distributed Management
Presentation transcript:

© 2004 IBM Corporation ICSOC2004 Panel Discussion: Grid Systems: What is needed from web service standards? Jeffrey Frey IBM

© 2004 IBM Corporation ICSOC 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

© 2004 IBM Corporation ICSOC 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?

© 2004 IBM Corporation ICSOC 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.

© 2004 IBM Corporation ICSOC IBM’s On Demand Management Infrastructure Enterprise Service Bus Utility Business Services Resource Virtualization Services Business Connections Availability Services Security Services BillingRating Metering Services ServerStorageResource MappingNetwork Service Level Automation and Orchestration Workload Services Configuration Services PeeringSettlement Infrastructure Services Information Mediation, Messaging, Events Problem Management … … Data Placement Business Service Business Performance Management

© 2004 IBM Corporation ICSOC 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(?)

© 2004 IBM Corporation ICSOC 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  …….

© 2004 IBM Corporation ICSOC 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