Globus Toolkit® 4 Ian Foster Argonne National Laboratory University of Chicago Univa Corporation.

Globus Toolkit® 4

Ian FosterArgonne National Laboratory

University of Chicago

Univa Corporation

Credits

Globus Toolkit v4 is the work of many talented Globus Alliance members, at Argonne Natl. Lab & U.Chicago USC Information Sciences Corporation National Center for Supercomputing Applns U. Edinburgh Swedish PDC Univa Corporation Other contributors at other institutions

Supported by DOE, NSF, UK EPSRC, and other sources

On April 29, 2005 the On April 29, 2005 the Globus Alliance releasedGlobus Alliance releasedthe finest version of the the finest version of the Globus Toolkit to date!Globus Toolkit to date!

Don’t take our word for it!Read the UK eScience Evaluation of GT4

www.nesc.ac.uk/technical_papers/UKeS-2005-03.pdf(Reachable from www.globus.org, under “News”)

Overview

Background and Globus approach Globus Toolkit: current capabilities Future directions Related tools

“… A new age has dawned in scientific and engineering research, pushed by continuing progress in computing, information, and communication technology, and pulled by the expanding complexity, scope and scale of today’s challenges. The capacity of this technology has crossed thresholds that now make possible a comprehensive cyberinfrastructure on which to build new types of scientific and engineering knowledge environments and organizations, and to pursue research in new ways and with increased efficacy…”

National Science Foundation Blue Ribbon Advisory Panel, 2003

History

In the early 90s, I (Foster) and others (e.g., Carl Kesselman, USC-ISI) enjoyed helping scientists apply distributed computing

Opportunities seemed ripe for the picking Application of technology always uncovers

new and interesting requirements Science is cool Big/innovative science is even cooler

History (continued)

While helping to build/integrate a diverse range of applications, the same problems kept showing up over and over again

Too many different security systems Too many different scheduling/execution

mechanisms Too many different storage systems Too many different monitoring/status/event

systems

What Kinds of Applications? Computation intensive

Interactive simulation (climate modeling) Large-scale simulation and analysis (galaxy formation, gravity

waves, event simulation) Engineering (parameter studies, linked models)

Data intensive Experimental data analysis (e.g., physics) Image & sensor analysis (astronomy, climate)

Distributed collaboration Online instrumentation (microscopes, x-ray) Remote

visualization (climate studies, biology) Engineering (large-scale structural testing)

Key Common Feature

The size and/or complexity of the problem requires that people in several organizations collaborate and share computing resources, data, instruments

An Example Problem The Large Hadron

Collider (LHC) Largest machine

ever built by humans! Located at CERN,

Geneva Switzerland Particle accelerator and

collider with a circumference of 16.8 miles

Scheduled to go into production in 2007

An Example Problem (continued)

Will generate 10 Petabytes (107 Gigabytes) of information per year

This information must be processed and stored somewhere

It is beyond the scope of a single institution to manage this problem

Virtual Organizations• Distributed resources and people• Linked by networks, crossing admin domains• Sharing resources, common goals• Dynamic

VO-BVO-A

VO-A VO-B

Virtual Organizations• Distributed resources and people• Linked by networks, crossing admin domains• Sharing resources, common goals• Dynamic• Fault tolerant

The Globus Approach

The Role of the Globus Toolkit

A collection of solutions to problems that come up frequently when building collaborative distributed applications

Heterogeneity A focus, in particular, on overcoming

heterogeneity for application developers Standards

We capitalize on and encourage use of existing standards (IETF, W3C, OASIS, GGF)

GT also includes reference implementations of new/proposed standards in these organizations

Layers in the Grid

A Typical eScience Use of Globus:Network for Earthquake Eng. Simulation

Links instruments, data, computers, people

Without the Globus Toolkit

WebBrowser

ComputeServer

DataCatalog

DataViewer

Certificateauthority

ChatTool

CredentialRepository

WebPortal

ComputeServer

Resources implement standard access & management interfaces

Collective services aggregate &/or

virtualize resources

Users work with client applications

Application services organize VOs & enable

access to other services

Databaseservice

SimulationTool

Camera

TelepresenceMonitor

RegistrationService

Application Developer

Off the Shelf

Globus Toolkit

Grid Community

With the Globus Toolkit

WebBrowser

ComputeServer

GlobusMCS/RLS

DataViewer

CertificateAuthority

CHEF ChatTeamlet

MyProxy

ComputeServer

Resources implement standard access & management interfaces

Collective services aggregate &/or

virtualize resources

Users work with client applications

Application services organize VOs & enable

access to other services

Databaseservice

SimulationTool

Camera

TelepresenceMonitor

Globus IndexService

GlobusGRAM

GlobusDAI

Application Developer

Off the Shelf

Globus Toolkit

Grid Community

