presentation talk

8/8/2019 Presentation Talk

1/62

128th Nov 2003 GRID COMPUTING

GRID Computing: On the path

to utility computing

-Dr. Srinivas Padmanabhuni

SETLabs
http://192.168.206.10/home.asp


2/62


Agenda

Why GRID?

What is GRID?

Where GRID applies? How is GRID constructed?

OGSA = Standards based GRID

Conclusions and Call For Action
http://192.168.206.10/home.asp


3/62


Why GRID?
http://192.168.206.10/home.asp


4/62


Todays IT architecture is complex and

unmanageable

access tier

web tier

application tier

database tier

edge routers

routingswitches

authentication, DNS,

intrusion detect, VPNweb cache

1st level firewall

2nd level firewall

load balancingswitches

webservers

web page storage(NAS)

databaseSQL servers

storage areanetwork(SAN)

applicationservers

files(NAS)

switches

switches

internet

internetinternet

internet
http://192.168.206.10/home.asp


5/62


Moores Law for Computing Speed..

Source: IntelSource: Intel

0.10.1

11

1010

100100

1,0001,000

10,00010,000

19701970 19801980 19901990 20002000 20102010

MHzMHz

Pentium 4 ProcessorPentium 4 Processor

Pentium III ProcessorPentium III ProcessorPentium II ProcessorPentium II Processor

Pentium ProcessorPentium Processor486 Processor486 Processor

386 Processor386 Processor286286

80868086

80858085

80808080

40044004

10 GHz by 201010 GHz by 2010
http://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asp


6/62


Network is growing even faster

Network vs. computer performanceComputer speed doubles every 18 months

Network speed doubles every 9 months

Difference = order of magnitude per 5 years

1986 to 2000

Computers: x 500

Networks: x 340,000

2001 to 2010Computers: x 60

Networks: x 4000

Moores Law vs. storage improvements vs. optical improvements. Graph from Scientific American

(Jan-2001) by Cleo Vilett, source Vined Khoslan, Kleiner, Caufield and Perkins.
http://192.168.206.10/home.asp


7/62728th Nov 2003 GRID COMPUTING

Putting together network and computing

speed rates of growth..1,000,000,000,000

100,000,000,000

1970

Moore/

Transistors

Gilder/

Bandwidth

Metcalf/

Network

Nodes

10,000,000,000

1,000,000,000

100,000,000

10,000,000

1,000,000100,000

10,000

1,000

100

10

11975 1980 1985 1990 1995 2000 2005 2010

2,300 6,000 29,000 275,000 1.2 mil 5.5 mil 42 mil 252 mil 1.344 bil

50 50 56 1,544 45,000 145,000 10 mil 2.43 bil 200.49 bi l

4 111 200 10,000 300,000 1 mil 140 mil 3.5 bil 300 bil

Moores Law. Transistors on a single chip

doubles approximately every1824 months.

Gilders Law.

Aggregate bandwidth triplesapproximately every year.

Metcalfes Law. The value of a network may

grow exponentially with thenumber of participants.

Source: Cambridge Energy Resource Associates10616-17
http://192.168.206.10/home.asphttp://192.168.206.10/home.asp



Low Infrastructure Utilization in todays IT

architecture..

24-hourPeriodUtilization

Prime-shiftUtilization

Peak-hour

Utilization

52%N/AN/AStorage

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

based



To summarize

Moores law improvements in computing produce highlyfunctional end-systems

The Internet and burgeoning wired and wireless provideuniversal connectivity

Collaborative modes of working and problem solvingemphasize teamwork, computation Network exponentials produce dramatic changes in

geometry and geography Standards for application to application communication

getting universal acceptance Pressure on effective utilization of resources inenterprises due to current low utilization rates..
http://192.168.206.10/home.asp



Enter on-demand computing and

related concepts On-Demand Computing: A conglomerate of multiple concepts

to enable respond to elastic computing demand using inelastic computingresources IBM calls it e-business On-Demand, Sun calls it N1, HP calls it adaptive

management, Microsoft calls it the Dynamic Systems Initiative

