IBM Grid Computing

8/8/2019 IBM Grid Computing

1/66

2003 IBM Corporation

Anbazhagan ManiGrid Computing Competency Center

IBM India Software Lab

OverviewPresentation


2/66


Contents Becoming an On Demand Business

Grid Overview

Detailed Grid Architecture

Demo

AppendixGrid Links


3/66


Computing Evolution

Mainframe

Network-Centric

Client-Server

On Demand


4/66


An enterprise whose business processes -- integrated end-to-endacross the company and with key partners, suppliers and customers

-- can respond with speed to any customer demand, market

opportunity or external threat

An On Demand Business

Responsive

Variable

Focused

Resilient

=Profit


5/66


On Demand Operating Environment Attributes

an approachable, adaptive, integrated andan approachable, adaptive, integrated and

reliable infrastructure delivering on demandreliable infrastructure delivering on demandservices for on demand business operationsservices for on demand business operations

Virtualized Autonomic

IntegratedOpen


6/66


VirtualizedStorage

ApplicationsApplicationsProcessingProcessing

Operating System

DataData

I/O

Distributed Computing Over a Network,

Using Open Standards to Enable

Heterogeneous Operations

Grid Computing


7/66


What would it mean if your business could

Analyze the value of an investment portfolio in minutes, rather thanhours?

Significantly accelerate the drug discovery process?

Cut the design time of products in half, while reducing the instances ofdefects?

Efficiently expand and contract to meet cyclical demand?

Unite research teams around the world to take advantage of the mostup-to-date learnings?


8/66


Gateway

Hub Server Group

Local

Director

Network

Business LogicPresentation

WebSphereApplication

Server

NetscapeEnterprise

Server WebSphereApplication

Server

JDBC

HTTP

MQ

Profile

Capture

Database

Servers

Security

Gateways

DB2SecurityServers

MQMQ

ApplicationLogging

GatewayLogging

MQ MQ

SecurityClient

SNA

SNA

SNA

Back-endSystems

zSeries

ComplexIMSData

CICS

zSeries

SysplexIMSData

zSeries

SysplexIMSData

zSeries

SysplexIMS

Data

zSeries

TPF

Front-end for Web presence for financial services

Typical Financial Subsystem Configuration

Current Environment: Distributed, Heterogeneous

and Complex


9/66


Gateway

Hub Server Group

Local

Director

Network

Business LogicPresentation

WebSphereApplication

Server

NetscapeEnterprise

Server WebSphereApplication

Server

JDBC

HTTP

MQ

Profile

Capture

Database

Servers

Security

Gateways

DB2SecurityServers

MQMQ

ApplicationLogging

GatewayLogging

MQ MQ

SecurityClient

SNA

SNA

SNA

Back-endSystems

zSeries

ComplexIMSData

CICS

zSeries

SysplexIMSData

zSeries

SysplexIMSData

zSeries

SysplexIMS

Data

zSeries

TPF

Front-end for Web presence for financial services

Typical Financial Subsystem Configuration

Complexity, Total

Cost of Ownership

Technology Component

Costs, IT Utilization Rates

Total Cost of Ownership Rising


10/66


Low Infrastructure Utilization

52%N/AN/AStorage

2-5%5-10%30%Intel-based


11/66


Grid Addresses These NeedsInfrastructure Optimization

Workload Management and Consolidation

Reduced Cycle Times

Increased Access to Data and Collaboration

Federation of Data

Global Distribution

Resilient / Highly Available Infrastructure

Business Continuity

Recovery and Failover


12/66


Untapped Potential

Value is expressed relative to the ASCI White Supercomputer (12.3 Teraflops) *

* Cost of one ASCI White Supercomputer= $110M


13/66


Businesses are leveraging Grid technologies today


14/66


Infrastructure Optimization

Provide capacity for high-demandapplications

Applications that cannot be run effectively on asingle processor

New large scale applications that providestrategic business advantage

Reduce infrastructure costs

Balance workload based on business rules

Optimize for cost or throughput

Reduce resource management costs Fewer resources to manage for the same

