the challenges of grid computing
DESCRIPTION
The Challenges of Grid Computing. Ian Foster Mathematics and Computer Science Division Argonne National Laboratory and Department of Computer Science The University of Chicago http://www.mcs.anl.gov/~foster. Condor Week Presentation at via Access Grid, March 4, 2002. - PowerPoint PPT PresentationTRANSCRIPT
The Challenges of Grid Computing
Ian Foster
Mathematics and Computer Science Division
Argonne National Laboratory
and
Department of Computer Science
The University of Chicago
http://www.mcs.anl.gov/~foster
Condor Week Presentation at via Access Grid, March 4, 2002
[email protected] ARGONNE CHICAGO
Trends in Grid Computing
New application domains– Data Grids, collaboratories
Integration with commercial technologies– Web services, .NET, …, …
Commercial acceptance and adoption– Very rapid; we don’t know what has hit us
Increasing scale– Sensor nets, mobile and wireless devices,
Internet-wide deployment
[email protected] ARGONNE CHICAGO
The Grid World: Current Status Dozens of major Grid projects in scientific &
technical computing/research & education Considerable consensus on key concepts and
technologies– Open source Globus Toolkit™ a de facto standard for
major protocols & services
– Far from complete or perfect, but out there, evolving rapidly, and large tool/user base
Industrial interest emerging rapidly Opportunity: convergence of eScience and
eBusiness requirements & technologies
[email protected] ARGONNE CHICAGO
The Grid Problem
Resource sharing & coordinated problem solving in dynamic, multi-institutional virtual organizations
[email protected] ARGONNE CHICAGO
Why Grids? (1) eScience A biochemist exploits 10,000 computers to
screen 100,000 compounds in an hour 1,000 physicists worldwide pool resources for
peta-op analyses of petabytes of data Civil engineers collaborate to design, execute,
& analyze shake table experiments Climate scientists visualize, annotate, &
analyze terabyte simulation datasets An emergency response team couples real time
data, weather model, population data
[email protected] ARGONNE CHICAGO
Why Grids? (2) eBusiness Engineers at a multinational company
collaborate on the design of a new product A multidisciplinary analysis in aerospace
couples code and data in four companies An insurance company mines data from partner
hospitals for fraud detection An application service provider offloads excess
load to a compute cycle provider An enterprise configures internal & external
resources to support eBusiness workload
[email protected] ARGONNE CHICAGO
Strategic Challenges
Managing the transition from a research area to an industry
Profiting from commercial technologies without compromising eScience needs
Innovating fast enough to meet needs of new application domains
Establishing and extending Grid community Pursuing the research to address next-
generation systems
[email protected] ARGONNE CHICAGO
Our Approach
Define & promote unifying, open view of Grids, integrating commercial technologies– Open Grid Services Architecture
Coherent, high-quality open source code Pursue realization in close collaboration
– For us, Condor Group is first among equals Reach out to, and engage, industry,
emphasizing benefits of collaboration– Identify areas where industry can add value
[email protected] ARGONNE CHICAGO
“Web Services” Increasingly popular standards-based framework for
accessing network applications– W3C standardization; Microsoft, IBM, Sun, others
WSDL: Web Services Description Language– Interface Definition Language for Web services
SOAP: Simple Object Access Protocol– XML-based RPC protocol; common WSDL target
WS-Inspection– Conventions for locating service descriptions
UDDI: Universal Desc., Discovery, & Integration – Directory for Web services
[email protected] ARGONNE CHICAGO
Transient Service Instances “Web services” address discovery & invocation of
persistent services– Interface to persistent state of entire enterprise
In Grids, must also support transient service instances, created/destroyed dynamically– Interfaces to the states of distributed activities
– E.g. workflow, video conf., dist. data analysis Significant implications for how services are managed,
named, discovered, and used– In fact, much of our work is concerned with the
management of service instances
[email protected] ARGONNE CHICAGO
OGSA Design Principles Service orientation to virtualize resources
– Everything is a service From Web services
– Standard interface definition mechanisms: multiple protocol bindings, local/remote transparency
From Grids– Service semantics, reliability and security models
– Lifecycle management, discovery, other services Multiple “hosting environments”
– C, J2EE, .NET, …
[email protected] ARGONNE CHICAGO
OGSA Service Model System comprises (a typically few) persistent
services & (potentially many) transient services– Everything is a service
OGSA defines basic behaviors of services: fundamental semantics, life-cycle, etc.– More than defining WSDL wrappers
[email protected] ARGONNE CHICAGO
Open Grid Services Architecture:Fundamental Structure
1) WSDL conventions and extensions for describing and structuring services– Useful independent of “Grid” computing
2) Standard WSDL interfaces & behaviors for core service activities– portTypes and operations => protocols
[email protected] ARGONNE CHICAGO
Standard Interfaces & Behaviors:Four Interrelated Concepts
Naming and bindings– Every service instance has a unique name, from which
can discover supported bindings Information model
– Service data associated with Grid service instances, operations for accessing this info
Lifecycle– Service instances created by factories
– Destroyed explicitly or via soft state Notification
– Interfaces for registering interest and delivering notifications
[email protected] ARGONNE CHICAGO
GridService Required– FindServiceData
– Destroy
– SetTerminationTime
NotificationSource– SubscribeToNotificationTopic
– UnsubscribeToNotificationTopic NotificationSink
– DeliverNotification
OGSA Interfaces and OperationsDefined to Date
Factory– CreateService
PrimaryKey– FindByPrimaryKey
– DestroyByPrimaryKey
Registry– RegisterService
– UnregisterService
HandleMap– FindByHandle
Authentication, reliability are binding propertiesManageability, concurrency, etc., to be defined
[email protected] ARGONNE CHICAGO
GT3: An Open Source OGSA-Compliant Globus Toolkit
GT3 Core– Implements Grid service
interfaces & behaviors
– Reference impln of evolving standard
GT3 Base Services– Evolution of current Globus
Toolkit capabilities Other Grid services
– Many …
GT3 Core
GT3 Grid Services
Other GridServicesGT3
DataServices
[email protected] ARGONNE CHICAGO
User/Application
Fabric (processing, storage, communication)
GridCondor
Globus Toolkit
Condor
[email protected] ARGONNE CHICAGO
For More Information
The Globus Project™– www.globus.org
Grid architecture– www.globus.org/
research/papers/anatomy.pdf
Open Grid Services Architecture– www.globus.org/ogsa