Utility Computing: Computing Resources made available (likeelectricity etc.) as needed, and charged on usage Autonomic Computing: A self-managing computing model

where computing resources are controlled without human intervention,includes self-healing, self-protecting, self-optimizing, and self-configuringfeatures.

GRID Computing: Pooling of multiple resources coordinated toappear as a single virtual resource to the external world
http://192.168.206.10/home.asp



What is GRID?
http://192.168.206.10/home.asp



The pigeons showed that..

Unity is Strength

A story first...
http://192.168.206.10/home.asp



Defining GRID..

"A computational grid is a hardware and software

infrastructure that provides dependable, consistent,

pervasive, and inexpensive access to high-end

computational capabilities.-The Grid: Blueprint for a New Computing Infrastructure; Morgan

Kaufmann; San Francisco; 1999

Flexible, secure, coordinated resource sharing

among dynamic collections (VOs) of individuals,institutions, and resources

-The Anatomy of the Grid: Enabling Scalable Virtual Organizations
http://192.168.206.10/home.asp



What constitutes GRID?

Coordination of resources that are not subject tocentralized control

Heterogeneous mix of resources

Loosely Coupled connections ..

Flexible and Dynamic Collection.. Usage of standard, open, general-purpose protocols

and interfaces

Virtualization of resources to create VOs..

Non-Trivial quality of service Resources may be processors, computers, clusters,

data, databases, scientific instruments, displays, etc..
http://192.168.206.10/home.asp



What is not a GRID?

A cluster of homogeneous machines..

A network attached storage device..

A standalone scientific instrument..

A huge standalone supercomputer..

A Massively Parallel Processing computer.. A multi-processor computer..

A high-speed network..

A homogeneous cluster of computers

Each is an important component of a Grid,

but by itself does not constitute a Grid
http://192.168.206.10/home.asp



A Picture of GRID
http://192.168.206.10/home.asp



History of the GRID

1986 - First Connection Machine CM-1 1987 - First CM-2 1988 - Condor project begins 1990 - PVM project begins 1991 - WWW created by Tim Berners-Lee at CERN 1991 - UK JANet goes IP 1991 - nCUBE running Oracle PS achieves 1,037 Tps (2x mainframe

speed, 0.05x cost) 1992 - CODINE project underway 1993 - First Cray T3D

1993 Legion, a GRID Object model project launch 1994 - Nimrod project launched Jul 1996 - SETI@home launched 1997 - Globus under development 1997 - UNICORE project launch Mar 1997 - Condor deployed at NCSA 1997 - Entropia Inc founded to commercialise PC cycle scavenging

Sep 1997 - Building a computational Grid workshop, ArgonneNational Lab

Oct 1997 - SRB v1.0 released

Jul 1998 - Foster/Kesselman: The GRID book Aug 1998 - Applied Meta Inc commercialises Legion Oct 1998 - Globus v1.0.0 released Jun 1999 - Grid Forum 1 Jan 2000 - UNICORE stage 2 launch Jul 2000 - SUN buys Gridware Inc Grid Engine Oct 2000 - NASA IPG prototype completed

Jan 2001 - EU DataGrid project launch

Mar 2001 - Global Grid Forum 1

Jul 2001 - UK e-Science Programme launch

Aug 2001 - US TeraGrid project launch

Nov 2001 - GEANT, the pan-EU gigabit network,

activated

2002

Dozens of application communities &projects in scientific and technical

computing

Major infrastructure deployments

De facto standard technology: Globus

ToolkitTM

Growing industrial interest

Global Grid Forum: ~1000 people,

30+ countries Jan 2002 - OGSA announced

Feb 2002 - OGSA-DAI project launch

Jun 2002 - NEC Earth Simulator achieves

35 Tflops

2003

Enterprise Attention around GRID

GT3.0 based on OGSA released.

Commercial Offerings from Vendors (IBMetc).
http://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asp



In summary..

GRID technology refers to the enablingtechnology for creating a large and powerfulVIRTUAL ORGANIZATION out of a pool ofheterogeneous resources

The connections are loosely coupled

The resources are heterogeneous ranging fromcomputers to databases to instruments to