The Globus Toolkit:“Standard Plumbing” for the Grid

Not turnkey solutions, but building blocks & tools for application developers & system integrators Some components (e.g., file transfer) go farther than

others (e.g., remote job submission) toward end-user relevance

Easier to reuse than to reinvent Compatibility with other Grid systems comes for free

Today the majority of the GT public interfaces are usable by application developers and system integrators Relatively few end-user interfaces In general, not intended for direct use by end users

(scientists, engineers, marketing specialists)

The Application-Infrastructure Gap

Dynamicand/or

DistributedApplications

Shared Distributed Infrastructure

Provisioning

Bridging the Gap:Grid Infrastructure

Service-oriented Gridinfrastructure Provision physical

resources to support application workloads

ApplnService

Workflows

Composition

Invocation

Service-oriented applications Wrap applications as

services Compose applications

into workflows

Grid Infrastructure

Distributed management Of physical resources Of software services Of communities and their policies

Unified treatment Build on Web services framework Use WS-RF, WS-Notification (or WS-

Transfer/Man) to represent/access state Common management

abstractions & interfaces

Globus is Open Source Grid Infrastructure

Implement key Web services standards State, notification, security, …

Software for Grid infrastructure Service-enable new & existing resources E.g., GRAM on computer, GridFTP on storage system,

custom application services Uniform abstractions & mechanisms

Tools to build applications that exploit Grid infrastructure Registries, security, data management, …

Enabler of a rich tool & service ecosystem

An eBusiness Use of Globus:SAP Demonstration @ GlobusWorld

3 Globus-enabled applns: CRM: Internet Pricing Configurator (IPC) CRM: Workforce

Management (WFM) SCM: Advanced Planner

& Optimizer (APO) Applications modified to:

Adjust to varying demand & resources

Use Globus to discover & provision resources

IPCDispatcher

IPCServerRequest:

Price Query

Delegation ofRequest

Response: PricelistDepending on: - Time - Discount - Number of Items - …

Web Browsers / Batch Processes(typically several thousand requests)

IPCServer

SAP AG R/3 Internet Pricing & Configurator (IPC)

Overview

The Globus Toolkit is a Collection of Components

A set of loosely-coupled components, with: Services and clients Libraries Development tools

GT components are used to build Grid-based applications and services GT can be viewed as a Grid SDK

GT components can be categorized across two different dimensions By broad domain area By protocol support

GT Domain Areas

Core runtime Infrastructure for building new services

Security Apply uniform policy across distinct systems

Execution management Provision, deploy, & manage services

Data management Discover, transfer, & access large data

Monitoring Discover & monitor dynamic services

GT Protocols

Web service protocols WSDL, SOAP WS Addressing, WSRF, WSN WS Security, SAML, XACML WS-Interoperability profile

Non Web service protocols Standards-based, such as GridFTP Custom

“Stateless” vs. “Stateful” Services

Without state, how does client: Determine what happened (success/failure)? Find out how many files completed? Receive updates when interesting events arise? Terminate a request?

Few useful services are truly “stateless”, but WS interfaces alone do not provide built-in support for state

Client

FileTransferService

move (A to B)move

FileTransferService (without WSRF)

Developer reinvents wheel for each new service Custom management and identification of state: transferID Custom operations to inspect state synchronously

(whatHappen) and asynchronously (tellMeWhen) Custom lifetime operation (cancel)

Client

FileTransferService

move (A to B) : transferIDmove

statewhatHappen

tellMeWhen

cancel

WSRF in a Nutshell Service State representation

Resource Resource Property

State identification Endpoint Reference

State Interfaces GetRP, QueryRPs,

GetMultipleRPs, SetRP Lifetime Interfaces

SetTerminationTime ImmediateDestruction

Notification Interfaces Subscribe Notify

ServiceGroups

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

FileTransferService (w/ WSRF)

Developer specifies custom method to createResource and leaves the rest to WSRF standards:

State exposed as Resource + Resource Properties and identified by Endpoint Reference (EPR)

State inspected by standard interfaces (GetRP, QueryRPs) Lifetime management by standard interfaces (Destroy)

ClientFileTransferService

createResource (A to B) : EPRcreateResource

Transfer getRP

queryRPs

destroy

Data MgmtSecurityCommonRuntime

Execution Mgmt

Info Services

Non-WS Components

Pre-WSAuthenticationAuthorization

GridFTPC CommonLibraries

Globus Toolkit version 2 (GT2)

Grid ResourceAlloc. Mgmt

(GRAM)

Monitoring& Discovery

Web Services

Components

Execution Mgmt

Info Services

Web Services

Components

Non-WS Components

GridFTPC CommonLibraries

WSAuthenticationAuthorization

ReliableFile

Transfer

Data Access& Integration

Grid ResourceAlloc. Mgmt(WS GRAM)

