1. An Overview of the Globus Toolkit and the Open Grid Services Architecture Mike Wilde Mathematics and Computer Science Division Argonne National Laboratory LISHEP 2004 – UERJ, Rio De Janeiro – Feb 2004

2. Grids – What & Why?

3. LISHEP2004/UERJ 3 www.griphyn.org What is a Grid? l Three key criteria –Coordinates distributed resources … –using standard, open, general-purpose protocols and interfaces … –to deliver non-trivial qualities of service. l What is not a Grid? –A cluster, a network attached storage device, a scientific instrument, a network, etc. –Each may be an important component of a Grid, but by itself does not constitute a Grid

4. LISHEP2004/UERJ 4 www.griphyn.org The Grid “ Resource sharing & coordinated problem solving in dynamic … virtual organizations” 1. Enable integration of distributed service & resources 2. Using general-purpose protocols & infrastructure 3. To achieve useful qualities of service “The Anatomy of the Grid”, Foster, Kesselman, Tuecke, 2001

5. LISHEP2004/UERJ 5 www.griphyn.org Authenticate once Submit a grid computation (code, resources, data,…) Locate resources Negotiate authorization, acceptable use, etc. Select and acquire resources Initiate data transfers, computation Monitor progress Steer computation Store and distribute results Account for usage Grid Applications

6. LISHEP2004/UERJ 6 www.griphyn.org Grid Communities & Applications: Data Grids for High Energy Physics Tier2 Centre ~1 TIPS Online System Offline Processor Farm ~20 TIPS CERN Computer Centre FermiLab ~4 TIPS France Regional Centre Italy Regional Centre Germany Regional Centre Institute Institute ~0.25TIPS Physicist workstations ~100 MBytes/sec ~622 Mbits/sec ~1 MBytes/sec There is a “bunch crossing” every 25 nsecs. There are 100 “triggers” per second Each triggered event is ~1 MByte in size 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 Physics data cache ~PBytes/sec ~622 Mbits/sec or Air Freight (deprecated) Tier2 Centre ~1 TIPS Caltech ~1 TIPS ~622 Mbits/sec Tier 0 Tier 1 Tier 2 Tier 4 1 TIPS is approximately 25,000 SpecInt95 equivalents Image courtesy Harvey Newman, Caltech

