Introduction to Grid Computing and the Globus Toolkit™

1. Introduction toGrid Computingand the Globus Toolkit™ The Globus Project™USC Information Sciences Institute Argonne National Laboratory http://www.globus.org

2. Outline • Introduction to Grid Computing • Some Definitions • Grid Architecture Philosophy • The Globus Toolkit (GT2) • Introduction, Security, Resource Management, Information Services, Data Management • Open Grid Services Architecture (GT3) Lecture 1: Intro to Grids Computing and Globus Toolkit

3. The Grid Problem • Flexible, secure, coordinated resource sharing among dynamic collections of individuals, institutions, and resource From “The Anatomy of the Grid: Enabling Scalable Virtual Organizations” • Enable communities (“virtual organizations”) to share geographically distributed resources as they pursue common goals -- assuming the absence of… • central location, • central control, • omniscience, • existing trust relationships. Lecture 1: Intro to Grids Computing and Globus Toolkit

4. Elements of the Problem • Resource sharing • Computers, storage, sensors, networks, … • Sharing always conditional: issues of trust, policy, negotiation, payment, … • Coordinated problem solving • Beyond client-server: distributed data analysis, computation, collaboration, … • Dynamic, multi-institutional virtual orgs • Community overlays on classic org structures • Large or small, static or dynamic Lecture 1: Intro to Grids Computing and Globus Toolkit

5. Why Grids? • A biochemist exploits 10,000 computers to screen 100,000 compounds in an hour • 1,000 physicists worldwide pool resources for petaop analyses of petabytes of data • Civil engineers collaborate to design, execute, & analyze shake table experiments • Climate scientists visualize, annotate, & analyze terabyte simulation datasets • An emergency response team couples real time data, weather model, population data Lecture 1: Intro to Grids Computing and Globus Toolkit

6. Online Access to Scientific Instruments Advanced Photon Source wide-area dissemination desktop & VR clients with shared controls real-time collection archival storage tomographic reconstruction DOE X-ray grand challenge: ANL, USC/ISI, NIST, U.Chicago Lecture 1: Intro to Grids Computing and Globus Toolkit

7. ~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 Caltech ~1 TIPS Tier2 Centre ~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 forHigh Energy Physics Image courtesy Harvey Newman, Caltech Lecture 1: Intro to Grids Computing and Globus Toolkit

8. Mathematicians Solve NUG30 • Looking for the solution to the NUG30 quadratic assignment problem • An informal collaboration of mathematicians and computer scientists • Condor-G delivered 3.46E8 CPU seconds in 7 days (peak 1009 processors) in U.S. and Italy (8 sites) • 14,5,28,24,1,3,16,15, • 10,9,21,2,4,29,25,22, • 13,26,17,30,6,20,19, • 8,18,7,27,12,11,23 MetaNEOS: Argonne, Iowa, Northwestern, Wisconsin Lecture 1: Intro to Grids Computing and Globus Toolkit

9. Network for EarthquakeEngineering Simulation • NEESgrid: national infrastructure to couple earthquake engineers with experimental facilities, databases, computers, & each other • On-demand access to experiments, data streams, computing, archives, collaboration NEESgrid: Argonne, Michigan, NCSA, UIUC, USC Lecture 1: Intro to Grids Computing and Globus Toolkit

10. Home ComputersEvaluate AIDS Drugs • Community = • 1000s of home computer users • Philanthropic computing vendor (Entropia) • Research group (Scripps) • Common goal= advance AIDS research Lecture 1: Intro to Grids Computing and Globus Toolkit

11. Broader Context • “Grid Computing” has much in common with major industrial thrusts • Business-to-business, Peer-to-peer, Application Service Providers, Storage Service Providers, Distributed Computing, Internet Computing… • Sharing issues not adequately addressed by existing technologies • Complicated requirements: “run program X at site Y subject to community policy P, providing access to data at Z according to policy Q” • High performance: unique demands of advanced & high-performance systems Lecture 1: Intro to Grids Computing and Globus Toolkit

12. Why Now? • Moore’s law improvements in computing produce highly functional endsystems • The Internet and burgeoning wired and wireless provide universal connectivity • Changing modes of working and problem solving emphasize teamwork, computation • Network exponentials produce dramatic changes in geometry and geography Lecture 1: Intro to Grids Computing and Globus Toolkit