MDS3Java

WS Core

CommunityAuthorization

ReplicaLocation

eXtensibleIO (XIO)

Grid ResourceAlloc. Mgmt

(GRAM)

Monitoring& Discovery

Execution Mgmt

Info Services

Web Services

Components

Non-WS Components

GridFTPPre-WS

Grid ResourceAlloc. & Mgmt

Pre-WSMonitoring

& Discovery

C CommonLibraries

AuthenticationAuthorization

ReliableFile

Transfer

Grid ResourceAllocation &

ManagementIndex

Java WS Core

ReplicaLocation

eXtensibleIO (XIO)

CredentialMgmt

CommunitySchedulingFramework

Delegation

DataReplication

TriggerC

WS Core

Python WS Core

WebMDS

WorkspaceManagement

Grid Telecontrol

Protocol

Contrib/Preview

Depre-cated

www.globus.org

Data Mgmt

SecurityCommonRuntime

Execution Mgmt

Info Services

GridFTPAuthenticationAuthorization

ReliableFile

Transfer

ManagementIndex

DataReplication

Delegation

ReplicaLocation

Trigger

Java Runtime

C Runtime

Python Runtime

WebMDS

WorkspaceManagement

Grid Telecontrol

Protocol

Globus Toolkit v4www.globus.org

CredentialMgmt

Globus Toolkit: Open Source Grid Infrastructure

4.0 is not a typical “.0” release,but the culmination of months of testing

3.0.0 3.2.0

4.0.03.9.4

3.2.13.0.1

CVS trunk

Stable release branch

Development release

Stable release

Java Services in Apache AxisPlus GT Libraries and Handlers

YourJava

Service

YourPythonService

YourJava

Service RF

pyGlobusWS Core

Service

C WS Core

C Services using GT Libraries and Handlers

SERVER

CLIENT

InteroperableWS-I-compliant

SOAP messaging

YourJavaClient

Client

YourPythonClient

YourJavaClient

Client

YourPythonClient

YourJavaClient

Client

YourPythonClient

YourJavaClient

Client

YourPythonClient

X.509 credentials =common authentication

Python hosting, GT Libraries

GT4 Components

Our Goals for GT4

Usability, reliability, scalability, … Web service components have quality equal or

superior to pre-WS components Documentation at acceptable quality level

Consistency with latest standards (WS-*, WSRF, WS-N, etc.) and Apache platform WS-I Basic Profile compliant WS-I Basic Security Profile compliant

New components, platforms, languages And links to larger Globus ecosystem

Data Mgmt

Execution Mgmt

Info Services

ReliableFile

Transfer

ManagementIndex

DataReplication

Delegation

ReplicaLocation

Trigger

Java Runtime

C Runtime

Python Runtime

WebMDS

WorkspaceManagement

Grid Telecontrol

Protocol

CredentialMgmt

GT4 Web Services Runtime

Supports both GT (GRAM, RFT, Delegation, etc.) & user-developed services

Redesign to enhance scalability, modularity, performance, usability

Leverages existing WS standards WS-I Basic Profile: WSDL, SOAP, etc. WS-Security, WS-Addressing

Adds support for emerging WS standards WS-Resource Framework, WS-Notification

Java, Python, & C hosting environments Java is standard Apache

GT4 WS Core in a Nutshell

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

Implementation of WSRF: Resources,

EndpointReferences, ResourceProperties

Operation Providers: pre-build implementations of

WSRF operations

Notification implementation: Topics, TopicSet, Embedded

Notification Consumer service

Implementations of Resources (ReflectionResource,

PersistentReflectionResource) and ResourceProperties

(SimpleResourceProperty, ReflectionResourceProperty)

Service Container

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Service Container: host multiple services in container; one JVM

process

…more details: based on AXIS service

container, processes SOAP messages, ResourceContext

extension.

Service Container

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Secure Communication: Transport, Message,

Conversation (Transport demonstrates best

performance)

Configurable Security Policies: Policy Information

Points (PIPs), Policy Decision Points (PDP) -- chained

Example authorization PDPs: GridMap, SAML

implementations,XACML policies

Service Container

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

WorkManager DB Conn Pool JNDI Directory

WorkManager: “thread pool”, site independent

“work” manager

Apache Database Connection Pool library

(JDBC “DataSource” implementation)

JNDI Directory: manages internal, shared objects

(ResourceHomes, WorkManager,

Configuration objects,…)

Apache Tomcat

Service Container

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

Resource

ServiceGetRP

GetMultRPs

QueryRPs

Subscribe

SetTermTime

Destroy

EPREPR

ResourceHome

WorkManager DB Conn Pool JNDI Directory

Deploy Service Container “standalone”

or within Apache Tomcat

CustomWeb

ServicesWS-Addressing, WSRF,