workload


15/66


Increased Access to Data and Collaboration

Enable collaboration across organizations forbetter results

Leverage Distributed Data and Resources

Support large multi-disciplinary collaboration

Link Business Processes

Federation of Data

Both within a single organizationand between partners

Exploit Replication Services Across

EnterprisesSimulation

PricingDesign

Design

DesignAnalytics


16/66


Leverage distributed resources to balanceworkload Scheduler manages job distribution

Failover and recovery leverage distributedresources

Scheduler use policies and prioritiesto determine how to meet goals

Resilient / Highly Available Infrastructure

112

2

3

45

67

8

9

10

11

JobScheduler

JOB 1JOB 1 JOB 2JOB 2 JOB 3JOB 3JOB 1JOB 1 Recovery/

Restart


17/66


The Value of Open Standards

Networking:

The Internet

(TCP/IP)

Communications:

e-mail

(pop3,SMTP,Mime)

Information:

World-wide Web

(html, http, j2ee, xml)

Applications:

Web Services

(SOAP, WSDL, UDDI)

Distributed Computing:

Grid

(Globus -> OGSA)

Operating System:

Linux


18/66


OGSA EnabledOGSA EnabledOGSA EnabledOGSA EnabledOGSA Enabled

OGSA

Open Grid Services Architecture(OGSA)
http://www.bea.com/http://www.microsoft.com/isapi/gomscom.asp?target=/http://www.oracle.com/index.html


19/66


Professiona

lServi

Network

OGSA Enabled

Storage

OGSA Enabled

Servers

OGSA Enabled

Messaging

OGSA Enabled

Directory

OGSA EnabledFile

Systems

OGSA Enabled

Database

OGSA Enabled

Workflow

OGSA Enabled

Security

OGSA Enabled

Web Services

OGSI Open Grid Services Infrastructure

Grid ServicesSystem Management

SevicesOpen Grid Services Architecture (OGSA)

Applications

Auto

nomic

Capa

b

Architecture Framework

OGSA Structure


20/66


Architecture Framework

OGSA Enabled

OGSA Enabled

OGSA Enabled

Messaging

OGSA Enabled

Directory

OGSA Enabled

FileSystems

OGSA Enabled

Database

OGSA Enabled

Workflow

OGSA Enabled

Security

OGSA Enabled

OGSI Open Grid Services Infrastructure

Grid ServicesSystem Management

Sevices

Auto

nomic

Capa

b

OGSA

IBM

Glo

balServ

ices

Products and Services for Grids
http://www.ariba.com/index.cfmhttp://www.peoplesoft.com/corp/en/public_index.asphttp://www.sap.com/index.asphttp://www.siebel.com/http://www.cisco.com/en/US/hmpgs/index.html


21/66


Grid - a part of competitive strategy

ReducedComplexity

Higher Quality ofService

IncreasedProductivity

IncreasedEfficiency

ImprovedResiliency


22/66


Needed a scalable, resilient infrastructure for running

massive multiplayer games

Using 2 clusters of 50 IBM Xseries, WebSphere Application

Server, DB2 Universal Database, and Globus Toolkit,

running in IGS hosting facilities

Improved end-user experience

Developers avoid huge upfront costs

Demonstrated 8x increase in profitability over centralized

server model

An Example - Butterfly.netEnterprise Optimization


23/66


Grid Technical Overview


24/66


The Grid Problem Flexible, secure, coordinated resource sharingamong dynamic collections of individuals,

institutions, and resource From The Anatomy of the Grid: Enabling Scalable Virtual

Organizations

Enable communities (virtual organizations) toshare geographically distributed resources as theypursue common goals -- assuming the absenceof central location,

central control,

omniscience,

existing trust relationships.


25/66


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


26/66


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 existingtechnologies 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


27/66


The Globus Project

Close collaboration with real Grid projects inscience and industry

Development and promotion of standard Gridprotocols to enable interoperability and sharedinfrastructure

Development and promotion of standard Gridsoftware APIs and SDKs to enable portability andcode sharing

The Globus Toolkit: Open source, reference