networks Non-Trivial Quality of Service offered by the VO

Composition of VO is dynamic and flexible
http://192.168.206.10/home.asp



Where GRID applies?
http://192.168.206.10/home.asp



What GRID computing can do..

Improve Resource Utilization Exploit underutilized resources (CPU, storage)

Improved load balancing

Provide high computing power Simulate Parallel CPU capacity

Pool Individual computing power

Provide additional storage

Pool individual storage units Provide additional bandwidth

Pool bandwidth from multiple units

Enhanced collaboration among multiple stakeholders Beyond the enterprise

Over a geographical spread (e.g. Collaborative research)

Enhanced access to other resources Software, Licenses, Equipment

Reliability based on Software

IT effectiveness Ease of management of IT infrastructure

Ability to execute Parallelizable applications
http://192.168.206.10/home.asp


21/62


Domains where GRID can be

applied Scientific Domain

GriPhyN (US Grid Physics Network for Data-intensiveScience) for Elementary particle physics, gravitationalwave astronomy, optical astronomy (digital sky survey)

DataGrid (led by CERN) for Analysis of data fromscientific exploration

Financial Domain Analytics (Risk Analysis and Modeling)

Portfolio Rebalancing

Treasury and Federal Banking

Life Sciences and Pharma Data Mining for Bioinformatics

Drug Discovery

Corporate Applications Business Intelligence

IT Effectiveness

Digital Content Distribution

Automotive Collaborative Design Combat Systems Design

Stealth Design of defense systems

Government Tax Processing Census applications Online Processing

Atmospheric Science Imagery and Geo-Spatial

Intelligence Weather /Ocean Forecasting

Defense and Security Nuclear weapons advanced

simulation and modeling Threat Analysis Cryptanalysis

Weapons Performance Analysis Economics

Econometric modeling
http://192.168.206.10/home.asp


22/62


A typical use case for data mining

in Bio-Informatics

MiningResource Bio Data Base 1

StorageResource

Bio Data Base 2

Bio-M

iningApplicatio

n

Request for a

data mining resource

Request for a

Transient storage

resource

Search Request

Search RequestStore Intermediate Result

Store Intermediate Result
http://192.168.206.10/home.asp


23/62


How is GRID constructed?
http://192.168.206.10/home.asp


24/62


Overall GRID Architecture

Application

Collective

Resource

Connectivity

Fabric

Application

TransportInternet

Link

GRID

Internet

Source: The Anatomy of the GRID, Foster, Kesselman and Teucke
http://192.168.206.10/home.asp


25/62


Fabric Layer

Fabric layer: Provides the resources to which sharedaccess is mediated by Grid protocols.

Example: computational resources, storage systems,catalogs, network resources, and sensors.

Fabric components implement local, resourcespecific operations.

Richer fabric functionality enables moresophisticated sharing operations.

Sample resources: computational resources, storageresources, network resources, code repositories,catalogs.
http://192.168.206.10/home.asp


26/62


Connectivity Layer

Communicating easily and securely.

Connectivity layer defines the corecommunication and authentication protocols

required for grid-specific network functions. This enables the exchange of data betweenfabric layer resources.

Support for this layer is drawn from TCP/IPs IP,

TCL and DNS layers. Authentication solutions: single sign on, etc.
http://192.168.206.10/home.asp


27/62


Resources Layer

Resource layer defines protocols, APIs, and SDKs forsecure negotiations, initiation, monitoring control, accountingand payment of sharing operations on individual resources.

Two protocols information protocol and managementprotocol define this layer.

Information protocols are used to obtain the informationabout the structure and state of the resource, ex:configuration, current load and usage policy.

Management protocols are used to negotiate access to theshared resource, specifying for example qos, advanced

reservation, etc.
http://192.168.206.10/home.asp


28/62


Collective Layer

Coordinating multiple resources.

Contains protocols and services that captureinteractions among a collection of resources.

It supports a variety of sharing behaviors withoutplacing new requirements on the resources beingshared.

Sample services: directory services, coallocation,brokering and scheduling services, data replicationservice, workload management services,collaboratory services.
http://192.168.206.10/home.asp