WS-Notification

CustomWSRF Web

Services

GT4WSRF Web

Services

WSDL, SOAP, WS-Security

User Applications

GT4 Web Services Runtime

StatefulEntities

Registry

Service requestor (e.g., user application)

Factoryservice

Create Stateful Entity

State Address

Resource allocation

RegisterStateful

Entity

Discovery

Interactions standardized using WSDL and SOAP

State inspection Lifetime mgmt Notifications

Authentication & Authorization are applied to all requests

Modeling State in Web Services

WSRF & WS-Notification Naming and bindings (basis for virtualization)

Every resource can be uniquely referenced, and has one or more associated services for interacting with it

Lifecycle (basis for fault resilient state mgmt) Resources created by services following factory pattern Resources destroyed immediately or scheduled

Information model (basis for monitoring, discovery) Resource properties associated with resources Operations for querying and setting this info Asynchronous notification of changes to properties

Service groups (basis for registries, collective svcs) Group membership rules & membership management

Base Fault type

GT4-Java GT4-C pyGridWare WSRF::Lite WSRF.NET

Languages supported Java C Python Perl C#/C++/VBasic, etc.

WS-Security password profile Yes No In progress In progress Yes

WS-Security X.509 profile Yes In progress Yes In progress Yes

WS-SecureConversation Yes No Yes No Yes

TLS/SSL Yes Yes Yes Yes Yes

Authorization Multiple Multiple Callout None

Persistence of WS-Resources Yes Not default Yes Yes Yes

Memory Footprint JVM + 10M 22 KB 12 MB 12 MB Depends

Memory size per WS-ResourceDepends on

resource state70B

Depends on resource state

0 (file/DB) or 10B (process)

Depends on resource state

Unmodified hosting environment Yes No Yes Yes (Apache) Yes

Compliance with WS-I Basic Profile

Yes Yes Yes In progress Yes

Compliance withWS-I Basic Security Profile

Yes Yes Yes No Yes

Logging Log4J Yes Yes Yes WSE diagnostics

WS-ResourceLifetime Yes Yes Yes Yes Yes

WS-ResourceProperties Yes Yes Yes Yes Yes

WS-ServiceGroup Yes Yes Yes Yes Yes

WS-BaseFaults Yes Yes Yes Yes Yes

WS-BaseNotification Yes Consumer Yes No Yes

WS-BrokeredNotification Partial No No No Yes

WS-Topics Partial Partial Partial No Partial

GetRP Test

Distributed client and service on same LAN(times in milliseconds)

GT4 - Java

GT4 - C

pyGridWare

WSRF::Lite

WSRF.NET

No Security

GT4 - Java

GT4 - C

pyGridWare

WSRF::Lite

WSRF.NET

GT4 - Java

GT4 - C

pyGridWare

WSRF::Lite

WSRF.NET

X509 Signing HTTPS

181.96

N/A11.46

2.8512.91

149.67

56GT4 WS Core Performance

GT4 Java GT4 C GT4 Python WSRF.NET

GetRP 181.96 14.77 140.50 81.39

SetRP 182.04 14.99 142.21 82.48

CreateR 188.46 14.98 132.26 96.22

DestroyR 182.03 15.76 136.12 86.89

Notify 219.51 N/A 244.93 101.57

GT4 Java GT4 C GT4 Python WSRF.NET

getRP 11.46 2.85 149.67 12.91

setRP 11.47 2.86 150.79 12.3

createR 18.00 2.82 132.60 20.84

destroyR 14.92 2.71 149.21 16.05

Notify 29.26 9.67 169.07 45.0

(1) Message-level security (times in milliseconds)

(2) Transport-level security (times in milliseconds)

“WSRF/WSNs Compared,” HPDC 2005.

Data Mgmt

Execution Mgmt

Info Services

ReliableFile

Transfer

ManagementIndex

DataReplication

Delegation

ReplicaLocation

Trigger

Java Runtime

C Runtime

Python Runtime

WebMDS

WorkspaceManagement

Grid Telecontrol

Protocol

CredentialMgmt

Globus Security

Control access to shared services Address autonomous management, e.g.,

different policy in different work-groups Support multi-user collaborations

Federate through mutually trusted services Local policy authorities rule

Allow users and application communities to set up dynamic trust domains Personal/VO collection of resources working

together based on trust of user/VO

Organization A Organization B

Compute Server C1Compute Server C2

Compute Server C3

File server F1 (disks A and B)

Person C(Student)

Person A(Faculty)

Person B(Staff) Person D

(Staff)Person F(Faculty)

Person E(Faculty)

Virtual Community C

Person A(Principal Investigator)

Compute Server C1'

Person B(Administrator)

File server F1 (disk A)

Person E(Researcher)

Person D(Researcher)

Virtual Organization (VO) Concept