13. Network Exponentials • Network vs. computer performance • Computer speed doubles every 18 months • Network speed doubles every 9 months • Difference = order of magnitude per 5 years • 1986 to 2000 • Computers: x 500 • Networks: x 340,000 • 2001 to 2010 • Computers: x 60 • Networks: x 4000 Moore’s Law vs. storage improvements vs. optical improvements. Graph from Scientific American (Jan-2001) by Cleo Vilett, source Vined Khoslan, Kleiner, Caufield and Perkins. Lecture 1: Intro to Grids Computing and Globus Toolkit

14. The Globus Project™ • Close collaboration with real Grid projects in science and industry • Development and promotion of standard Grid protocols and interfaces to enable interoperability and shared infrastructure • The Globus Toolkit™: Open source, reference software base for building grid infrastructure and applications • GT2: • GT3: New implementation of toolkit based on grid services (which extend web services) • Global Grid Forum: Development of standard protocols and APIs for Grid computing Lecture 1: Intro to Grids Computing and Globus Toolkit

15. g g g Selected Major Grid Projects Lecture 1: Intro to Grids Computing and Globus Toolkit

16. g g g Selected Major Grid Projects Lecture 1: Intro to Grids Computing and Globus Toolkit

17. g g g g g Selected Major Grid Projects Lecture 1: Intro to Grids Computing and Globus Toolkit

18. g g Selected Major Grid Projects Lecture 1: Intro to Grids Computing and Globus Toolkit

19. The 13.6 TF TeraGrid:Computing at 40 Gb/s Site Resources Site Resources 26 HPSS HPSS 4 24 External Networks External Networks 8 5 Caltech Argonne External Networks External Networks NCSA/PACI 8 TF 240 TB SDSC 4.1 TF 225 TB Site Resources Site Resources HPSS UniTree TeraGrid/DTF: NCSA, SDSC, Caltech, Argonne www.teragrid.org Lecture 1: Intro to Grids Computing and Globus Toolkit

20. Tier0/1 facility Tier2 facility Tier3 facility 10 Gbps link 2.5 Gbps link 622 Mbps link Other link iVDGL:International Virtual Data Grid Laboratory U.S. PIs: Avery, Foster, Gardner, Newman, Szalay www.ivdgl.org Lecture 1: Intro to Grids Computing and Globus Toolkit

21. Some Definitions The Globus Project™ Argonne National LaboratoryUSC Information Sciences Institute http://www.globus.org

22. Some Important Definitions • Resource • Network protocol • Network enabled service • Application Programmer Interface (API) • Software Development Kit (SDK) • Syntax • Not discussed, but important: policies Lecture 1: Intro to Grids Computing and Globus Toolkit

23. Resource • An entity that is to be shared • E.g., computers, storage, data, software • Defined in terms of interfaces, not devices • E.g. scheduler such as LSF and PBS define a compute resource such as a cluster • E.g., Open/close/read/write define access to a distributed file system, e.g. NFS, AFS, DFS Lecture 1: Intro to Grids Computing and Globus Toolkit

24. Network Protocol • A formal description of message formats and a set of rules for message exchange • Rules may define sequence of message exchanges • Protocol may define state-change in endpoint, e.g., file system state change • Good protocols designed to do one thing • Protocols can be layered • Examples of protocols • IP, TCP, TLS (was SSL), HTTP, Kerberos Lecture 1: Intro to Grids Computing and Globus Toolkit

25. FTP Server Web Server HTTP Protocol FTP Protocol Telnet Protocol TLS Protocol TCP Protocol TCP Protocol IP Protocol IP Protocol Network Enabled Services • Implementation of a protocol that defines a set of capabilities • Protocol defines interaction with service • All services require protocols • Not all protocols are used to provide services (e.g. IP, TLS) • Examples: FTP and Web servers Lecture 1: Intro to Grids Computing and Globus Toolkit

26. Application Programming Interface • A specification for a set of routines to facilitate application development • Refers to definition, not implementation • E.g., there are many implementations of MPI • Spec often language-specific • Routine name, number, order and type of arguments; mapping to language constructs • Behavior or function of routine • Examples • GSS API (security), MPI (message passing) Lecture 1: Intro to Grids Computing and Globus Toolkit

27. Software Development Kit • A particular instantiation of an API • SDK consists of libraries and tools • Provides implementation of API specification • Can have multiple SDKs for an API • Examples of SDKs • MPICH, Motif Widgets Lecture 1: Intro to Grids Computing and Globus Toolkit