software base for building grid infrastructure andapplications

Global Grid Forum: Development of standardprotocols and APIs for Grid computing


28/66


Some Important Definitions

Resource

Network protocol

Network enabled service

Application Programmer Interface (API)

Software Development Kit (SDK)

Syntax

Policies


29/66


Globus Architecture

Descriptive Provide a common vocabulary for use when describing Grid

systems

Guidance Identify key areas in which services are required

Prescriptive Define standard Intergrid protocols and APIs to facilitate

creation of interoperable Grid systems and portable

applications


30/66


One View of Requirements

Identity & authentication

Authorization & policy

Resource discovery

Resource characterization

Resource allocation

(Co-)reservation, workflow

Distributed algorithms

Remote data access

High-speed data transfer

Performance guarantees

Monitoring

q

Adaptationq Intrusion detection

q Resource management

q Accounting & payment

q Fault managementq System evolution

q Etc.

q Etc.

q


31/66


A Protocol-oriented View of Grid Architecture

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


32/66


Layered Grid Architecture

Application

FabricControlling things locally: Accessto, & control of, resources

ConnectivityTalking to things: communication(Internet protocols) & security

ResourceSharing single resources:negotiating access, controlling use

CollectiveCoordinating multiple resources:ubiquitous infrastructure services,

app-specific distributed services

Internet

Transport

Application

Link

Internet

ProtocolArchite

cture


33/66


Protocol, Services & API occur at each level

Languages/Frameworks

Fabric Layer

Applications

Local Access APIs and Protocols

Collective Service APIs and SDKs

Collective ServicesCollective Service Protocols

Resource APIs and SDKs

Resource ServicesResource Service Protocols

Connectivity APIs


34/66


Fabric Layer

Just what you would expect: the diverse mix ofresources that may be shared Individual computers, Condor pools, file systems, archives,

metadata catalogs, networks, sensors, etc., etc.

Few constraints on low-level technology:connectivity and resource level protocols formthe neck in the hourglass

Defined by interfaces not physical characteristics


35/66


36/66


Resource Layer Protocols & 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


37/66


Collective Layer Protocols & Services

Index servers aka metadirectory services Custom views on dynamic resource collections assembled by a

community

Resource brokers (e.g., Condor Matchmaker)

Resource discovery and allocation Replica catalogs

Replication services

Co-reservation and co-allocation services

Workflow management services Etc.


38/66


Security Services

Resources being used may be valuable & theproblems being solved sensitive

Resources are often located in distinct administrativedomains Each resource has own policies & procedures

Set of resources used by a single computation maybe large, dynamic, and unpredictable Not just client/server, requires delegation

It must be broadly available & applicable Standard, well-tested, well-understood protocols; integrated with

wide variety of tools


39/66


Security Services (GSI)

GSI-enabled

GRAM server

GSI-enabled

GRAM server

Remote processcreation requests*

* With mutual authentication

Site A(Kerberos) Site B(Unix)

Site C(Kerberos)

GSI-enabledFTP server

AuthorizeMap to local idAccess file

Remote fileaccess request*

Computer

User

Single sign-on via grid-id

& generation of proxy cred.

Or: retrieval of proxy cred.from online repository

User ProxyProxy

credential

Computer

Communication*Process

Kerberosticket

Restrictedproxy

Process

Restrictedproxy

Local idLocal id

Authorize

Map to local idCreate processGenerate credentials

Ditto


40/66


Grid Security Infrastructure (GSI)

Extensions to standard protocols & APIs Standards: SSL/TLS, X.509 & CA, GSS-API

Extensions for single sign-on and delegation

Globus Toolkit reference implementation of GSI

SSLeay/OpenSSL + GSS-API + SSO/delegation Tools and services to interface to local security

Simple ACLs; SSLK5/PKINIT for access to K5, AFS;

Tools for credential management

Login, logout, etc.

Smartcards

MyProxy: Web portal login and delegation K5cert: Automatic X.509 certificate creation


41/66


Resource Management Services

Enabling secure, controlled remote access toheterogeneous computational resources andmanagement of remote computation Authentication and authorization