VO for each application or workload Carve out and configure resources for a particular

use and set of users

GT4 Security

RightsUsers

Rights’

ComputeCenter

Access

Services (runningon user’s behalf)

Rights

Local policyon VO identityor attributeauthority

CAS or VOMSissuing SAMLor X.509 ACs

SSL/WS-Securitywith ProxyCertificates

Authz Callout:SAML, XACML

MyProxy

GT4 Security Public-key-based authentication Extensible authorization framework based on Web

services standards SAML-based authorization callout

As specified in GGF OGSA-Authz WG

Integrated policy decision engine XACML policy language, per-operation policies, pluggable

Credential management service MyProxy (One time password support)

Community Authorization Service Standalone delegation service

GT4’s Use of Security Standards

Supported, Supported, Fastest, but slow but insecure so default

GT-XACML Integration

eXtensible Access Control Markup Language OASIS standard, open source implementations

XACML: sophisticated policy language Globus Toolkit ships with XACML runtime

Included in every client and server built on GT Turned-on through configuration

… that can be called transparently from runtime and/or explicitly from application …

… and we use the XACML-”model” for our Authz Processing Framework

GT Authorization Framework

Other Security Services Include …

MyProxy Simplified credential management Web portal integration Single-sign-on support

KCA & kx.509 Bridging into/out-of Kerberos domains

SimpleCA Online credential generation

PERMIS Authorization service callout

Data Mgmt

Execution Mgmt

Info Services

ReliableFile

Transfer

ManagementIndex

DataReplication

Delegation

ReplicaLocation

Trigger

Java Runtime

C Runtime

Python Runtime

WebMDS

WorkspaceManagement

Grid Telecontrol

Protocol

CredentialMgmt

GT4 Data Management Stage/move large data to/from nodes

GridFTP, Reliable File Transfer (RFT) Alone, and integrated with GRAM

Locate data of interest Replica Location Service (RLS)

Replicate data for performance/reliability Distributed Replication Service (DRS)

Provide access to diverse data sources File systems, parallel file systems, hierarchical

storage: GridFTP Databases: OGSA DAI

GridFTP in GT4 100% Globus code

No licensing issues Stable, extensible

IPv6 Support XIO for different transports Striping multi-Gb/sec wide area transport

27 Gbit/s on 30 Gbit/s link Pluggable

Front-end: e.g., future WS control channel Back-end: e.g., HPSS, cluster file systems Transfer: e.g., UDP, NetBLT transport

Bandwidth Vs Striping

0 10 20 30 40 50 60 70

Degree of Striping

# Stream = 1 # Stream = 2 # Stream = 4

# Stream = 8 # Stream = 16 # Stream = 32

Disk-to-disk onTeraGrid

Reliable File Transfer:Third Party Transfer

RFT Service

RFT Client

SOAP Messages

Notifications(Optional)

DataChannel

Protocol Interpreter

MasterDSI

DataChannel

SlaveDSI

IPCReceiver

IPC Link

MasterDSI

Protocol Interpreter

Data Channel

IPCReceiver

SlaveDSI

Data Channel

IPC Link

GridFTP Server GridFTP Server

Fire-and-forget transfer Web services interface Many files & directories Integrated failure recovery Has transferred 900K files

Replica Location Service

Identify location of files via logical to physical name map

Distributed indexing of names, fault tolerant update protocols

GT4 version scalable & stable

Managing ~40 million files across ~10 sites

IndexIndex

Local DB

Update send (secs)

Bloom filter

(secs)

Bloom filter (bits)

10K <1 2 1 M

1 M 2 24 10 M

5 M 7 175 50 M

Cardiff

AEI/Golm

Birmingham•

Reliable Wide Area Data Replication

Replicating >1 Terabyte/day to 8 sites>30 million replicas so farMTBF = 1 month

LIGO Gravitational Wave Observatory

www.globus.org/solutions

OGSA-DAI

Provide service-based access to structured data resources as part of Globus

Specify a selection of interfaces tailored to various styles of data access—starting with relational and XML

OGSA-DAI service

Engine

SQLQuery

JDBCData

Resources

Activities

The OGSA-DAI Framework

GZip GridFTPXPath

XIndice

readFile

SWISSPROT

SQLServer

Data-bases

ApplicationApplicationClient ToolkitClient Toolkit

OGSA-DAI service

Engine

SQLQuery

MultipleSQL GDS

SQLQuery

Extensibility Example

75OGSA-DAI: A Framework for Building Applications

Supports data access, insert and update Relational: MySQL, Oracle, DB2, SQL Server, Postgres XML: Xindice, eXist Files – CSV, BinX, EMBL, OMIM, SWISSPROT,…

Supports data delivery SOAP over HTTP FTP; GridFTP E-mail Inter-service

Supports data transformation XSLT ZIP; GZIP