29/62


Applications Layer

These are user applications that operatewithin VO environment.

Applications are constructed by calling upon

services defined at any layer. Each of the layers are well defined using

protocols, provide access to useful services.

Well defined APIs also exist to work with these

services.
http://192.168.206.10/home.asp


30/62


Implementations

Till date mostly proprietary

implementations

Globus (Open Source) Toolkit the most

popular one

OGSA (Open Grid Services Architecture),

a move for open standards for grid

Globus Toolkit 3.0 recently released

OGSA compliant
http://192.168.206.10/home.asp


31/62


User

Userprocess #1

Proxy

Authenticate &create proxycredential

GSI(Grid

ecurityInfrastruc-

ture)

Gatekeeper(factory)

Reliable

remoteinvocation

GRAM(Grid Resource Allocation & Management)

Reporter(registry +discovery)

Userprocess #2Proxy #2

Create process Register

Globus Toolkit 2.0 : Proprietary

Implementation Grid protocols (GSI, GRAM, ) enable resource sharing within

virtual orgs; toolkit provides reference implementation ( = Globus

Toolkit services)

q Protocols (and APIs) enable other tools and services

for membership, discovery, data mgmt, workflow,

Other service(e.g. GridFTP)

Other GSI-authenticatedremote service

requests

GIIS: GridInformationIndex Server(discovery)

MDS-2(Monitor./Discov. Svc.)

Soft stateregistration;

enquiry

Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
http://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asphttp://192.168.206.10/home.asp


32/62


OGSA = Standards for GRIDImplementations
http://192.168.206.10/home.asp


33/62


Open Grid Services Architecture

Based on Service oriented Architecture

virtualize resources

unify resources/services/information

Leverages useful Web Services properties

Standards for service description and discovery

Leverage commercial efforts in Web Services

Leverages existing grid systems properties

Service Semantics

Lifecycle management

Reliability and Security models

Resource Management Authorization etc.

Provides a unifying architecture for computational Grids
http://192.168.206.10/home.asp


34/62


Web Services A web service is a software application identified by a URI, whose interfaces and bindings are capable

of being defined, described and discovered by XML artifacts. A web service supports direct interaction

with other software agents using XML based messages exchanged via internet based protocols Source:WS Architecture Working Group W3C

Web Services are software applications based on openstandards. These applications can be :

Published,

Searched,

Located, and

Invoked by other applications on internet/intranet/extranet

Strict adherence to standards makes it easy for one

application to talk to another

XML is the lingua-franca of communication
http://192.168.206.10/home.asp


35/62


OGSA is an implementation of a Service Oriented

Architecture (SOA)

Service Providers

Provide service functionality which is

published by the Service discovery agency

Discovery Agency

Maintain a registry of services, their interface

descriptions, provider information and

invocation methods

Service Requestors

Locate required service from the services

published by the Discovery agency, and get

all the information for binding to the service

from the agency

SERVICE

PROVIDER

DISCOVERY

AGENCY

SERVICE

REQUESTORFIND

PUBLI

SH

BIND
http://192.168.206.10/home.asp


36/62


The Open Grid Services

Architecture

Open Grid Services Infrastructure

OGSA services: registry,

authorization, monitoring, data

access, management, etc., etc.

TransportProtocolHosting EnvironmentHosting Environment

Host. Env. & Protocol Bindings

OGSAsche

mas

More specialized &

domain-specific

services

Other

schemas

Web Services

O G id S i A hit t
http://192.168.206.10/home.asp


37/62


Web Services: Basic Functionality

OGSA

Open Grid Services Architecture

- Detailed

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 DataIntegration

Structured Data Access

Structured DataRelational XML Semi-structured

Transformation

Registry

Job Submission

Data Transport Resource Usage

Banking

Brokering Workflow

Authorisation
http://192.168.206.10/home.asp


38/62


Concepts in OGSA

NamingGlobally & uniquely identify a grid service instance by a GSH (Grid Service Handler in the form ofa URI).

GSH is a URI

