28th Nov 2003 GRID COMPUTING 1
GRID Computing: On the path to utility computing
-Dr. Srinivas Padmanabhuni
SETLabs
28th Nov 2003 GRID COMPUTING 2
Agenda
• Why GRID?
• What is GRID?
• Where GRID applies?
• How is GRID constructed?
• OGSA = Standards based GRID
• Conclusions and Call For Action
28th Nov 2003 GRID COMPUTING 4
Today’s IT architecture is complex and unmanageable…
access tier
web tier
application tier
database tier
edge routers
routingswitches
authentication, DNS,intrusion detect, VPN
web cache1st level firewall
2nd level firewall
load balancingswitches
web servers
web page storage(NAS)
databaseSQL servers
storage areanetwork(SAN)
applicationservers
files(NAS)
switches
switches
internetinternetinternetinternet
28th Nov 2003 GRID COMPUTING 5
Moore’s 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
8080808040044004
10 GHz by 201010 GHz by 2010
28th Nov 2003 GRID COMPUTING 6
Network is growing even faster…
• Network vs. computer performance–Computer 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 2010–Computers: x 60–Networks: x 4000
Moore’s Law vs. storage improvements vs. optical improvements. Graph from Scientific American (Jan-2001) by Cleo Vilett, source Vined Khoslan, Kleiner, Caufield and Perkins.
28th Nov 2003 GRID COMPUTING 7
Putting together network and computing speed rates of growth..
1,000,000,000,000
100,000,000,000
1970
Moore/Transistors
Gilder/Bandwidth
Metcalf/NetworkNodes
10,000,000,000
1,000,000,000
100,000,000
10,000,000
1,000,000
100,000
10,000
1,000
100
101
1975 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 bil
4 111 200 10,000 300,000 1 mil 140 mil 3.5 bil 300 bil
• Moore’s Law. – Transistors on a single chip
doubles approximately every 18–24 months.
• Gilder’s Law. – Aggregate bandwidth triples
approximately every year.
• Metcalfe’s Law. – The value of a network may
grow exponentially with the number of participants.
Source: Cambridge Energy Resource Associates10616-17
28th Nov 2003 GRID COMPUTING 8
Low Infrastructure Utilization in today’s IT architecture..
24-hour Period Utilization
Prime-shift Utilization
Peak-hour Utilization
52%N/AN/AStorage
2-5%5-10%30%Intel-based
<10%10-15%50-70%UNIX
60%70%85-100%Mainframes
Source: IBM Scorpion White Paper: Simplifying the Corporate IT Infrastructure, 2000
28th Nov 2003 GRID COMPUTING 9
To summarize…
• Moore’s law improvements in computing produce highly functional end-systems
• The Internet and burgeoning wired and wireless provide universal connectivity
• Collaborative modes of working and problem solving emphasize 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 in enterprises due to current low utilization rates..
28th Nov 2003 GRID COMPUTING 10
Enter on-demand computing and related concepts…
• On-Demand Computing: A conglomerate of multiple concepts to enable respond to elastic computing demand using inelastic computing resources
– 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 (like
electricity 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-configuring features.
• GRID Computing: Pooling of multiple resources coordinated to appear as a single virtual resource to the external world
28th Nov 2003 GRID COMPUTING 12
The pigeons showed that..Unity is Strength
A story first...
28th Nov 2003 GRID COMPUTING 13
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
28th Nov 2003 GRID COMPUTING 14
What constitutes GRID?
– Coordination of resources that are not subject to centralized 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..
28th Nov 2003 GRID COMPUTING 15
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
28th Nov 2003 GRID COMPUTING 17
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, Argonne National 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 (IBM etc).
28th Nov 2003 GRID COMPUTING 18
In summary..
• GRID technology refers to the enabling technology for creating a large and powerful “VIRTUAL ORGANIZATION” out of a pool of heterogeneous resources
• The connections are loosely coupled• The resources are heterogeneous ranging from
computers to databases to instruments to networks
• Non-Trivial Quality of Service offered by the VO• Composition of VO is dynamic and flexible
28th Nov 2003 GRID COMPUTING 20
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
28th Nov 2003 GRID COMPUTING 21
Domains where GRID can be applied…
• Scientific Domain– GriPhyN (US Grid Physics Network for Data-
intensive Science) for Elementary particle physics, gravitational wave astronomy, optical astronomy (digital sky survey)
– DataGrid (led by CERN) for Analysis of data from scientific 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
28th Nov 2003 GRID COMPUTING 22
A typical use case for data mining in Bio-Informatics
MiningResource Bio Data Base 1
StorageResource
Bio Data Base 2
Bio-M
ining A
pplication
Request for a data mining resource
Request for a Transient storage resource
Search Request
Search Request Store Intermediate Result
Store Intermediate Result
28th Nov 2003 GRID COMPUTING 24
Overall GRID Architecture
Application
Collective
Resource
Connectivity
Fabric
Application
Transport
InternetLink
GRIDInternet
Source: The Anatomy of the GRID, Foster, Kesselman and Teucke
28th Nov 2003 GRID COMPUTING 25
Fabric Layer• Fabric layer: Provides the resources to which shared
access is mediated by Grid protocols.• Example: computational resources, storage
systems, catalogs, network resources, and sensors.• Fabric components implement local, resource
specific operations.• Richer fabric functionality enables more
sophisticated sharing operations.• Sample resources: computational resources,
storage resources, network resources, code repositories, catalogs.
28th Nov 2003 GRID COMPUTING 26
Connectivity Layer
• Communicating easily and securely.• Connectivity layer defines the core
communication and authentication protocols required for grid-specific network functions.
• This enables the exchange of data between fabric layer resources.
• Support for this layer is drawn from TCP/IP’s IP, TCL and DNS layers.
• Authentication solutions: single sign on, etc.
28th Nov 2003 GRID COMPUTING 27
Resources Layer• Resource layer defines protocols, APIs, and SDKs for
secure negotiations, initiation, monitoring control, accounting and payment of sharing operations on individual resources.
• Two protocols information protocol and management protocol define this layer.
• Information protocols are used to obtain the information about the structure and state of the resource, ex: configuration, current load and usage policy.
• Management protocols are used to negotiate access to the shared resource, specifying for example qos, advanced reservation, etc.
28th Nov 2003 GRID COMPUTING 28
Collective Layer
• Coordinating multiple resources.• Contains protocols and services that capture
interactions among a collection of resources.• It supports a variety of sharing behaviors without
placing new requirements on the resources being shared.
• Sample services: directory services, coallocation, brokering and scheduling services, data replication service, workload management services, collaboratory services.
28th Nov 2003 GRID COMPUTING 29
Applications Layer
• These are user applications that operate within 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.
28th Nov 2003 GRID COMPUTING 30
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
28th Nov 2003 GRID COMPUTING 31
User
Userprocess #1
Proxy
Authenticate & create proxy
credential
GSI(Grid
Security Infrastruc-
ture)
Gatekeeper(factory)
Reliable remote
invocation
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)
Protocols (and APIs) enable other tools and services for membership, discovery, data mgmt, workflow, …
Other service(e.g. GridFTP)
Other GSI-authenticated remote service
requests
GIIS: GridInformationIndex Server (discovery)
MDS-2(Monitor./Discov. Svc.)
Soft stateregistration;
enquiry
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 32
OGSA = Standards for GRID Implementations
28th Nov 2003 GRID COMPUTING 33
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
28th Nov 2003 GRID COMPUTING 34
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 open standards. 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 anotherXML is the lingua-franca of communication
28th Nov 2003 GRID COMPUTING 35
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
SERVICEPROVIDER
DISCOVERY AGENCY
SERVICEREQUESTOR
FIND
PU
BLI
SH
BIND
28th Nov 2003 GRID COMPUTING 36
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
OG
SA
schem
as
More specialized &domain-specific
services
Other
schemas
Web Services
28th Nov 2003 GRID COMPUTING 37
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
28th Nov 2003 GRID COMPUTING 38
Concepts in OGSA
• NamingGlobally & uniquely identify a grid service instance by a GSH (Grid Service Handler in the form of a URI). <for example>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 be queried. A factory have a associated registry to keep track of instances and enable discovery.
• InstancesClient communicate with Grid service instance via GSR (Grid Service Reference). GSH is mapped to the appropriate GSR via the registry.
• Stateful Web ServicesA grid service instance has a state.
28th Nov 2003 GRID COMPUTING 39
Service registry
Service requestor (e.g. user application)
Service factory
Create Service
Grid Service Handle
Resource allocation
Service instances
Register Service
Service discovery
Interactions standardized using WSDL
Service data Keep-alives Notifications Service invocation
Authentication & authorization are applied to all requests
A run-time view of Open Grid ServicesInfrastructure (OGSI)
28th Nov 2003 GRID COMPUTING 40
XML definition for a WSDL GSR
XML definition for a GSH
<targetNamespace = “http://www.gridforum.org/namespaces/2003/03/OGSI”
<xsd:element name="handle" type="ogsi:HandleType"/>
<xsd:simpleType name="HandleType">
<xsd:restriction base="xsd:anyURI"/>
</xsd:simpleType>
targetNamespace = http://www.gridforum.org/namespaces/2003/03/OGSI”
<xsd:complexType name="WSDLReferenceType">
<xsd:complexContent>
<xsd:extension base="ogsi:ReferenceType">
<xsd:sequence>
<xsd:element ref="wsdl:definitions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
28th Nov 2003 GRID COMPUTING 41
WSDL: Recap Data Types
Endpoint
HTTP Binding
Abstract Interface
28th Nov 2003 GRID COMPUTING 42
GWSDL: Differences and Example
<wsdl:definitions> <wsdl:types>…</wsdl:types> <wsdl:message>…</wsdl:message> … <gwsdl:portType name=“foo” extends=“ns:bar ogsi:GridService”>
<wsdl:operation name=“op1”>…</wsdl:operation> <wsdl:operation name=“op2”>…</wsdl:operation>
<ogsi:serviceData … />
</gwsdl:portType> …</wsdl:definitions>
•Differences•Interface Inheritance•Ability to describe additional information elements with interface definitions
•serviceData – special elements for life cycle (can be static or dynamic)•Typical attributes: goodFrom, goodUntil, availableUntilExample:
28th Nov 2003 GRID COMPUTING 43
OGSI Grid Service Behavior portTypes
PortType NameInterface Description
and Operations
Service Data elements defined by this portType
Default service data (static) values
GridService (required)
All Grid services implements this interface and provides these operations and behaviors. OperationsfindServiceDatasetServiceDatarequestTerminationTimeAfterrequestTerminationTimeBeforedestroy
InterfacesserviceDataNamefactoryLocatorGridServiceHandleGridServiceRefrencefindServiceDataExtensibilitysetServiceDataExtensibilityterminationTime
<ogsi: findServiceDataExtensibility inputElement="queryByServiceDataNames" /><ogsi: setServiceDataExtensibility inputElement="deleteByServiceDataNames" />
Factory (optional)
To create a new Grid service. Operations1.createService
1.createServiceExtensibility None
HandleResolver (optional)
A service provided mechanism to resolve a GSH to a GSROperations1.FindByHandle
handleResolverScheme None
28th Nov 2003 GRID COMPUTING 44
GridService portType Operations
Operation Description
<TB>findServiceData Query information about the Grid service instance
setServiceData Modify service data values
requestTerminationAfter Specify earliest desired termination time
requestTerminationBefore Specify latest desired termination time
destroy Terminate Grid service instance
28th Nov 2003 GRID COMPUTING 45
OGSI Grid Service Notification portTypes
PortType NameInterface Description
and Operations
Service Data elements defined by this portType
Default service data (static) values
NotificationSource (optional)
This enables a client to subscribe for notification based on a service data value change.Operations1.subscribe
notifiableServiceDataNamesubscribeExtensibility
<ogsi: subscribeExtensibility inputElement="subscribeByServiceDataNames" />
NotificationSink (optional)
Implementing this interface enables a Grid service instance to receive notification messages based on a subscription.Operations1.deliverNotification
None None
NotificationSubscription (optional)
Calling a subscription of a Notification Source results in the creation of a subscription Grid service.OperationsNone defined
subscriptionExpressionsinkLocator
None
28th Nov 2003 GRID COMPUTING 46
OGSI Grid Service Grouping Behavior
PortType NameInterface Description
and Operations
Service Data elements defined by this portType
Default service data (static) values
ServiceGroup (optional)
An abstract interface to represent a grouping of zero or more services. This interface extends the GridService portType.OperationsNone defined but can use operations defined in GridService portType.
MembershipContentRuleentry
None
ServiceGroupRegistration (optional)
This interface extends the ServiceGroup interface and provides operations to manage a ServiceGroup including adding/delete a service to/from a group. Operationsaddremove
addExtensibilityremoveExtensibility
<ogsi: removeExtensibility inputElement= "matchByLocatorEquivalence" />
ServiceGroupEntry (optional)
This is a representation of an individual entry of a ServiceGroup and is created on ServiceGroupRegistration "add". Each entry contains a service locator to a member Grid service and information about the member service as defined by the Service group membership rule (content).OperationsNone defined
memberServiceLocatorcontent
28th Nov 2003 GRID COMPUTING 47
• A DBaccess Grid service will support at least two portTypes– 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
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 48
Transient Database Service
GridService
DBaccessFactory
Factory info
Instance name, etc.
GridService Registration
Registry info
Instance name, etc.
GridService DBaccess
DB info
Name, lifetime, etc.
GridService DBaccess
DB info
Name, lifetime, etc.
“What services can you create?”
“What database services exist?”
“Create a database service”
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 49
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 databasecontaining data one.coli metabolism”
.
.
.
DatabaseFactory
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 50
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
“Find me a data mining service, and somewhere to store
data”
DatabaseFactory
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 51
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
GSHs for Miningand Database factories
DatabaseFactory
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 52
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
“Create a data mining service with initial lifetime 10”
“Create adatabase with initial lifetime 1000”
DatabaseFactory
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 53
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
DatabaseFactory
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
Database
Miner
“Create a data mining service with initial lifetime 10”
“Create adatabase with initial lifetime 1000”
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 54
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
DatabaseFactory
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
Database
Miner
Query
Query
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 55
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
DatabaseFactory
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
Database
Miner
Query
Query
Keepalive
Keepalive
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 56
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
DatabaseFactory
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
Database
MinerKeepalive
KeepaliveResults
Results
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 57
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
DatabaseFactory
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
Database
Miner
Keepalive
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 58
Example:Data Mining for Bioinformatics
UserApplication
BioDB n
Storage Service Provider
DatabaseFactory
MiningFactory
CommunityRegistry
DatabaseService
BioDB 1
DatabaseService
.
.
.
Compute Service Provider...
Database
Keepalive
Source: Grid Services and Web Services Tutorial: GlobusWorld 2003
28th Nov 2003 GRID COMPUTING 60
Conclusions
• GRID is based on idea of virtualization of a pool of heterogeneous resources into one scalable virtual organization
• GRID provides enhanced throughput, resource utilization, non-trivial QoS, leveraging heterogeneous resources
• GRID is suitable for computationally intensive and other resource 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
28th Nov 2003 GRID COMPUTING 61
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…
Top Related