1 / 38

Future Directions in Grid Computing

Future Directions in Grid Computing. Ian Foster Mathematics and Computer Science Division Argonne National Laboratory and Department of Computer Science The University of Chicago http://www.mcs.anl.gov/~foster. Invited Talk, Terena 2002 Conference, Limerick, June 5, 2002. The Grid Vision.

beck
Download Presentation

Future Directions in Grid Computing

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. Future Directionsin Grid Computing Ian Foster Mathematics and Computer Science Division Argonne National Laboratory and Department of Computer Science The University of Chicago http://www.mcs.anl.gov/~foster Invited Talk, Terena 2002 Conference, Limerick, June 5, 2002

  2. The Grid Vision “Resource sharing & coordinated problem solving in dynamic, multi-institutional virtual organizations” • On-demand, ubiquitous access to computing, data, and services • New capabilities constructed dynamically and transparently from distributed services “When the network is as fast as the computer's internal links, the machine disintegrates across the net into a set of special purpose appliances” (George Gilder)

  3. Why the Grid?(1) Evolution of the Scientific Process • Pre-electronic • Theorize &/or experiment, alone or in small teams; publish paper • Post-electronic • Construct and mine very large databases of observational or simulation data • Develop computer simulations & analyses • Access specialized devices remotely • Exchange information quasi-instantaneously within distributed multidisciplinary teams • Need to manage dynamic, distributed infrastructures, services, and applications

  4. eScience Application:Sloan Digital Sky Survey Analysis

  5. Galaxy cluster size distribution Chimera Virtual Data System + iVDGL Data Grid (many CPUs) eScience Application:Sloan Digital Sky Survey Analysis Size distribution of galaxy clusters?

  6. Challenging Technical Requirements • Dynamic formation and management of virtual organizations • Online negotiation of access to services: who, what, why, when, how • Configuration of applications and systems able to deliver multiple qualities of service • Autonomic management of distributed infrastructures, services, and applications • Management of distributed state as a fundamental issue

  7. State of the Art:Globus ToolkitTM (since 1996) • Small, standards-based set of protocols for distributed system management • Authentication, delegation; resource discovery; reliable invocation; etc. • Information-centric design • Data models; publication, discovery protocols • Open source implementation • Large international user community • Successful enabler of higher-level services and applications

  8. Grid Projects in eScience

  9. A Large Virtual Organization: CERN’s Large Hadron Collider 1800 Physicists, 150 Institutes, 32 Countries 100 PB of data by 2010; 50,000 CPUs?

  10. ~PBytes/sec ~100 MBytes/sec Offline Processor Farm ~20 TIPS There is a “bunch crossing” every 25 nsecs. There are 100 “triggers” per second Each triggered event is ~1 MByte in size ~100 MBytes/sec Online System Tier 0 CERN Computer Centre ~622 Mbits/sec or Air Freight (deprecated) Tier 1 FermiLab ~4 TIPS France Regional Centre Germany Regional Centre Italy Regional Centre ~622 Mbits/sec Tier 2 Tier2 Centre ~1 TIPS Tier2 Centre ~1 TIPS Caltech ~1 TIPS Tier2 Centre ~1 TIPS Tier2 Centre ~1 TIPS HPSS HPSS HPSS HPSS HPSS ~622 Mbits/sec Institute ~0.25TIPS Institute Institute Institute Physics data cache ~1 MBytes/sec 1 TIPS is approximately 25,000 SpecInt95 equivalents Physicists work on analysis “channels”. Each institute will have ~10 physicists working on one or more channels; data for these channels should be cached by the institute server Pentium II 300 MHz Pentium II 300 MHz Pentium II 300 MHz Pentium II 300 MHz Tier 4 Physicist workstations Data Grids for High Energy Physics

  11. Human Models Grids at NASA: Aviation Safety Wing Models • Lift Capabilities • Drag Capabilities • Responsiveness Stabilizer Models Airframe Models • Deflection capabilities • Responsiveness Crew Capabilities - accuracy - perception - stamina - re-action times - SOPs Engine Models • Braking performance • Steering capabilities • Traction • Dampening capabilities • Thrust performance • Reverse Thrust performance • Responsiveness • Fuel Consumption Landing Gear Models

  12. Life Sciences: Telemicroscopy DATA ACQUISITION PROCESSING,ANALYSIS ADVANCEDVISUALIZATION NETWORK COMPUTATIONALRESOURCES IMAGING INSTRUMENTS LARGE DATABASES

  13. Why the Grid:(2) And What About Business? • Fragmentation of enterprise infrastructure • Specialized platforms -> commodity servers • “Intelligence” embedded in networks • The rise of the “eUtility” (IBM, HP, …) • Outsourcing, economies of scale • Business-to-business computing • Especially complex virtual organizations • Ever more challenging QoS requirements • “Green-screen” -> “ubiquitious web presence”

  14. Today’s EnterpriseComputing Environment

  15. Butterfly.net: Grid for multi-player games Grids and Industry: Early Examples Entropia: Distributed computing (BMS, Novartis, …)

  16. The Business Opportunity • On-demand computing, storage, services • Significant savings due to reduced build-out, economies of scale, reduced admin costs • Greater flexibility => greater productivity • Entirely new applications and services • Based on high-speed resource integration • Solution to enterprise computing crisis • Render distributed infrastructures manageable

  17. Grid Computing

  18. Realizing the PromiseRequires Significant Innovation • Automation of infrastructure operation to achieve economies of scale • Management and component models for distributed service provisioning • New applications and tools powered by distributed services and resources • Business and service models to support specialization of function

  19. Grid Evolution:Open Grid Services Architecture • Refactor Globus protocol suite to enable common base and expose key capabilities • Service orientation to virtualize resources and unify resources/services/information • Embrace key Web services technologies for standard IDL, leverage commercial efforts • Result: standard interfaces & behaviors for distributed system management: the Grid service

  20. Open Grid Services Architecture:Transient Service Instances • “Web services” address discovery & invocation of persistent services • Interface to persistent state of entire enterprise • In Grids, must also support transient service instances, created/destroyed dynamically • Interfaces to the states of distributed activities • E.g. workflow, video conf., dist. data analysis • Significant implications for how services are managed, named, discovered, and used • In fact, much of OGSA (and Grid) is concerned with the management of service instances

  21. Open Grid Services Architecture • Defines fundamental (WSDL) interfaces and behaviors that define a Grid Service • Required + optional interfaces = WS “profile” • A unifying framework for interoperability & establishment of total system properties • Defines WSDL extensibility elements • E.g., serviceType (a group of portTypes) • Delivery via open source Globus Toolkit 3.0 • Leverage GT experience, code, community • And commercial implementations

  22. GridService (required) … other interfaces … (optional) Service data access Explicit destruction Soft-state lifetime Standard: - Notification - Authorization - Service creation - Service registry - Manageability - Concurrency + application-specific interfaces The Grid Service =Interfaces/Behaviors + Service Data Service data element Service data element Service data element Binding properties: - Reliable invocation - Authentication Implementation Hosting environment/runtime (“C”, J2EE, .NET, …)

  23. Service Data • A Grid service instance maintains a set of service data elements • XML fragments encapsulated in standard <name, type, TTL-info> containers • Includes basic introspection information, interface-specific data, and application data • FindServiceData operation (GridService interface) queries this information • Extensible query language support • See also notification interfaces • Allows notification of service existence and changes in service data

  24. Grid Service Example:Database Service • A DBaccess Grid service will support at least two portTypes • GridService • DBaccess • Each has service data • GridService: basic introspection information, lifetime, … • DBaccess: database type, query languages supported, current load, …, … • Maybe other portTypes as well • E.g., NotificationSource (SDE = subscribers) Grid Service DBaccess Name, lifetime, etc. DB info

  25. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service BioDB 1 Compute Service Provider User Application . . . . . . “I want to create a personal database containing data on e.coli metabolism” Database Service Database Factory BioDB n Storage Service Provider

  26. Example:Data Mining for Bioinformatics “Find me a data mining service, and somewhere to store data” Community Registry Mining Factory Database Service BioDB 1 Compute Service Provider User Application . . . . . . Database Service Database Factory BioDB n Storage Service Provider

  27. Example:Data Mining for Bioinformatics Community Registry Mining Factory GSHs for Mining and Database factories Database Service BioDB 1 Compute Service Provider User Application . . . . . . Database Service Database Factory BioDB n Storage Service Provider

  28. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service “Create a data mining service with initial lifetime 10” BioDB 1 Compute Service Provider User Application . . . . . . “Create a database with initial lifetime 1000” Database Service Database Factory BioDB n Storage Service Provider

  29. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service “Create a data mining service with initial lifetime 10” BioDB 1 Miner Compute Service Provider User Application . . . . . . “Create a database with initial lifetime 1000” Database Service Database Factory BioDB n Database Storage Service Provider

  30. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Query BioDB 1 Miner Compute Service Provider User Application . . . . . . Query Database Service Database Factory BioDB n Database Storage Service Provider

  31. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Query BioDB 1 Miner Keepalive Compute Service Provider User Application . . . . . . Query Database Service Database Factory Keepalive BioDB n Database Storage Service Provider

  32. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service BioDB 1 Miner Keepalive Compute Service Provider User Application . . . . . . Results Database Service Database Factory Keepalive Results BioDB n Database Storage Service Provider

  33. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service BioDB 1 Miner Compute Service Provider User Application . . . . . . Database Service Database Factory Keepalive BioDB n Database Storage Service Provider

  34. Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service BioDB 1 Compute Service Provider User Application . . . . . . Database Service Database Factory Keepalive BioDB n Database Storage Service Provider

  35. GT3: An Open Source OGSA-Compliant Globus Toolkit • GT3 Core • Implements Grid service interfaces & behaviors • Reference impln of evolving standard • Multiple hosting envs:Java/J2EE, C, C#/.NET? • GT3 Base Services • Evolution of current Globus Toolkit capabilities • Many other Grid services Other Grid GT3 Services Data Services GT3 Base Services GT3 Core

  36. Summary:Grids and Globus Toolkit • The Grid: Resource sharing & coordinated problem solving in dynamic, multi-institutional virtual organizations • Considerable impact within eScience, growing interest & adoption within eBusiness • Globus Toolkit an open source, defacto standard source of protocol and API definitions—and reference implementations • A strong community organization: the Global Grid Forum

  37. Summary:Open Grid Services Architecture • Open Grid Services Architecture represents (we hope!) next step in Grid evolution • Service orientation enables unified treatment of resources, data, and services • Standard interfaces and behaviors (the Grid service) for managing distributed state • Deeply integrated information model for representing and disseminating service data • Open source Globus Toolkit implementation (and commercial value adds)

  38. For More Information • Grid Book (somewhat old) • www.mkp.com/grids • Survey + research articles • www.mcs.anl.gov/~foster • The Globus Project™ • www.globus.org • GriPhyN project • www.griphyn.org • Global Grid Forum • www.gridforum.org • www.gridforum.org/ogsi-wg • Edinburgh, July 22-24 • Chicago, Oct 15-17

More Related