Introduction to GT3 Background The Grid Problem The Globus Approach OGSA & OGSI Globus Toolkit GT3 Architecture and Functionality: The Latest Refinement of the Globus Toolkit Core Base s User-Defined s Future Directions Installation and Administration Installation Configuration Debugging Support Important Things to Remember June 2003 GGF8 Introduction to Globus Toolkit 3.0 1 GT-OGSA Grid Infrastructure Grid Container User-Defined s Base s System-Level s OGSI Spec Implementation Security Infrastructure Web Engine June 2003 GGF8 Introduction to Globus Toolkit 3.0 2 GT3 Core: OGSI Specification The Specification Defines how Entities can Create, Discover and Interact with a Grid GT3 Core Required: -Introspection ( data) - Explicit destruction - Soft-state lifetime Grid (required) data element data element other interfaces (optional) data element Implementation Optional: - creation - - Registration - Groups + applicationspecific interfaces locator Includes 0 or more Grid Handles (GSHs) Includes 0 or more Grid References (GSRs) June 2003 GGF8 Introduction to Globus Toolkit 3.0 3 June 2003 GGF8 Introduction to Globus Toolkit 3.0 4 1
GT3 Core: OGSI Implementation GT3 includes a set of primitives that implement the interfaces and behaviors defined in the latest version of the OGSI Specification The implementation supports a declarative programming model in which GT3 users can compose OGSI-Compliant grid s by plugging the desired primitives into their implementation GT3 Core: OGSI Specification (cont.) Grid porttype Defines the fundamental behavior of a Grid Introspection Discovery Soft State Lifetime Management Mandated by the Spec June 2003 GGF8 Introduction to Globus Toolkit 3.0 5 June 2003 GGF8 Introduction to Globus Toolkit 3.0 6 GT3 Core: OGSI Specification (cont.) Factory porttype Factories create s Factories are typically persistent s Factory is an optional OGSI interface (Grid s can also be instantiated by other mechanisms) GT3 Core: OGSI Specification (cont.) porttypes A subscription for notification causes the creation of a Subscription Sinks are not required to implement the Grid porttype s can be set on Data Elements porttypes are optional June 2003 GGF8 Introduction to Globus Toolkit 3.0 7 June 2003 GGF8 Introduction to Globus Toolkit 3.0 8 2
GT3 Core: OGSI Specification (cont.) group porttypes A Group is a grid that maintains information about a group of other grid s The classic registry model can be implemented with the Group porttypes A grid can belong to more than one Group Members of a Group can be heterogenous or homogenous Each entry in a group can be represented as its own group porttypes are optional OGSI interfaces GT3 Core: OGSI Specification (cont.) HandleResolver porttype Defines a means for resolving a GSH (Grid Handle) to a GSR (Grid Reference) A GSH points to a Grid (GT3 uses a hostname-based GSH scheme) A GSR specifies how to communicate with the Grid (GT3 currently supports SOAP over HTTP, so GSRs are in WSDL format) HandleResolver is an optional OGSI interface June 2003 GGF8 Introduction to Globus Toolkit 3.0 9 June 2003 GGF8 Introduction to Globus Toolkit 3.0 10 A Creation Scenario* A Creation Scenario 1. From a known registry, the client discovers a by querying the data of the registry 1. From a known registry, the client discovers a by querying the data of the registry create Factory * The scenarios in this presentation are offered as examples and are not prescriptive June 2003 GGF8 Introduction to Globus Toolkit 3.0 11 June 2003 GGF8 Introduction to Globus Toolkit 3.0 12 3
A Creation Scenario A Creation Scenario 1. From a known registry, the client discovers a by querying the data of the registry create Factory 3. The creates a 1. From a known registry, the client discovers a by querying the data of the registry create 4. The returns a locator Factory 3. The creates a June 2003 GGF8 Introduction to Globus Toolkit 3.0 13 June 2003 GGF8 Introduction to Globus Toolkit 3.0 14 A Creation Scenario A Scenario 1. From a known registry, the client discovers a by querying the data of the registry create 4. The returns a locator Factory 3. The creates a 1. Sink calls the subscribe operation on Source Source 5. The client and interact Sink June 2003 GGF8 Introduction to Globus Toolkit 3.0 15 June 2003 GGF8 Introduction to Globus Toolkit 3.0 16 4
A Scenario A Scenario Source Source Sink 1. Sink calls the subscribe operation on Source Subscription 2. Source creates a subscription Sink 1. Sink calls the subscribe operation on Source 3. Source returns a locator to the subscription Subscription 2. Source creates a subscription June 2003 GGF8 Introduction to Globus Toolkit 3.0 17 June 2003 GGF8 Introduction to Globus Toolkit 3.0 18 A Scenario 4.a deliver stream continues for the lifetime of Subscription Source A Scenario 4.a deliver stream continues for the lifetime of Subscription The sole mandated cardinality: 1 to 1 Source Sink 1. Sink calls the subscribe operation on Source 3. Source returns a locator to the subscription 4.b The Sink and Subscription interact to perform lifetime management Subscription 2. Source creates a subscription Sink 1. Sink calls the subscribe operation on Source 3. Source returns a locator to the subscription 4.b The Sink and Subscription interact to perform lifetime management Subscription 2. Source creates a subscription June 2003 GGF8 Introduction to Globus Toolkit 3.0 19 June 2003 GGF8 Introduction to Globus Toolkit 3.0 20 5
GT-OGSA Grid Infrastructure Grid Container User-Defined s Base s System-Level s OGSI Spec Implementation Security Infrastructure Web Engine June 2003 GGF8 Introduction to Globus Toolkit 3.0 21 GT3 Core: Security Infrastructure Transport Layer Security/Secure Socket Layer (TLS/SSL) To be deprecated SOAP Layer Security Based on WS-Security, XML Encryption, XML Signature GT3 uses X.509 identity certificates for authentication It also uses X.509 Proxy certificates to support delegation and single sign-on, updated to conform to latest IETF/GGF draft June 2003 GGF8 Introduction to Globus Toolkit 3.0 22 GT-OGSA Grid Infrastructure Grid Container User-Defined s Base s System-Level s OGSI Spec Implementation Security Infrastructure Web Engine GT3 Core: System Level s General-purpose s that facilitate the use of Grid s in production environments The 3.0 distribution includes the following System-Level s: An Administration A Logging A Management June 2003 GGF8 Introduction to Globus Toolkit 3.0 23 June 2003 GGF8 Introduction to Globus Toolkit 3.0 24 6
GT-OGSA Grid Infrastructure Grid Container User-Defined s Base s System-Level s OGSI Spec Implementation Security Infrastructure Web Engine June 2003 GGF8 Introduction to Globus Toolkit 3.0 25 GT3 Core: Grid Container Includes the OGSI Implementation, security infrastructure and system-level s, plus: activation, deactivation, construction, destruction, etc. data element placeholders that allow you to dynamically fetch data values at query time Evaluator framework (supporting ByXPath and ByName notifications and queries) Interceptor/callback framework (allows one to intercept certain lifecycle events) June 2003 GGF8 Introduction to Globus Toolkit 3.0 26 GT3 Core: Grid Container (cont.) Layers in the Web s Model GT-OGSA Grid Infrastructure Grid Container User-Defined s Interface Layer Transport Layer Implementation Layer OGSI Spec is here Transport/Binding Layer (GT3 supports SOAP over HTTP) Container is here Base s System-Level s OGSI Spec Implementation Security Infrastructure Web Engine June 2003 GGF8 Introduction to Globus Toolkit 3.0 27 June 2003 GGF8 Introduction to Globus Toolkit 3.0 28 7
GT3 Core: GT3 currently offers support for four Java s: Embedded Standalone Servlet EJB GT3 Core: Virtual Hosting Environment Framework Virtual Hosting allows grid s to be distributed across several remote containers Useful in implementing solutions for problems common to distributed computing Load balancing User account sandboxing June 2003 GGF8 Introduction to Globus Toolkit 3.0 29 June 2003 GGF8 Introduction to Globus Toolkit 3.0 30 A Creation Scenario Illustrating Redirection in Virtual Hosting A Creation Scenario Illustrating Redirection in Virtual Hosting 1. From a known registry, the client retrieves a locator Router HE Starter 1. From a known registry, the client retrieves a locator 2. The router intercepts the create call on the Router HE Starter June 2003 GGF8 Introduction to Globus Toolkit 3.0 31 June 2003 GGF8 Introduction to Globus Toolkit 3.0 32 8
A Creation Scenario Illustrating Redirection in Virtual Hosting 1. From a known registry, the client retrieves a locator 3. The router passes the create request to the Host Env Starter 2. The router intercepts the create call on the Router HE Starter A Creation Scenario Illustrating Redirection in Virtual Hosting 1. From a known registry, the client retrieves a locator 3. The router passes the create request to the Host Env Starter 2. The router intercepts the create call on the Router HE Starter 4.The HE Starter creates a new Host Env as well as the June 2003 GGF8 Introduction to Globus Toolkit 3.0 33 June 2003 GGF8 Introduction to Globus Toolkit 3.0 34 A Creation Scenario Illustrating Redirection in Virtual Hosting 1. From a known registry, the client retrieves a locator 3. The router passes the create request to the Host Env Starter 2. The router intercepts the create call on the 5. The router returns a locator Router HE Starter 4.The HE Starter creates a new Host Env as well as the A Creation Scenario Illustrating Redirection in Virtual Hosting 1. From a known registry, the client retrieves a locator 3. The router passes the create request to the Host Env Starter 2. The router intercepts the create call on the 5. The router returns a locator Router HE Starter 4.The HE Starter creates a new Host Env as well as the 6. Using the locator, the router redirects subsequent client- interactions June 2003 GGF8 Introduction to Globus Toolkit 3.0 35 June 2003 GGF8 Introduction to Globus Toolkit 3.0 36 9
GT-OGSA Grid Infrastructure Grid Container User-Defined s GT3 Base s Base s System-Level s OGSI Spec Implementation Security Infrastructure Web Engine June 2003 GGF8 Introduction to Globus Toolkit 3.0 37 June 2003 GGF8 Introduction to Globus Toolkit 3.0 38 GT3 Base: Resource Management GRAM Architecture rendered in OGSA The runs as an unprivileged user, with a small highly-constrained setuid executable behind it. Master User MJS User 1 MJS MJFS MJS User 2 MJFS MJS User 3 MJFS MJS MJS : Master Managed Job Factory MJFS: Managed Job Factory MJS: Managed Job June 2003 GGF8 Introduction to Globus Toolkit 3.0 39 1. From an index, the client chooses an GRAM Job Submission Scenario Index June 2003 GGF8 Introduction to Globus Toolkit 3.0 40 10
GRAM Job Submission Scenario GRAM Job Submission Scenario 1. From an index, the client chooses an Index create, supplying RSL 1. From an index, the client chooses an Index create, supplying RSL 3. The creates a Managed Job MJS June 2003 GGF8 Introduction to Globus Toolkit 3.0 41 June 2003 GGF8 Introduction to Globus Toolkit 3.0 42 GRAM Job Submission Scenario GRAM Job Submission Scenario 1. From an index, the client chooses an Index create, supplying RSL 4. The returns a locator 3. The creates a Managed Job 1. From an index, the client chooses an Index create, supplying RSL 4. The returns a locator 3. The creates a Managed Job MJS 5. The client subscribes to the MJS status SDE and retrieves output MJS June 2003 GGF8 Introduction to Globus Toolkit 3.0 43 June 2003 GGF8 Introduction to Globus Toolkit 3.0 44 11
GT3 Base: Information s Index as Caching Aggregator Caches data from other grid s Index as Provider Framework Serves as a host for data providers that live outside of a grid to publish data GT3 Base: Reliable File Transfer Reliably performs a third party transfer between two GridFTP servers OGSI-compliant exposing GridFTP control channel functionality Recoverable Grid Automatically restarts interrupted transfers from the last checkpoint Progress and Restart Monitoring GridFTP RFT Server 1 JDBC GridFTP Server 2 June 2003 GGF8 Introduction to Globus Toolkit 3.0 45 June 2003 GGF8 Introduction to Globus Toolkit 3.0 46 GT-OGSA Grid Infrastructure Grid Container User-Defined s Base s System-Level s OGSI Spec Implementation Security Infrastructure GT3 User-Defined s GT3 can be viewed as a Grid Development Kit that includes: Primitives designed to ease the task of building OGSI-Compliant s Primitives for provisioning security Base s that provide an infrastructure with which to build higher-level s Web Engine June 2003 GGF8 Introduction to Globus Toolkit 3.0 47 June 2003 GGF8 Introduction to Globus Toolkit 3.0 48 12
GT3 User-Defined s (cont.) Future Directions of GT User source files (Diagram inspired by Borja Sotomayor s excellent tutorial on GT3) ANT GT3 Build Files User Build File Grid executable files Standardization of container model Development of lightweight container/api Adding rich support for queries Further refinements of Base designs Pushing on standardizing at a higher level than OGSI June 2003 GGF8 Introduction to Globus Toolkit 3.0 49 June 2003 GGF8 Introduction to Globus Toolkit 3.0 50 13