Supports security X.509 certificate based security

OGSA-DAI: Other Features

A framework for building data clients Client toolkit library for application developers

A framework for developing functionality Extend existing activities, or implement your own Mix and match activities to provide functionality

you need Highly extensible

Customise our out-of-the-box product Provide your own services, client-side support,

and data-related functionality

Data Mgmt

Execution Mgmt

Info Services

ReliableFile

Transfer

ManagementIndex

DataReplication

Delegation

ReplicaLocation

Trigger

Java Runtime

C Runtime

Python Runtime

WebMDS

WorkspaceManagement

Grid Telecontrol

Protocol

CredentialMgmt

Execution Management (GRAM)

Common WS interface to schedulers Unix, Condor, LSF, PBS, SGE, …

More generally: interface for process execution management Lay down execution environment Stage data Monitor & manage lifecycle Kill it, clean up

A basis for application-driven provisioning

GT4 WS GRAM

2nd-generation WS implementation optimized for performance, flexibility, stability, scalability

Streamlined critical path Use only what you need

Flexible credential management Credential cache & delegation service

GridFTP & RFT used for data operations Data staging & streaming output Eliminates redundant GASS code

GRAMservices

GT4 Java Container

GRAMservices

Delegation

RFT FileTransfer

Transferrequest

GridFTPRemote storage element(s)

Localscheduler

Userjob

Compute element

GridFTP

GRAMadapter

FTPcontrol

Local job control

Delegate

FTP data

ent Job

functions

Delegate

Service host(s) and compute element(s)

GT4 WS GRAM Architecture

SEGJob events

GRAMservices

GT4 Java Container

GRAMservices

Delegation

RFT FileTransfer

Transferrequest

Localscheduler

Userjob

Compute element

GridFTP

GRAMadapter

FTPcontrol

Local job control

Delegate

FTP data

ent Job

functions

Delegate

SEGJob events

Delegated credential can be:Made available to the application

GRAMservices

GT4 Java Container

GRAMservices

Delegation

RFT FileTransfer

Transferrequest

Localscheduler

Userjob

Compute element

GridFTP

GRAMadapter

FTPcontrol

Local job control

Delegate

FTP data

ent Job

functions

Delegate

SEGJob events

Delegated credential can be:Used to authenticate with RFT

GRAMservices

GT4 Java Container

GRAMservices

Delegation

RFT FileTransfer

Transferrequest

Localscheduler

Userjob

Compute element

GridFTP

GRAMadapter

FTPcontrol

Local job control

Delegate

FTP data

ent Job

functions

Delegate

SEGJob events

Delegated credential can be:Used to authenticate with GridFTP

WS GRAM Performance

Time to submit a basic GRAM job Pre-WS GRAM: < 1 second WS GRAM: 2 seconds

Concurrent jobs Pre-WS GRAM: 300 jobs WS GRAM: 32,000 jobs

Various studies are underway to test latest software

GT4 WS GRAM Performance

Number of Client Threads (M)

1 2 4 8 16 32 64 128

1 7 15 29 57 80 69 69 70

2 15 29 58 79 74 70 70 64

4 29 58 78 77 68 69 52 69

8 59 77 77 72 65 27 69

16 77 77 75 64 27 50

32 76 75 68 64 67

64 75 73 70 66 65

128 80 72 64 63 71

All numbers are simple jobs/minute, no delegation or staging

Workspace Service:The Hosted Activity

Policy

Client

Environment

Activity

Negotiate accessInitiate activityMonitor activityControl activity

Interface Resource provider

Activities Can Be Nested

Policy

Client

Environment

Interface Resource provider

ClientClient

For Example …

Physical machineProcure hardware

Hypervisor/OS Deploy hypervisor/OS

VM VM Deploy virtual machine

Provisioning, management, and monitoring at all levels

JVM Deploy container

JVM Deploy service

Dynamic Service Deployment

CommunityA

CommunityZ

• Community scheduling logic• Data distribution• Community management• Science services• ...

Requirements:• Community control• Persistence• Resource guarantees• Non- interference

Virtual Machine Costs

GRAM job

GRAM job in paused VM

Job in booted VM

Virtual OSG Clusters

OSG cluster

Xen hypervisors

TeraGrid cluster

Data Mgmt

Execution Mgmt

Info Services

ReliableFile

Transfer

ManagementIndex

DataReplication

Delegation

ReplicaLocation

Trigger

Java Runtime

C Runtime

Python Runtime

WebMDS

WorkspaceManagement

Grid Telecontrol

Protocol

CredentialMgmt

Monitoring and Discovery

“Every service should be monitorable and discoverable using common mechanisms” WSRF/WSN provides those mechanisms

A common aggregator framework for collecting information from services, thus: MDS-Index: Xpath queries, with caching MDS-Trigger: perform action on condition (MDS-Archiver: Xpath on historical data)