(http://192.168.0.1:8080/ogsa/services/base/multirft/MultiFileRFTFactoryService)

Can be thought of as a network pointer to a grid service but does not provide enough information to

access a grid service.

GSH needs to be resolved to a GSR in order to access a grid service instance.

GSR is A temporal, binding specific end-point that provide access to a grid service instance.

GSR is a WSDL document that describe how to reach a grid service instance

Factories

Create new grid service instances and maintain a group of service data elements which can bequeried. A factory have a associated registry to keep track of instances and enable discovery.

Instances

Client communicate with Grid service instance via GSR (Grid Service Reference). GSH ismapped to the appropriate GSR via the registry.

Stateful Web Services

A grid service instance has a state.

A run time view of Open Grid Services
http://192.168.206.10/home.asp


39/62


Serviceregistry

Servicerequestor

(e.g. userapplication)

Servicefactory

CreateService

Grid ServiceHandle

Resourceallocation

Serviceinstances

RegisterService

Servicediscovery

Interactions standardized using WSDL

Service dataKeep-alivesNotificationsServiceinvocation

Authentication& authorizationare applied toall requests

A run-time view of Open Grid Services

Infrastructure (OGSI)
http://192.168.206.10/home.asp


40/62


XML definition for a WSDL GSR

XML definition for a GSH


41/62


WSDL: Recap Data Types

Endpoint

HTTP Binding

Abstract Interface
http://192.168.206.10/home.asp


42/62


GWSDL: Differences and Example

Differences

Interface InheritanceAbility to describe additional information elements with interface definitions

serviceData special elements for life cycle (can be static or dynamic)Typical attributes: goodFrom, goodUntil, availableUntil

Example:
http://192.168.206.10/home.asp


43/62


OGSI Grid Service Behavior portTypesPortType Name Interface Description

and OperationsService Data elements

defined by this

portType

Default service data(static) values

GridService (required) All Grid services implementsthis interface andprovides theseoperations andbehaviors. OperationsfindServiceDatasetServiceData

requestTerminationTimeAfterrequestTerminationTimeBeforedestroy

InterfacesserviceDataNamefactoryLocatorGridServiceHandleGridServiceRefrencefindServiceDataExtensibility

setServiceDataExtensibilityterminationTime

Factory (optional) To create a new Grid service.

Operations1.createService

1.createServiceExtensibility None

HandleResolver (optional) A service providedmechanism to resolve aGSH to a GSROperations1.FindByHandle

handleResolverScheme None

G idS i tT
http://192.168.206.10/home.asp


44/62


GridService portType

Operations

Operation Description

findServiceData Query information about the Gridservice instance

setServiceData Modify service data values

requestTerminationAfter Specify earliest desiredtermination time

requestTerminationBefore Specify latest desired terminationtime

destroy Terminate Grid service instance


45/62


OGSI Grid Service Notification portTypes

PortType Name Interface Description

and Operations

Service Data elements

defined by thisportType

Default service data

(static) values

NotificationSource (optional) This enables a client tosubscribe for notificationbased on a service datavalue change.Operations1.subscribe

notifiableServiceDataNamesubscribeExtensibility

NotificationSink (optional) Implementing this interfaceenables a Grid serviceinstance to receivenotification messagesbased on a subscription.Operations1.deliverNotification

None None

NotificationSubscription(optional)

Calling a subscription of aNotification Sourceresults in the creation ofa subscription Gridservice.OperationsNone defined

subscriptionExpressionsinkLocator

None

OGS G S G
http://192.168.206.10/home.asp


46/62


OGSI Grid Service Grouping

BehaviorPortType Name Interface Description

and OperationsService Data elements

defined by thisportType

Default service data(static) values

ServiceGroup (optional) An abstract interface to represent agrouping of zero or moreservices. This interface extendsthe GridService portType.OperationsNone defined but can useoperations defined in GridService

portType.

MembershipContentRuleentry

None

ServiceGroupRegistration (optional) This interface extends the ServiceGroupinterface and provides operationsto manage a ServiceGroupincluding adding/delete a serviceto/from a group.Operationsaddremove

addExtensibilityremoveExtensibility

ServiceGroupEntry (optional) This is a representation of an individualentry of a ServiceGroup and iscreated onServiceGroupRegistration "add".Each entry contains a servicelocator to a member Grid serviceand information about themember service as defined bythe Service group membershiprule (content).Operations

None defined

memberServiceLocatorcontent
http://192.168.206.10/home.asp


47/62


A DBaccess Grid service will support at least twoportTypes

GridService

DBaccess

Each has service data GridService: basic introspection information, lifetime,

DBaccess: database type, query languages supported,

current load, ,

Maybe other portTypes as well

E.g., NotificationSource

GridService DBaccess

DB info

Name, lifetime, etc.

Example:

Use Case Revisited: Database Service for BioInformatics

http://192.168.206.10/home.asp


48/62


Transient Database Service

GridService

DBaccessFactory

Factory info

Instance name, etc.

GridService Registration

Registry info

Instance name, etc.

GridService DBaccess

DB info


GridService

DBaccess

DB info


What servicescan you create?

What databaseservices exist?

Create a databaseservice


E l


49/62


Example:

Data Mining for Bioinformatics

UserApplication

BioDB n

Storage Service Provider

MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.

Compute Service Provider

I want to createa personal database

containing data one.coli metabolism

.

.

.

Database

Factory


E l
http://192.168.206.10/home.asphttp://192.168.206.10/home.asp


50/62


Example:


UserApplication

BioDB n


MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Find me a datamining service, andsomewhere to store

data

Database

Factory


E l
http://192.168.206.10/home.asp


51/62


Example:


UserApplication

BioDB n


MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

GSHs for Miningand Databasefactories

Database

Factory


E l
http://192.168.206.10/home.asp


52/62


Example:


UserApplication

BioDB n


MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Create a data miningservice with initial

lifetime 10

Create adatabase with initiallifetime 1000

Database

Factory


E l
http://192.168.206.10/home.asp


53/62


Example:


UserApplication

BioDB n


Database

Factory

MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Database

Miner

Create a data miningservice with initial

lifetime 10

Create adatabase with initial

lifetime 1000


E ample
http://192.168.206.10/home.asp


54/62


Example:


UserApplication

BioDB n


Database

Factory

MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Database

Miner

Query

Query


Example:
http://192.168.206.10/home.asp


55/62


Example:


UserApplication

BioDB n


Database

Factory

MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Database

Miner

Query

Query

Keepalive

Keepalive


Example:
http://192.168.206.10/home.asp


56/62


Example:


UserApplication

BioDB n


Database

Factory

MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Database

MinerKeepalive

KeepaliveResults

Results


Example:
http://192.168.206.10/home.asp


57/62


Example:


UserApplication

BioDB n


Database

Factory

MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Database

Miner

Keepalive


Example:
http://192.168.206.10/home.asp


58/62


Example:


UserApplication

BioDB n


Database

Factory

MiningFactory

CommunityRegistry

DatabaseService

BioDB 1

DatabaseService

.

.

.


.

.

.

Database

Keepalive

http://192.168.206.10/home.asp


59/62


Conclusionsand

Call For Action
http://192.168.206.10/home.asp


60/62


Conclusions

GRID is based on idea of virtualization of a pool ofheterogeneous resources into one scalable virtualorganization

GRID provides enhanced throughput, resource

utilization, non-trivial QoS, leveraging heterogeneousresources

GRID is suitable for computationally intensive and otherresource intensive works across multiple verticals

GRID computing is REAL today and businesses are

leveraging GRID OGSA, the standard for GRID, based on web services

will be mainstream and will enhance penetration of GRID
http://192.168.206.10/home.asp


61/62


Call for Action

Read about GRID..

Download GLOBUS Toolkit 3.0..

Identify potential application areas of Pilot

for GRID

Run Pilot GRIDs with a dedicated set of

services for focused problems

Build Solutions and Take to Clients..

GRID COMPUTING IS REAL TODAY
http://192.168.206.10/home.asp


62/62

THANKS
http://192.168.206.10/home.asp

presentation talk

Documents