Resource discovery & characterization Reservation and allocation

Computation monitoring and control

Addressed by new protocols & services GRAM protocol as a basic building block

Resource brokering & co-allocation services

GSI for security, MDS for discovery


42/66


Resource Management Services

The Grid Resource Allocation Management(GRAM) protocol and client API allows programsto be started on remote resources, despite localheterogeneity

Resource Specification Language (RSL) is usedto communicate requirements

A layered architecture allows application-specificresource brokers and co-allocators to be defined

in terms of GRAM services Integrated with Condor, PBS


43/66


Resource Management Architecture

GRAM GRAM GRAM

LSF Condor NQE

Application

RSL

Simple ground RSL

InformationService

Localresourcemanagers

RSLspecialization

Broker

Ground RSL

Co-allocator

Queries

& Info


44/66


GRAM Protocol

GRAM-1: Simple HTTP-based RPC Job request

Returns a job contact: Opaque string that can be passed between

clients, for access to job

Job cancel, status, signal

Event notification (callbacks) for state changes Pending, active, done, failed, suspended

GRAM-1.5 (U Wisconsin contribution) Add reliability improvements

Once-and-only-once submission

Recoverable job manager service

Reliable termination detection

GRAM-2: Moving to Web Services (SOAP)


45/66


GRAM Components

Grid SecurityInfrastructure

Job Manager

MDS client API callsto locate resources

Query current statusof resource

Create

RSL Library

Parse

RequestAllocate &

create processes

Process

Process

Process

Monitor &control

Site boundary

Client MDS: Grid Index Info Server

Gatekeeper

MDS: Grid Resource Info Server

Local Resource Manager

MDS client API callsto get resource info

GRAM client API statechange callbacks


46/66


Information Services

System information is critical to operation of thegrid and construction of applications What resources are available?

Resource discovery

What is the state of the grid? Resource selection

How to optimize resource use Application configuration and adaptation?

We need a general information infrastructure to

answer these questions


47/66


Grid Information Service

Provide access to static and dynamic informationregarding system components

A basis for configuration and adaptation inheterogeneous, dynamic environments

Requirements and characteristics Uniform, flexible access to information

Scalable, efficient access to dynamic data

Access to multiple information sources

Decentralized maintenance


48/66


Two classes of Information Services

Resource Description Services Supplies information about a specific resource (e.g. Globus

1.1.3 GRIS).

Aggregate Directory Services

Supplies collection of information which was gathered frommultiple GRIS servers (e.g. Globus 1.1.3 GIIS).

Customized naming and indexing


49/66


Information Protocols

Grid Resource Registration Protocol Support information/resource discovery

Designed to support machine/network failure

Grid Resource Inquiry Protocol Query resource description server for information

Query aggregate server for information

LDAP V3.0 in Globus 1.1.3


50/66


Meta-Computing Directory Service (MDS)

Use LDAP as Inquiry

Access information in a distributed directory Directory represented by collection of LDAP servers

Each server optimized for particular function

Directory can be updated by: Information providers and tools

Applications (i.e., users)

Backend tools which generate info on demand

Information dynamically available to tools andapplications


51/66


Grid Resource Information Service

Server which runs on each resource Given the resource DNS name, you can find the GRIS server (well

known port = 2135)

Provides resource specific information

Much of this information may be dynamic Load, process information, storage information, etc. GRIS gathers this information on demand

White pages lookup of resource information Ex: How much memory does machine have?

Yellow pages lookup of resource options Ex: Which queues on machine allows large jobs?


52/66


Grid Index Information Service

GIIS describes a class of servers Gathers information from multiple GRIS servers

Each GIIS is optimized for particular queries Ex1: Which machines are >16 process SGIs?

Ex2: Which storage servers have >100Mbps bandwidth to host X?

Akin to web search engines

Organization GIIS The Globus Toolkit ships with one GIIS

Caches GRIS info with long update frequency Useful for queries across an organization that rely on relatively static

information (Ex1 above)

Can be merged into GRIS

D t M t S i


53/66