Deep integration with Globus containers & services: every GT4 service is discoverable GRAM, RFT, GridFTP, CAS, …

GT4 Container

GT4 Monitoring & Discovery

GRAM User

MDS-Index

GT4 Cont.

MDS-Index

GT4 Container

MDS-Index

GridFTP

adapter

Registration &WSRF/WSN Access

Custom protocolsfor non-WSRF entities

Clients(e.g., WebMDS)

Automatedregistrationin container

WS-ServiceGroup

Index Server Performance

As the MDS4 Index grows, query rate and response time both slow, although sublinearly

Response time slows due to increasing data transfer size Full Index is being returned Response is re-built for every query

Real question – how much over simple WS-N performance?

Information Providers

GT4 information providers collect information from some system and make it accessible as WSRF resource properties

Growing number of information providers Ganglia, CluMon, Nagios SGE, LSF, OpenPBS, PBSPro, Torque

Many opportunities to build additional ones E.g., network monitoring, storage systems,

various sensors

Java Services in Apache AxisPlus GT Libraries and Handlers

YourJava

Service

YourPythonService

YourJava

Service RF

pyGlobusWS Core

Service

C WS Core

C Services using GT Libraries and Handlers

SERVER

CLIENT

InteroperableWS-I-compliant

SOAP messaging

YourJavaClient

Client

YourPythonClient

YourJavaClient

Client

YourPythonClient

YourJavaClient

Client

YourPythonClient

YourJavaClient

Client

YourPythonClient

X.509 credentials =common authentication

Python hosting, GT Libraries

GT4 Summary

GT4 Documentation

is Much Improved!

Overview

The Globus Commitment to Open Source

Globus was first established as an open source project in 1996

The Globus Toolkit is open source to: allow for inspection

for consideration in standardization processes

encourage adoption in pursuit of ubiquity and interoperability

encourage contributions harness the expertise of the community

The Globus Toolkit is distributed under the (BSD-style) Apache License version 2

The Future:Structure

NSF Community Driven Improvement of Globus Software (CDIGS) project 5 years of funding for GT enhancement Regular Globus roadmaps outlining plans

GlobDev http://dev.globus.org Apache-like community development site Community governance of components “Globus Toolkit” & other related software Open for business early 2006 “Globus Alliance” = “GlobDev committers”

GlobDev The current set of Globus components will be

organized into several “Globus Projects” Projects release products

Each project will have its own group of “Committers” committers are responsible for governance on

matters relating to their products The “Globus Management Committee” will

provide overall guidance and conflict resolution approve the creation of new Globus Projects

The Future:Content

We now have a solid and extremely powerful Web services base

Next, we will build an expanded open source Grid infrastructure Virtualization New services for provisioning, data management,

security, VO management End-user tools for application development Etc., etc.

And of course responding to user requests for other short-term needs

The Future

We now have a solid and extremely powerful Web services base

Next, we will build an expanded open source Grid infrastructure Virtualization New services for provisioning, data management,

security, VO management End-user tools for application development Etc., etc.

And of course responding to user requests for other short-term needs

Short-Term Priorities: Security

Improve GSI error reporting & diagnostics Secure password, one-time password,

Kerberos support for initial log on Trust roots, use of GridLogon Identity/attribute assertions in GT auth.

callouts (e.g., Shib, PERMIS, VOMS, SAML) Extend CAS admin & policy support Security logging with management control

for audit purposes

Short-Term Priorities: Data Management

Space & bandwidth management in GridFTP

Concurrency in globus-url-copy Priorities in RFT Data replication service Enhance policy support in data services Physical file name creation service Scalable & distributed metadata manager

Short-Term Priorities: Execution Management

Implement GGF JSDL once finalized Advance reservation support Policy-driven restart of “persistent” jobs Improved information collection for jobs Improved management of job collections Credential refresh Development of workspace service Integration of virtual machines (Xen, VMware) and

associated services Windows port of WS GRAM

Short-Term Priorities: Information Services

Many more information sources, including gateways to other systems

Automated configuration of monitoring Specialized monitoring displays Performance optimization of registry Archiver service Helper tools to streamline integration of

new information sources

Short-Term Priorities: WS Core

Streamlined container configuration Remote management interface Dynamic service deployment Service isolation: multiple service instances WS-Notification, subscription performance Full functionality in C WS Core Optimized WS-ServiceGroup support WS-SecureConversation support

What to Expect from theGlobus Alliance in the Coming Months

Support for users of GT4 Working to make sure the toolkit meets user

needs Answering questions on the mailing lists Further improving documentation

Normal evolution of performance, scalability and feature enhancements

Further development of tools and services in support of VOs

Expanding contributions to Globus

Overview

The Globus Ecosystem

