Service Oriented Grid Architecture Hui Li


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Service Oriented Grid Architecture Hui Li

  1. 1. Service Oriented Grid Architecture Hui Li ICT in Business Colloquium, LIACS Mar 1 st , 2006 Note: Part of this presentation is based on Dr. Ian Foster’s talks ( http://www- )
  2. 2. Outline <ul><li>Service Oriented Architecture (SOA) </li></ul><ul><li>Stateful Grid Services - WSRF </li></ul><ul><li>Grid Dynamics </li></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Resource Management </li></ul></ul><ul><li>System Level Science </li></ul><ul><li>Business on Demand, Adaptive Enterprises </li></ul><ul><li>Discussions, Assignments </li></ul>
  3. 3. Service Oriented Architecture <ul><li>A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed. </li></ul><ul><li>Distributed Computing Technology: DCOM, CORBA </li></ul><ul><li>Web Services (SOAP, UDDI, WSDL, XML, XACML, etc) </li></ul>
  4. 4. An Enterprise View
  5. 5. Grid and SOA – A Brief History <ul><li>`95-`02: I-Way, Globus, NASA IPG </li></ul><ul><li>`02- : Globus 2 Toolkit , EDG (EGEE, LCG), Grid3/OSG, Scientific Communities </li></ul><ul><li>`03- : Globus 3, OGSA, Web Services, Industry Sponsors, GGF </li></ul><ul><li>`04- : Globus 4, WSRF, Grid Services , Virtual Organizations, Communities, Social Dynamics, GGF </li></ul>
  6. 6. Reality -> Vision <ul><li>Heterogeneity -> Virtualization </li></ul><ul><li>Diversity -> Standards </li></ul><ul><li>Isolated -> Interoperable </li></ul><ul><li>Tightly-coupled -> Loosely-coupled </li></ul><ul><li>Manual -> Automated </li></ul><ul><li>… … </li></ul><ul><li>Toolkit based? Service Oriented ! </li></ul>
  7. 7. Why Grid? <ul><li>Leveraging existing web services standards and fabric </li></ul><ul><li>WSRF – building stateful Grid services </li></ul><ul><li>Other standards contributions </li></ul><ul><li>Grid services for distributed resource sharing </li></ul><ul><ul><li>Resource Management, Security, Information Services, Data Management, Programming Environments, etc </li></ul></ul>
  8. 8. WSRF – Stateful Services <ul><li>Standard Web Services are stateless </li></ul><ul><li>Without state, how does client: </li></ul><ul><ul><li>Determine what happened (success/failure)? </li></ul></ul><ul><ul><li>Find out how many files completed? </li></ul></ul><ul><ul><li>Receive updates when interesting events arise? </li></ul></ul><ul><ul><li>Terminate a request? </li></ul></ul>Client FileTransfer Service move (A to B) move
  9. 9. WSRF in a Nutshell <ul><li>Service </li></ul><ul><li>State representation </li></ul><ul><ul><li>Resource </li></ul></ul><ul><ul><li>Resource Property </li></ul></ul><ul><li>State identification </li></ul><ul><ul><li>Endpoint Reference </li></ul></ul><ul><li>State Interfaces </li></ul><ul><ul><li>GetRP, QueryRPs, GetMultipleRPs, SetRP </li></ul></ul><ul><li>Lifetime Interfaces </li></ul><ul><ul><li>SetTerminationTime </li></ul></ul><ul><ul><li>ImmediateDestruction </li></ul></ul><ul><li>Notification Interfaces </li></ul><ul><ul><li>Subscribe </li></ul></ul><ul><ul><li>Notify </li></ul></ul><ul><li>ServiceGroups </li></ul>Service GetRP GetMultRPs SetRP QueryRPs Subscribe SetTermTime Destroy EPR EPR EPR RPs Resource
  10. 10. Retro… <ul><li>Service Oriented Architecture </li></ul><ul><li>Grid adopts SOA </li></ul><ul><li>Grid uses Web Services as a platform </li></ul><ul><li>Stateful Grid Services </li></ul><ul><ul><li> </li></ul></ul>
  11. 11. What the Grid looks like in 5 years? <ul><li>Panel discussion in Grid’05, Seattle, WA </li></ul><ul><li>Fran Berman (SDSC): Data -> Social Dynamics </li></ul>
  12. 12. Grid Dynamics <ul><li>Grid = dynamic behaviors & environments </li></ul><ul><ul><li>Dynamic communities (VOs) & activities </li></ul></ul><ul><ul><li>Decoupling of service consumption from service production </li></ul></ul><ul><ul><li>Dynamic provisioning of services </li></ul></ul><ul><li>Tools to realize dynamic scenarios </li></ul><ul><ul><li>Uniform state representation & access </li></ul></ul><ul><ul><li>Flexible security & policy framework </li></ul></ul><ul><ul><li>Virtual machines, dynamic services, & other building blocks </li></ul></ul>
  13. 13. A Two-Dimensional Problem <ul><li>Decompose across network </li></ul><ul><li>Clients integrate dynamically </li></ul><ul><ul><li>Select & compose services </li></ul></ul><ul><ul><li>Select “best of breed” providers </li></ul></ul><ul><ul><li>Publish result as new services </li></ul></ul><ul><li>Decouple resource & service providers </li></ul>Function Resource Data Archives Analysis tools Discovery tools Users Fig: S. G. Djorgovski
  14. 14. Service-Oriented Systems: The Role of Grid Infrastructure <ul><li>Service-oriented Grid infrastructure </li></ul><ul><ul><li>Provision physical resources to support application workloads </li></ul></ul>Appln Service Appln Service Users Workflows Composition Invocation <ul><li>Service-oriented applications </li></ul><ul><ul><li>Wrap applications as services </li></ul></ul><ul><ul><li>Compose applications into workflows </li></ul></ul>“ The Many Faces of IT as Service”, ACM Queue, Foster, Tuecke, 2005 Provisioning
  15. 15. Forming & Operating Communities <ul><li>Define membership & roles; enforce laws & community standards </li></ul><ul><ul><li>I.e., policy for service-oriented architecture </li></ul></ul><ul><ul><li>Addressing dynamic membership & policy </li></ul></ul><ul><li>Build, buy, operate, & share infrastructure </li></ul><ul><ul><li>Decouple consumer & provider </li></ul></ul><ul><ul><li>For data, programs, services, computing, storage, instruments </li></ul></ul><ul><ul><li>Address dynamics of community demand </li></ul></ul>
  16. 16. Defining Community: Membership and Laws <ul><li>Identify VO participants and roles </li></ul><ul><ul><li>For people and services </li></ul></ul><ul><li>Specify and control actions of members </li></ul><ul><ul><li>Empower members  delegation </li></ul></ul><ul><ul><li>Enforce restrictions  federate policy </li></ul></ul>Access granted by community to user Site admission-control policies Effective Access Policy of site to community A 1 2 B 1 2 A B 1 10 1 10 1 16
  17. 17. Evolution of Grid Security & Policy <ul><li>1) Grid security infrastructure </li></ul><ul><ul><li>Public key authentication & delegation </li></ul></ul><ul><ul><li>Access control lists (“gridmap” files) </li></ul></ul><ul><ul><li> Limited set of policies can be expressed </li></ul></ul><ul><li>2) Utilities to simplify operational use, e.g. </li></ul><ul><ul><li>MyProxy: online credential repository </li></ul></ul><ul><ul><li>VOMS, ACL/gridmap management </li></ul></ul><ul><ul><li> Broader set of policies, but still ad-hoc </li></ul></ul><ul><li>3) General, standards-based framework for authorization & attribute management </li></ul>
  18. 18. Security Services for VO Policy <ul><li>Attribute Authority ( ATA ) </li></ul><ul><ul><li>Issue signed attribute assertions (incl. identity, delegation & mapping) </li></ul></ul><ul><li>Authorization Authority ( AZA ) </li></ul><ul><ul><li>Decisions based on assertions & policy </li></ul></ul>VO A Service VO ATA VO AZA Mapping ATA VO B Service VO User A Delegation Assertion User B can use Service A VO-A Attr  VO-B Attr VO User B Resource Admin Attribute VO Member Attribute VO Member Attribute
  19. 19. Trust in VOs <ul><li>Do I “believe” an attribute assertion? </li></ul><ul><ul><li>Used to evaluate cost vs. benefit of performing an operation </li></ul></ul><ul><ul><li>E.g., perform untrusted operation with extra auditing </li></ul></ul><ul><li>Look at attributes of assertion signer </li></ul><ul><li>Rooting trust </li></ul><ul><ul><li>Externally recognized source, e.g., CA </li></ul></ul><ul><ul><li>Dynamically via VO structure  delegation </li></ul></ul><ul><ul><li>Dynamically via alternative sources, e.g., reputation </li></ul></ul>
  20. 20. Retro… <ul><li>Dynamic communities </li></ul><ul><li>Users and Virtual Organizations </li></ul><ul><li>Security (Authentication, Authorization) </li></ul><ul><li>Trust, CA, Federation </li></ul><ul><li> </li></ul>
  21. 21. Build, buy, operate, & share infrastructure <ul><li>1) Integrate services from other sources </li></ul><ul><ul><li>Virtualize external services as VO services </li></ul></ul><ul><li>2) Coordinate & compose </li></ul><ul><ul><li>Create new services from existing ones </li></ul></ul>Community Services Provider Content Services Capacity Capacity Provider “ Service-Oriented Science”, Foster, 2005
  22. 22. Embedded Resource Management: E.g., EGEE & OSG VO User Cluster Resource Manager GRAM Cluster Resource Manager GRAM <ul><li>VO admin delegates credentials to be used by downstream VO services. </li></ul><ul><li>VO admin starts the required services. </li></ul><ul><li>VO jobs comes in directly from the upstream VO Users </li></ul><ul><li>VO job gets forwarded to the appropriate resource using the VO credentials </li></ul><ul><li>Computational job started for VO </li></ul>Client-side VO Scheduler Other Services VO Admin . . . Monitoring and control Headnode Resource Manager GRAM Deleg Deleg Deleg VO User VO Job VO Job
  23. 23. System-Level Science Problems too large &/or complex to tackle alone …
  24. 25. Business on Demand <ul><li>The Big Blue’s Vision for next generation computing </li></ul><ul><ul><li>Power architecture, Cell processor </li></ul></ul><ul><ul><li>Carbon Nanotubes </li></ul></ul><ul><ul><li>Services, Utilities, and Grids </li></ul></ul>
  25. 26. Case Study: IBM WS On-Demand
  26. 27. Oceano (1)
  27. 28. Oceano (2)
  28. 29. Retro… <ul><li>Virtualization </li></ul><ul><li>Decomposition </li></ul><ul><li>Integration </li></ul><ul><li>SLA </li></ul>
  29. 30. Assignments <ul><li>Programming Java Web Services </li></ul><ul><li>Writing a Report in the following topics: </li></ul><ul><ul><li>Resource Management </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Information Services </li></ul></ul><ul><ul><li>Data Management </li></ul></ul><ul><ul><li>OGSA and Web Services </li></ul></ul>
  30. 31. Discussions <ul><li>Questions? </li></ul><ul><li>More info @ </li></ul><ul><ul><li> </li></ul></ul>