28. Syntax • Rules for encoding information, e.g. • XML, Condor ClassAds, Globus RSL • X.509 certificate format (RFC 2459) • Cryptographic Message Syntax (RFC 2630) • Distinct from protocols • One syntax may be used by many protocols (e.g., XML); & useful for other purposes • Syntaxes may be layered • E.g., Condor ClassAds -> XML -> ASCII • Important to understand layerings when comparing or evaluating syntaxes Lecture 1: Intro to Grids Computing and Globus Toolkit

29. A Protocol can have Multiple APIs • TCP/IP APIs include BSD sockets, Winsock, System V streams, … • The protocol provides interoperability: programs using different APIs can exchange information • I don’t need to know remote user’s API Application Application WinSock API Berkeley Sockets API TCP/IP Protocol: Reliable byte streams Lecture 1: Intro to Grids Computing and Globus Toolkit

30. Application Application MPI API MPI API LAM SDK MPICH-P4 SDK LAM protocol MPICH-P4 protocol Different message formats, exchange sequences, etc. TCP/IP TCP/IP An API can have Multiple Protocols • MPI provides portability: any correct program compiles & runs on a platform • Does not provide interoperability: all processes must link against same SDK • E.g., MPICH and LAM versions of MPI Lecture 1: Intro to Grids Computing and Globus Toolkit

31. APIs and Protocols are Both Important • Standard APIs/SDKs are important • They enable application portability • But w/o standard protocols, interoperability is hard (every SDK speaks every protocol?) • Standard protocols are important • Enable cross-site interoperability • Enable shared infrastructure • But w/o standard APIs/SDKs, application portability is hard (different platforms access protocols in different ways) Lecture 1: Intro to Grids Computing and Globus Toolkit

32. Grid Architecture The Globus Project™ Argonne National LaboratoryUSC Information Sciences Institute http://www.globus.org

33. The Systems Problem:Resource Sharing Mechanisms That … • Address security and policy concerns of resource owners and users • Are flexible enough to deal with many resource types and sharing modalities • Scale to large number of resources, many participants, many program components • Operate efficiently when dealing with large amounts of data & computation Lecture 1: Intro to Grids Computing and Globus Toolkit

34. Aspects of the Systems Problem • Need for interoperability when different groups want to share resources • Diverse components, policies, mechanisms • E.g., standard notions of identity, means of communication, resource descriptions • Need for shared infrastructure services to avoid repeated development, installation • E.g., one port/service/protocol for remote access to computing, not one per tool/appln • E.g., Certificate Authorities: expensive to run • A common need for protocols & services Lecture 1: Intro to Grids Computing and Globus Toolkit

35. Hence, a Protocol-Oriented View of Grid Architecture that emphasises … • Development of Grid protocols & services • Protocol-mediated access to remote resources • New services: e.g., resource brokering • “On the Grid” = speak Intergrid protocols • Mostly (extensions to) existing protocols • Development of Grid APIs & SDKs • Interfaces to Grid protocols & services • Facilitate application development by supplying higher-level abstractions • The (hugely successful) model is the Internet Lecture 1: Intro to Grids Computing and Globus Toolkit

36. Application Application Internet Protocol Architecture “Coordinating multiple resources”: ubiquitous infrastructure services, app-specific distributed services Collective “Sharing single resources”: negotiating access, controlling use Resource “Talking to things”: communication (Internet protocols) & security Connectivity Transport Internet “Controlling things locally”: Access to, & control of, resources Fabric Link Layered Grid Architecture(By Analogy to Internet Architecture) Lecture 1: Intro to Grids Computing and Globus Toolkit

37. Protocols, Services,and APIs Occur at Each Level Applications Languages/Frameworks Collective Service APIs and SDKs Collective Service Protocols Collective Services Resource APIs and SDKs Resource Service Protocols Resource Services Connectivity APIs Connectivity Protocols Local Access APIs and Protocols Fabric Layer Lecture 1: Intro to Grids Computing and Globus Toolkit

38. Important Points • Built on Internet protocols & services • Communication, routing, name resolution, etc. • “Layering” here is conceptual, does not imply constraints on who can call what • Protocols/services/APIs/SDKs will, ideally, be largely self-contained • Some things are fundamental: e.g., communication and security • But, advantageous for higher-level functions to use common lower-level functions Lecture 1: Intro to Grids Computing and Globus Toolkit