Data Management Services

Two major Data Grid components:

1. Data Transport and Access Common protocol

Secure, efficient, flexible, extensible data movement

Family of tools supporting this protocol

2. Replica Management Architecture Simple scheme for managing:

multiple copies of files

collections of files

G idFTP


54/66


GridFTP

Why FTP? Ubiquity enables interoperation with many commodity tools

Already supports many desired features, easily extended to

support others

Well understood and supported

We use the term GridFTP to refer to Transfer protocol which meets requirements

Family of tools which implement the protocol

Note GridFTP > FTP

Note that despite name, GridFTP is not restricted tofile transfer!

R li M t


55/66


Replica Management

Maintain a mapping between logical names for filesand collections and one or more physical locations

Important for many applications Example: CERN data

Multiple petabytes of data per year

Copy of everything at CERN (Tier 0)

Subsets at national centers (Tier 1)

Smaller regional centers (Tier 2)

Individual researchers will have copies

Replica Manager Components


56/66


Replica Manager Components

Replica catalog definition LDAP object classes for representing logical-to-physical

mappings in an LDAP catalog

Low-level replica catalog API globus_replica_catalog library

Manipulates replica catalog: add, delete, etc. High-level reliable replication API

globus_replica_manager library

Combines calls to file transfer operations and calls to low-level

API functions: create, destroy, etc.

Globus Overall View


57/66


Globus Overall View

Local ServicesCondor

LSF

MPI

PBS NQE Solaris

UDPTCP

AIXLinux

Applications

Core Services

I/O

MetacomputingDirectory Svcs

HeartBeatMonitor

GRAM

GASSGlobal Security

Interface

Nexus

High-Level Services & ToolsGlobusView Testbed Status

DUROC MPI Condor HPC++ Nimrod/G globusrun

secure messaging repositories

security services

cluster services

services hosting environment

resource mgmt

What is evolving Web Services & Grid


58/66


What is evolving Web Services & Grid

Web Services and Grid try to solve similar problems indifferent realms:

Defining an open distributed computing platform

Assuring interoperability

Dealing with heterogeneous platforms, protocols and

applications

In the business and scientific computing areas


59/66


60/66


Hosting Environment

Open Grid Infrastructure (OGSI)

Implementation

Service Data AccessLifetime Management

GridService(required)

Other Interfaces(Optional)

Service creation (Factory)Service discovery (Registry)NotificationHandle Management

Other functions e.g.WorkflowAuditingResource Management

Element

ElementElementService Data

Grid ServiceHandle

Anatomy of a Grid Service


61/66


Hardware

Operating System

Other Middleware

Hosting Environment

Open Grid Infrastructure (OGSI)

Implementation

Abstract serviceinterface remains the

same

Grid Service Implementation Independence


62/66


63/66


Hardware

Operating System

Other Middleware

Hosting Environment - J2EE

Open Grid Infrastructure (OGSI)Grid Service Implementation - Examples

File TransferService

FileSystem

Storage System (NAS/SAN)

Implementation

Abstract serviceinterface remains the

same

Database (DB2)


64/66


OGSA portTypesPortType Name Description

GridService encapsulates the root behavior of the service model

HandleResolver mapping from a GSH to a GSR

NotificationSource allows clients to subscribe to notification messages

NotificationSubscription defines the relationship between a single NotificationSourceand NotificationSink pair

NotificationSink defines a single operation for delivering a notificationmessage to the service instance that implements theoperation

Factory standard operation for creation of Grid service instances

ServiceGroup allows clients to maintain groups of services

ServiceGroupRegistration allows Grid services to be added and removed from aServiceGroup

ServiceGroupEntry defines the relationship between a Grid service and itsmembership within a ServiceGroup


65/66


Grid Vision

Partner Grid

across multiple orgs

Grid Vision

Enterprise Grid

inter-dept sharing within orgs

Service Grid

supported by xSPs

Grid


66/66


Grid Computing is real TODAY & very important for everycompany!Grids will be an integral part of your organizationson-demand infrastructure.

Documents

IBM Grid Computing