Globus components address core issues relating to resource access, monitoring, discovery, security, data movement, etc. GT4 being the latest version

A larger Globus ecosystem of open source and proprietary components provide complementary components A growing list of components

These components can be combined to produce solutions to Grid problems We’re building a list of such solutions

Many Tools Build on, or Can Contribute to, GT4-Based Grids

Condor-G, DAGman MPICH-G2 GRMS Nimrod-G Ninf-G Open Grid Computing Env. Commodity Grid Toolkit GriPhyN Virtual Data System Virtual Data Toolkit GridXpert Synergy

Platform Globus Toolkit VOMS PERMIS GT4IDE Sun Grid Engine PBS scheduler LSF scheduler GridBus TeraGrid CTSS NEES IBM Grid Toolbox …

DocumentingThe Grid

Ecosystem

The Grid Ecosystem: Software Components for Grid SystemsAnd Applications

www.grids-center.org

Example Solutions

Portal-based User Reg. System (PURSE) VO Management Registration Service Service Monitoring Service TeraGrid TGCP Tool Lightweight Data Replicator GriPhyN Virtual Data System

Condor-G

The Condor Project @ U Wisconsin Madison develops software for high-throughput computing on collections of distributed compute resources

Condor-G is an interface to GRAM created by the Condor team that allows users to submit jobs to GRAM servers

GridShib Allows the use of Shibboleth-transported

attributes for authorization in GT4 deployments And, more generally, SAML support

2 year project started December 1, 2004 Participants

Von Welch, UIUC/NCSA (PI) Kate Keahey, UChicago/Argonne (PI) Frank Siebenlist, Argonne Tom Barton, UChicago

Beta software released September 16, 2005

Handle System

The Handle System from CNRI (http://www.handle.net) is a general-purpose global name service enabling secure name resolution over the internet

The Handle System-GT Integration Project leverages the Handle System for identifier and resolution services through tight integration with GT4’s Web services protocols

MPICH-G2

MPICH-G2, developed at Northern Illinois University and Argonne National Lab, is a grid-enabled implementation of the MPI v1.1 standard

MPICH-G2 is implemented using the pre-WS GRAM component in GT4; integration with GT4 WS GRAM is expected in the near future

Nimrod/G

Nimrod is a specialized parametric modeling system from Monash University

Nimrod/G uses a simple declarative parametric modeling language to express parameter sweep experiments. Based on GT4 WS services, Nimrod/G enables the formulation, execution and monitoring of multiple individual parametric experiments

Ninf-G4

Ninf-G4, from AIST, is a reference implementation of the GGF standard GridRPC API

Ninf-G4 is provides higher-level programming APIs for the development and execution of parallel applications on the Grid

PERMIS

PERMIS is an EU-funded Privilege Management service that implements Role-Based Access Control

Thanks to the work of the UK Grid Engineering Task Force, services running in a Java WS Core container can use PERMIS via GT4’s SAML authorization callouts

SRB is a package from SDSC providing a uniform interface for connecting to network-based heterogeneous data resources

GT4’s GridFTP includes an interface to SRB data sources, and vice versa

Sun Grid Engine

Sun Grid Engine is an open source distributed resource management system from Sun Microsystems

In a collaboration between the London e-Science Centre, Gridwise and MCNC, the Sun Grid Engine has been integrated with GT4

Tells Us About YourGrid Tools & Solutions

We list links to related projects on the “Related Software” of the Globus Toolkit web www.globus.org/toolkit/tools/

“Solutions” are documented on the Globus web www.globus.org/solutions/

If we’ve got details wrong or you have a GT4-related tool to list on our website, please send mail to info@globus.org

Questions?Questions?

Globus Toolkit® 4 Ian Foster Argonne National Laboratory University of Chicago Univa Corporation.

u argonne

supercomputing applns

different storage systems

different security systems

cooler slide

instruments slide

news slide

cool u biginnovative

Documents

GRAM: Grid Resource Allocation & Management Globus...

Grid Computing and the Globus Toolkit Jennifer M. Schopf...

globus online Product...

Ian Foster on behalf of the Globus Alliance Computation...

Grid Services Overview & Introduction Ian Foster Argonne...

Bruksanvisning - Univa

Inicio - Univa

Globus: A Core Grid Middleware Source: The Globus Project...

Globus Ian Foster and Carl Kesselman Argonne National...

Globus Connect Personal · Globus Connect Personal...

The Globus Toolkit: Description and Applications Review...

1 Globus Grid Middleware: Basics, Components, and Services.....

The Grid: Opportunities, Achievements, and Challenges for...

Globus: Where Are We Going For the Next 10 Years? Jennifer.....

Campus Bridging Made Easy via Globus Services · Campus...

KESSEL-Schachtsystem UNIVA LW 1000 UNIVA … · ANLEITUNG.....