7. LISHEP2004/UERJ 7 www.griphyn.org Grid2003: Towards a Persistent U.S. Open Science Grid Status on 11/19/03 (http://www.ivdgl.org/grid2003) P

8. LISHEP2004/UERJ 8 www.griphyn.org Examples of Production Grid Deployments “Persistent deployment of Grid services in support of a diverse user community” l Grid3/iVDGL (US) –22 sites, O(3000) CPUs, 2 countries l LHC Computing Grid –25 sites, international –High energy physics l NorduGrid –24 clusters, 724 CPUs, 6 countries; physics l NASA IPG –4 sites, O(3000) CPUs –Aeronautics l NEESgrid (prod. 2004) –Instruments, data, compute, collaborative –Earthquake eng. l TeraGrid(prod. Jan 04) –5 sites, expanding W P P P P P P re-WS Web Services

9. LISHEP2004/UERJ 9 www.griphyn.org Resource Integration as a Fundamental Challenge R Discovery Many sources of data, services, computation R Registries organize services of interest to a community Access Data integration activities may require access to, & exploration/analysis of, data at many locations Exploration & analysis may involve complex, multi-step workflows RM Resource management is needed to ensure progress & arbitrate competing demands Security service Security service Policy service Policy service Security & policy must underlie access & management decisions

10. Globus Toolkit 2.4

11. Grid Security Infrastructure - Secure Communcation

12. LISHEP2004/UERJ 12 www.griphyn.org Certificates l By checking the signature, one can determine that a public key belongs to a given user. Name Issuer Public Key Signature Hash =? Decrypt Public Key from Issuer

13. LISHEP2004/UERJ 13 www.griphyn.org Grid Security Infrastructure (GSI) l GSI is: PKI (CAs and Certificates) SSL/ TLS Proxies and Delegation PKI for credentials SSL for Authentication And message protection Proxies and delegation (GSI Extensions) for secure single Sign-on

14. LISHEP2004/UERJ 14 www.griphyn.org Site A (Kerberos) Site B (Unix) Site C (Kerberos) Computer User Single sign-on via “grid-id” & generation of proxy cred. Or: retrieval of proxy cred. from online repository User Proxy Proxy credential Computer Storage system Communication* GSI-enabled FTP server Authorize Map to local id Access file Remote file access request* GSI-enabled GRAM server GSI-enabled GRAM server Remote process creation requests* * With mutual authentication Process Kerberos ticket Restricted proxy Process Restricted proxy Local id Authorize Map to local id Create process Generate credentials Ditto GSI in Action: “Processes at A and B Communicate & Access Files at C”

15. Resource discovery and status information

16. LISHEP2004/UERJ 16 www.griphyn.org The Grid Information Problem l Large numbers of distributed “sensors” with different properties l Need for different “views” of this information, depending on community membership, security constraints, intended purpose, sensor type

17. LISHEP2004/UERJ 17 www.griphyn.org Globus Toolkit Solution: MDS-2 Registration & enquiry protocols, information models, query languages –Provides standard interfaces to sensors –Supports different “directory” structures supporting various discovery/access strategies Karl Czajkowski, Steve Fitzgerald, others

18. LISHEP2004/UERJ 18 www.griphyn.org MDS-2 Components l Grid Information Service (GRIS) –Provides resource description –Modular content gateway l Grid Index Information Service (GIIS) –Provides aggregate directory –Hierarchical groups of resources l Lightweight Dir. Access Protocol (LDAP) –Standard with many client implementations –Used for GRIP (and GRRP currently)

19. LISHEP2004/UERJ 19 www.griphyn.org GRIS Host Objects OS

20. LISHEP2004/UERJ 20 www.griphyn.org MDS Architecture l Resources run a standard information service (GRIS) which speaks LDAP and provides information about the resource (no searching). l GIIS provides a “caching” service much like a web search engine. Resources register with GIIS and GIIS pulls information from them when requested by a client and the cache has expired. l GIIS provides the collective-level indexing/searching function. GIIS Cache contains info from A and B Resource A GRIS GIIS requests information from GRIS services as needed. Client 1 Client 2 Client 3 Resource B GRIS Clients 1 and 2 request info directly from resources. Client 3 uses GIIS for searching collective information.

21. Resource Management and Job Execution: GRAM, Condor-G

22. LISHEP2004/UERJ 22 www.griphyn.org GRAM Components Globus Security Infrastructure Job Manager GRAM client API calls to request resource allocation and process creation. MDS client API calls to locate resources Query current status of resource Create RSL Library Parse Request Allocate & create processes Process Monitor & control Site boundary ClientMDS: Grid Index Info Server Gatekeeper MDS: Grid Resource Info Server Local Resource Manager MDS client API calls to get resource info GRAM client API state change callbacks

23. LISHEP2004/UERJ 23 www.griphyn.org Resource Management Review l Resource Specification Language (RSL) is used to communicate requirements l The Globus Resource Allocation and Management (GRAM) API allows programs to be started on remote resources, despite local heterogeneity l A layered architecture allows application- specific resource brokers and co-allocators (e.g. DUROC) to be defined in terms of GRAM services

24. LISHEP2004/UERJ 24 www.griphyn.org Condor-G: Job Submission Client l Use Condor to run jobs on the Grid l Uses Globus Toolkit –GRAM (submit a remote job) –GASS (transfer job’s files) l Run a job on a Grid resource l Features –Job management –Fault tolerance –Credential management

25. LISHEP2004/UERJ 25 www.griphyn.org How It Works Schedd JobManager LSF Condor-GGrid Resource GridManager 600 Globus jobs

26. Data Management – GridFTP, Replica Location Service

27. LISHEP2004/UERJ 27 www.griphyn.org GridFTP l Data-intensive grid applications need to transfer and replciate large data sets –Terabytes to petabytes –between any two sites in the Grid l GridFTP Features: –Uses Grid security –Third party (client mediated) transfer –Parallel transfers –Striped transfers –TCP buffer optimizations

28. LISHEP2004/UERJ 28 www.griphyn.org Command line tool: globus-url-copy l This is the GridFTP client tool provided with the Globus Toolkit l It takes a source URL and destination URL and will do protocol conversion for http, https, FTP, gsiftp, and file (file must be local). l globus-url-copy sourceURL destURL l globus-url-copy gsiftp://sourceHostName:port/dir1/dir2/file17 gsiftp://destHostName:port/dirX/dirY/fileA

29. LISHEP2004/UERJ 29 www.griphyn.org Striped GridFTP Server Parallel File System (e.g. PVFS, PFS, etc.) MPI-IO … Plug-in Control GridFTP Server Parallel Backend GridFTP server master mpirun GridFTP client Plug-in Control Plug-in Control Plug-in Control … MPI (Comm_World) MPI (Sub-Comm) To Client or Another Striped GridFTP Server Control socket GridFTP Control ChannelGridFTP Data Channels

30. LISHEP2004/UERJ 30 www.griphyn.org GridFTP Development For GT3 l Major redesign planned l Part 1: Replace existing globus_io libraries with XIO libraries (under development) –Pluggable protocol stack –TCP, reliable UDP, HTTP, GSI l Part 2: GridFTP OGSA Service (?) –Based on redesign of GRAM job submission, service level agreements –Data transfer is just another type of job to be executed

31. RLS

32. LISHEP2004/UERJ 32 www.griphyn.org Replica Management in Grids l Data intensive applications – Produce Terabytes or Petabytes of data l Replicate data at multiple locations –Fault tolerance –Performance: avoid wide area data transfer latencies, achieve load balancing l Issues: –Locating replicas of desired files –Creating new replicas –Scalability –Reliability

33. LISHEP2004/UERJ 33 www.griphyn.org A Replica Location Service l A Replica Location Service (RLS) is a distributed registry service that records the locations of data copies and allows discovery of replicas l Maintains mappings between logical identifiers and target names –Physical targets: Map to exact locations of replicated data –Logical targets: Map to another layer of logical names, allowing storage systems to move data without informing the RLS l RLS was designed and implemented in a collaboration between the Globus project and the DataGrid project

34. LISHEP2004/UERJ 34 www.griphyn.org LRC RLI LRC Replica Location Indexes Local Replica Catalogs LRCs contain consistent information about logical-to- target mappings on a site RLIs nodes aggregate information about LRCs Soft state updates from LRCs to RLIs: relaxed consistency of index information, used to rebuild index after failures Arbitrary levels of RLI hierarchy

35. OGSA – the Evolution of Grid Architecture

36. LISHEP2004/UERJ 36 www.griphyn.org Overview l Grid background l Open Grid Services Architecture l Open Grid Services Infrastructure l Beyond OGSI: other OGSA services l Globus Toolkit v3 implementation l Early GT3 performance results l Scientific and commercial perspectives l Summary

37. LISHEP2004/UERJ 37 www.griphyn.org Why Open Standards Matter l Ubiquitous adoption demands open, standard protocols –Standard protocols enable interoperability –Avoid product/vendor lock-in –Enables innovation/competition on end points l Further aided by open, standard APIs –Standard APIs enable portability –Allow implementations to port to different vendor platforms l Internet and Web as exemplars

38. LISHEP2004/UERJ 38 www.griphyn.org Increased functionality, standardization Custom solutions 1990199520002005 Open Grid Services Arch Real standards Multiple implementations Web services, etc. Managed shared virtual systems Computer science research Globus Toolkit Defacto standard Single implementation Internet standards The Emergence of Open Grid Standards 2010

39. LISHEP2004/UERJ 39 www.griphyn.org Open Grid Services Architecture l Service orientation to virtualize resources –Everything is a service l From Web services –Standard interface definition mechanisms –Evolving set of other standards: security, etc. l From Grids (Globus Toolkit) –Service semantics, reliability & security models –Lifecycle management, discovery, other services è A framework for the definition & management of composable, interoperable services “The Physiology of the Grid: An Open Grid Services Architecture for Distributed Systems Integration”, Foster, Kesselman, Nick, Tuecke, 2002

40. LISHEP2004/UERJ 40 www.griphyn.org Globus Toolkit: A Story of Evolution l Definition of Grid problem has been stable since original Globus Project proposal in 1995 –Though we’ve gotten better at articulating it l But our approach to its solution has evolved: –From APIs and custom protocols… –to standard protocols… –to Grid services (OGSA) l Driven by experience implementing and deploying the Globus Toolkit, and building real applications with it

41. LISHEP2004/UERJ 41 www.griphyn.org Globus Toolkit ® v3.0 l All of the GT v2.4 services and clients l Complete Java implementation of OGSI v1.0 –Rich, container-based implementation –Built on Apache Axis l Globus “proprietary” services built on OGSI –Managed Jobs (akin to GT2 GRAM) –Reliable File Transfer (RFT) –Index Services (akin to GT2 GIIS) l Some services not yet OGSI-fied: –GridFTP, Replica Location Services (RLS)

42. LISHEP2004/UERJ 42 www.griphyn.org GT2 Components RLS GT-OGSA Grid Service Infrastructure The focus of this presentation GT3 Distribution

43. LISHEP2004/UERJ 43 www.griphyn.org Web Services l XML-based distributed computing technology l Web service = a server process that exposes typed ports to the network l Described by the Web Services Description Language, an XML document that contains –Type of message(s) the service understands & types of responses & exceptions it returns –“Methods” bound together as “port types” –Port types bound to protocols as “ports” l A WSDL document completely defines a service and how to access it

44. LISHEP2004/UERJ 44 www.griphyn.org WSDL Example

45. LISHEP2004/UERJ 45 www.griphyn.org Web Services: Mode of Operation l Definition in a Meta-language –CORBA: Interface Definition Language (IDL) –WS: Web Services Definition Language (WSDL) l Stubs: –Serialize/deserialize or marshal/unmarshal –Implement interaction based on a protocol such as IIOP or SOAP Meta-language definition of a procedure, object or service server’s stub (skeleton) server’s implementation client’s stub (proxy) client’s implementation interaction

46. LISHEP2004/UERJ 46 www.griphyn.org WSDL Document Structure l WSDL: Web Services Definition Language l Document structure: –Service Description –Implemenation Details l Service Description –Elements >PortType (~ class) >Operations (~ method) >Messages, message parts (~ parameters) >Types (type definitions) –Used for >Generating stubs and skeletons >Service discovery

47. LISHEP2004/UERJ 47 www.griphyn.org WSDL Document Structure (cntd) l Implementation Details –Binding >Messaging protocol (eg. SOAP) >Message Interpretation (eg. RPC or literal) >Data-encoding model (eg. SOAP or literal encoding) >Transport protocol (eg. HTTP or FTP) –Port: describes service endpoint –Service Element: groups Port elements together l Others: –Definition: root element of a SOAP document

48. LISHEP2004/UERJ 48 www.griphyn.org Database: Service Description <schema targetNamespace="http://samples.ogsa.globus.org/database/database.xsd" xmlns="http://www.w3.org/2001/XMLSchema"> “class” “method” “parameter” “parameter” type

49. LISHEP2004/UERJ 49 www.griphyn.org Database: Implementation <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://samples.ogsa.globus.org/database"/> <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://samples.ogsa.globus.org/database"/> use SOAP encoding the service is located here use http for transport interpret as RPC call use SOAP

50. LISHEP2004/UERJ 50 www.griphyn.org Transient Service Instances l “Web services” address discovery & invocation of persistent services –Interface to persistent state of entire enterprise l In Grids, must also support transient services, created/destroyed dynamically –Interfaces to the states of distributed activities –E.g. workflow, video conf., dist. data analysis l Significant implications for how services are managed, named, discovered, and used –In fact, much of our work is concerned with the management of services

51. LISHEP2004/UERJ 51 www.griphyn.org OGSA Structure l A standard substrate: the Grid service –Standard interfaces and behaviors that address key distributed system issues: naming, service state, lifetime, notification –A Grid service is a Web service l … supports standard service specifications –Agreement, data access & integration, workflow, security, policy, diagnostics, etc. –Target of current & planned GGF efforts l … and arbitrary application-specific services based on these & other definitions

52. LISHEP2004/UERJ 52 www.griphyn.org Overview l Grid background l Open Grid Services Architecture l Open Grid Services Infrastructure l Beyond OGSI: other OGSA services l Globus Toolkit v3 implementation l Early GT3 performance results l Scientific and commercial perspectives l Summary

53. LISHEP2004/UERJ 53 www.griphyn.org OGSI Specification l Defines WSDL conventions and extensions –For describing and naming services –Working with W3C WSDL working group to drive OGSI extensions into WSDL 1.2 l Defines fundamental interfaces (using extended WSDL) and behaviors that define a Grid Service –A unifying framework for interoperability & establishment of total system properties l http://www.ggf.org/ogsi-wg

54. LISHEP2004/UERJ 54 www.griphyn.org Fundamental Interfaces & Behaviors l OGSI defines basic patterns of interaction, which can be combined with each other and with custom patterns in a myriad of ways l OGSI Specification focuses on: –Atomic, composable patterns in the form of portTypes/interfaces >Define operations & associated service data elements –A model for how these are composed >Compatible with WSDL 1.2 l Complete service descriptions are left to other groups that are defining real services

55. LISHEP2004/UERJ 55 www.griphyn.org OGSI: Standard Web Services Interfaces & Behaviors l Naming and bindings (basis for virtualization) –Every service instance has a unique name, from which can discover supported bindings l Lifecycle (basis for fault resilient state management) –Service instances created by factories –Destroyed explicitly or via soft state l Information model (basis for monitoring & discovery) –Service data (attributes) associated with GS instances –Operations for querying and setting this info –Asynchronous notification of changes to service date l Service Groups (basis for registries & collective svcs) –Group membership rules & membership management l Base Fault type

56. LISHEP2004/UERJ 56 www.griphyn.org OGSI Service Data l Attributes: Publicly visible state of the service l Want to bring full power of XML to attributes –getXXX/setXXX is too limiting >How to get/set multiple? >Want richer queries across attributes (e.g., join) –Use XML Schema, XPath, XQuery, XSLT, etc. –OGSI service data: >Attributes defined using XML Schema >Attributes combined into a single (logical) document within the service >Rich pull/push/set operations against service data document l Should declare attributes in WSDL interface

57. LISHEP2004/UERJ 57 www.griphyn.org Open Grid Services Infrastructure Implementation Service data element Other standard interfaces: factory, notification, collections Hosting environment/runtime (“C”, J2EE,.NET, …) Service data element Service data element GridService (required) Data access Lifetime management Explicit destruction Soft-state lifetime Introspection: What port types? What policy? What state? Client Grid Service Handle Grid Service Reference handle resolution

58. LISHEP2004/UERJ 58 www.griphyn.org Service registry Service requestor (e.g. user application) Service factory Create Service Grid Service Handle Resource allocation Service instances Register Service Service discovery Interactions standardized using WSDL Service data Keep-alives Notifications Service invocation Authentication & authorization are applied to all requests Open Grid Services Infrastructure (OGSI)

59. LISHEP2004/UERJ 59 www.griphyn.org GT-OGSA Grid Service Infrastructure Security Infrastructure System-Level Services Base Services User-Defined Services Grid Service Container Hosting Environment Web Service Engine OGSI Spec Implementation

60. LISHEP2004/UERJ 60 www.griphyn.org OGSI Implementation l GT3 includes a set of primitives that fully implement the interfaces and behaviors defined in the OGSI Specification –Defines how entities can create, discover and interact with a Grid service l The OGSI Specification defines a protocol: GT3 provides a programming model for that protocol

61. LISHEP2004/UERJ 61 www.griphyn.org Implementation of the GridService portType: GridServiceImpl and PersistentGridServiceImpl l destroy() l setServiceData() l findServiceData() l requestTerminationAfter() l requestTerminationBefore() l addOperationProvider() (See docs for complete set of methods) Implementation of the OGSI Spec ”> Additional functionality can be added to a Grid Service using OperationProviders Deployment descriptor

62. LISHEP2004/UERJ 62 www.griphyn.org Building an OGSI-Compliant Grid Service using GT3 Write service-specific logic that also implements the GT3 OperationProvider interface

63. LISHEP2004/UERJ 63 www.griphyn.org Write service-specific logic that also implements the GT3 OperationProvider interface Combine with one of the two GT3 implementations of base GridService functionality: GridServiceImpl or PersistentGridServiceImpl Building an OGSI-Compliant Grid Service using GT3

64. LISHEP2004/UERJ 64 www.griphyn.org Write service-specific logic that also implements the GT3 OperationProvider interface Combine with one of the two GT3 implementations of base GridService functionality: GridServiceImpl or PersistentGridServiceImpl An OGSI-Compliant grid service Building an OGSI-Compliant Grid Service using GT3

65. LISHEP2004/UERJ 65 www.griphyn.org An OGSI-Compliant grid service OperationProviders are configured at deployment time or added at runtime Write service-specific logic that also implements the GT3 OperationProvider interface Combine with one of the two GT3 implementations of base GridService functionality: GridServiceImpl or PersistentGridServiceImpl Building an OGSI-Compliant Grid Service using GT3

66. LISHEP2004/UERJ 66 www.griphyn.org A Grid Service Can be Composed of Multiple OperationProviders l OPs can be designed as atomic bits of functionality to facilitate reuse l OP approach eases the task of bringing legacy code into OGSI-compliance l OPs allow Grid Services to be formed dynamically (in contrast to the inheritance approach)

67. LISHEP2004/UERJ 67 www.griphyn.org Several OperationProviders are Included in the GT3 Distribution NotificationSourceProvider HandleResolverProvider ServiceGroupRegistrationProvider ServiceGroupProvider FactoryProvider

68. LISHEP2004/UERJ 68 www.griphyn.org GWSDL l OGSI requires interface extension/composition l We worked within W3C WSDL working group to define standard interface extension in WSDL 1.2 that meets OGSI requirements l But could not wait for WSDL 1.2 l So defined gwsdl:portType that extends WSDL 1.1 portType with: –WSDL 1.2 portType extension –WSDL 1.2 open content model l Define GWSDL  WSDL 1.1 & 1.2 mappings

69. LISHEP2004/UERJ 69 www.griphyn.org GWSDL Example … … …

70. LISHEP2004/UERJ 70 www.griphyn.org MMJFS Resource Management l GRAM Architecture rendered in OGSA l The MMJFS runs as an unprivileged user, with a small highly-constrained setuid executable behind it l Individual user environments are created using virtual hosting MJS User 1 User 2 User 3 Master User MJS MMJFS: Master Managed Job Factory Service MJS: Managed Job Service User Hosting Environment

71. LISHEP2004/UERJ 71 www.griphyn.org Client GRAM Job Submission Scenario Index Service 1. From an index service, the client chooses an MMJFS

72. LISHEP2004/UERJ 72 www.griphyn.org Client GRAM Job Submission Scenario Index Service 2. The client calls the createService operation on the factory and supplies RSL MMJFS 1. From an index service, the client chooses an MMJFS

73. LISHEP2004/UERJ 73 www.griphyn.org Client GRAM Job Submission Scenario Index Service MMJFS MJS 3. The factory creates a Managed Job Service 1. From an index service, the client chooses an MMJFS 2. The client calls the createService operation on the factory and supplies RSL

74. LISHEP2004/UERJ 74 www.griphyn.org Client GRAM Job Submission Scenario Index Service MMJFS MJS 4. The factory returns a locator 1. From an index service, the client chooses an MMJFS 2. The client calls the createService operation on the factory and supplies RSL 3. The factory creates a Managed Job Service

75. LISHEP2004/UERJ 75 www.griphyn.org Client GRAM Job Submission Scenario Index Service MMJFS MJS 5. The client subscribes to the MJS’ status SDE and retrieves output 1. From an index service, the client chooses an MMJFS 2. The client calls the createService operation on the factory and supplies RSL 3. The factory creates a Managed Job Service 4. The factory returns a locator

76. LISHEP2004/UERJ 76 www.griphyn.org Information Services l Index service as caching aggregator –Caches service data from other Grid services l Index service as provider framework –Serves as a host for service data providers that live outside of a Grid service to publish data

77. LISHEP2004/UERJ 77 www.griphyn.org Reliable File Transfer l OGSI-compliant service exposing GridFTP control channel functionality –3rd-party transfer between GridFTP servers l Recoverable Grid service –Automatically restarts interrupted transfers from the last checkpoint l Progress and restart monitoring GridFTP Server 1 GridFTP Server 2 RFT JDBC

78. LISHEP2004/UERJ 78 www.griphyn.org Example: Reliable File Transfer Service Performance Policy Faults service data elements Pending File Transfer Internal State Grid Service Notf’n Source Policy interfaces Query &/or subscribe to service data Fault Monitor Perf. Monitor Client Request and manage file transfer operations Data transfer operations

79. LISHEP2004/UERJ 79 www.griphyn.org OGSI Implementations l Globus Toolkit version 3.0 (Java, C client) l U Virginia OGSI.NET (.NET) l LBNL pyGlobus (Python) l U Edinburgh (.NET) l U Manchester (PERL) l Fujitsu Unicore (Java)

80. LISHEP2004/UERJ 80 www.griphyn.org Overview l Grid background l Open Grid Services Architecture l Open Grid Services Infrastructure l Beyond OGSI: other OGSA services l Globus Toolkit v3 implementation l Early GT3 performance results l Scientific and commercial perspectives l Summary

81. LISHEP2004/UERJ 81 www.griphyn.org Web Services: Basic Functionality OGSA Open Grid Services Architecture OGSI: Interface to Grid Infrastructure Applications in Problem Domain X Compute, Data & Storage Resources Distributed Application & Integration Technology for Problem Domain X Users in Problem Domain X Virtual Integration Architecture Generic Virtual Service Access and Integration Layer - Structured Data Integration Structured Data Access Structured Data RelationalXMLSemi-structured Transformation Registry Job Submission Data TransportResource Usage Banking BrokeringWorkflow Authorisation

82. LISHEP2004/UERJ 82 www.griphyn.org OGSA Standardization & Implementation l OGSI defines core interfaces and behaviors for manageable services –Supported by strong open source technology & major commercial vendors l Efforts are underway within GGF, OASIS, and other bodies to define standards for –Agreement negotiation –Common management model –Data access and integration –Security and policy –Etc., etc., etc.