39. The Hourglass Model • Focus on architecture issues • Propose set of core services as basic infrastructure • Use to construct high-level, domain-specific solutions • Design principles • Keep participation cost low • Enable local control • Support for adaptation • “IP hourglass” model A p p l i c a t i o n s Diverse global services Core services Local OS Lecture 1: Intro to Grids Computing and Globus Toolkit

40. Connectivity LayerProtocols & Services • Communication • Internet protocols: IP, DNS, routing, etc. • Security: Grid Security Infrastructure (GSI) • Uniform authentication, authorization, and message protection mechanisms in multi-institutional setting • Single sign-on, delegation, identity mapping • Public key technology, SSL, X.509, GSS-API • Supporting infrastructure: Certificate Authorities, certificate & key management, … GSI: www.gridforum.org/security Lecture 1: Intro to Grids Computing and Globus Toolkit

41. Resource LayerProtocols & Services • Grid Resource Allocation Mgmt (GRAM) • Remote allocation, reservation, monitoring, control of compute resources • GridFTP protocol (FTP extensions) • High-performance data access & transport • Grid Resource Information Service (GRIS) • Access to structure & state information • Network reservation, monitoring, control • All built on connectivity layer: GSI & IP GridFTP: www.gridforum.org GRAM, GRIS: www.globus.org Lecture 1: Intro to Grids Computing and Globus Toolkit

42. Collective LayerProtocols & Services • Index servers (e.g. Monitoring and Discovery Service) • Custom views on dynamic resource collections assembled by a community • Resource brokers (e.g., Condor Matchmaker) • Resource discovery and allocation • Replica Location and Management Services • Metadata Services • Co-reservation and co-allocation services • Workflow management services • Etc. Condor: www.cs.wisc.edu/condor Lecture 1: Intro to Grids Computing and Globus Toolkit

43. API SDK C-point Protocol Checkpoint Repository API SDK Access Protocol Compute Resource Example:High-ThroughputComputing System App High Throughput Computing System Collective (App) Dynamic checkpoint, job management, failover, staging Collective (Generic) Brokering, certificate authorities Access to data, access to computers, access to network performance data Resource Communication, service discovery (DNS), authentication, authorization, delegation Connect Storage systems, schedulers Fabric Lecture 1: Intro to Grids Computing and Globus Toolkit

44. Example: Grid Servicesfor Data-Intensive Applications App Discipline-Specific Data Grid Application Collective (App) Coherency control, replica selection, task management, virtual data catalog, virtual data code catalog, … Collective (Generic) Replica catalog, replica management, co-allocation, certificate authorities, metadata catalogs, Access to data, access to computers, access to network performance data, … Resource Communication, service discovery (DNS), authentication, authorization, delegation Connect Storage systems, clusters, networks, network caches, … Fabric Lecture 1: Intro to Grids Computing and Globus Toolkit

45. The Globus Toolkit™ Version 2:Introduction

46. Globus Toolkit™ Version 2 • A software toolkit addressing key technical problems in the development of Grid enabled tools, services, and applications • Offer a modular “bag of technologies” • Enable incremental development of grid-enabled tools and applications • Implement standard Grid protocols and APIs • Make available under liberal open source license Lecture 1: Intro to Grids Computing and Globus Toolkit

47. Four Main Components • Security • Information Management • Resource Management • Data Management Lecture 1: Intro to Grids Computing and Globus Toolkit

48. General Approach • Define Grid protocols & APIs • Protocol-mediated access to remote resources • Integrate and extend existing standards • “On the Grid” = speak “Intergrid” protocols • Develop a reference implementation • Open source Globus Toolkit • Client and server SDKs, services, tools, etc. • Grid-enable wide variety of tools • Globus Toolkit, FTP, SSH, Condor, SRB, MPI, … • Learn through deployment and applications Lecture 1: Intro to Grids Computing and Globus Toolkit

49. Four Key Protocols • The Globus Toolkit™ Version 2 centers around four key protocols • Connectivity layer: • Security: Grid Security Infrastructure (GSI) • Resource layer: • Resource Management: Grid Resource Allocation Management (GRAM) • Information Services: Grid Resource Information Protocol (GRIP) • Data Transfer: Grid File Transfer Protocol (GridFTP) Lecture 1: Intro to Grids Computing and Globus Toolkit

50. The Globus Toolkit™ Version 2:Security Services