0% found this document useful (0 votes)
76 views

Grid Computing Overview

The document provides an overview of grid computing, including defining grid computing, describing elements of a grid like resource sharing and virtual organizations, and discussing grid middleware and architecture. It also compares web services to grid services, noting grids allow for more versatile and complex distributed computing.

Uploaded by

sridharegsp
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
76 views

Grid Computing Overview

The document provides an overview of grid computing, including defining grid computing, describing elements of a grid like resource sharing and virtual organizations, and discussing grid middleware and architecture. It also compares web services to grid services, noting grids allow for more versatile and complex distributed computing.

Uploaded by

sridharegsp
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 38

Grid Computing Overview

Dr.M.ARAMUDHAN
Associate Professor & Head
Department of Information Technology
PKIET, Karaikal - 609603

Grid environment

INTRODUCTION
Grid computing is a form of distributed
computing whereby a "super and virtual
computer" is composed of a cluster of networked,
loosely coupled computers, acting in concert to
perform very large tasks.
Grid computing (Foster and Kesselman, 1999) is a
growing technology that facilitates the executions
of large-scale resource intensive applications on
geographically distributed computing resources.

The term Grid comes from an analogy to the Electric Grid.


Pervasive access to power.
Similarly, Grid will provide pervasive, consistent, and
inexpensive
access
to
advanced
computational
resources.
Grids are about large-scale resource sharing.
Spanning administrative boundaries.
Central processors, storage, network bandwidth,
databases, applications, sensors and so on
Problem solving in dynamic, multi-institutional environment.
Organizing geographically distributed computing resources
So that they can be flexibly and dynamically allocated
and accessed

Providing such capabilities, where Sharing is


highly controlled, clear definitions of exactly what
is shared, who is allowed to share, and the
conditions under which sharing occurs.
Types of Grids
Data Grid is a grid computing system that
deals with the controlled sharing and management
of distributed data.
Computational Grid is a grid computing
system that is concerned with the computation.

Elements of the Grid


Resource sharing
Computers, data, 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 organizations
Community overlays on classic org structures
Large or small, static or dynamic

A set of individuals and/or institutions defined by


a set of sharing rules. The sharing is highly
controlled,
with
resource
providers
and
consumers defining clearly and carefully just what
is shared.
An example:
the set of application service
providers, storage service providers, cycle
providers and consultants engaged by a car
manufacturer to plan for a new factory. Another
example: industrial consortium building a new
aircraft

A grid is a system that:


Coordinates resource sharing in a decentralized manner (i.e., different VOs).
Uses standard, open, general purpose
protocols and interfaces.
Delivers non-trivial qualities of service.
Guaranteed bandwidth for application.
Guaranteed CPU cycles.
Guaranteed latency.

Introduction
Topologies in Grid
Intragrids Single organizations No partner integration A single
cluster
Extragrids Multiple organizations Partner integration Multiple
clusters
Intergrids Many organizations Multiple partners Many multiple
clusters
Three main issues to confront in Grid environment:
Heterogeneity multiplicity of resources
Scalability
Adaptability - Resource managers or applications dynamic to
extract the maximum performance from the available resources
and services.
9

Grid Middleware
System software between applications and
operating system
Provide services to application
Discovery, storage, execution, information,
service integration, resource monitoring,
failure detection and recovery,
Hide heterogeneous of the Grid environment
Provide standardised interfaces to services.

10

Purposes of Middleware
Open, general-purpose and standard
Standard protocols
Defines the contents and sequence of message
exchanges used to request remote operation
Important and essential to achieve the
interoperability that Grid depends on
Standard APIs
Interfaces to code libraries
Facilitate construction of Grid components by
allowing code components to be reused

11

Introduction to Grid Architecture


Why Discuss Architecture?
Descriptive
Provide a common vocabulary for use when
describing Grid systems
Guidance
Identify key areas in which services are
required
Prescriptive
Define standard protocols and APIs to facilitate
creation of interoperable Grid systems and
portable applications

Introduction to Grid Architecture


The nature of grid architecture
A grid architecture identifies fundamental system
components, specifies the purpose and function of
these
components, and indicate how these
components interact.
Grids protocols allow VO users and resources to
negotiate, establish, manage and exploit sharing
relationships.
Interoperability a fundamental concern
The protocols are critical to interoperability
Services are important
We need to consider APIs and SDKs

Introduction to Grid Architecture


Grid architecture requirements
The components are
numerous
owned and managed by different, potentially
mutually distrustful organisations and individuals
may be potentially faulty
have different security requirements and policies
heterogeneous
connected by heterogeneous, multilevel networks
have different resource management policies
are likely to be geographically separated

Grid layered architecture


- The neck: a small
set of core
abstractions and
protocols
- Top of hourglass:
many different highlevel behaviors can
be mapped
- Base of hourglass:
can be mapped onto
many different
underlying
technologies

15

Key Components

Internet Protocol Architecture

Layered Grid Architecture


(By Analogy to Internet Architecture)

Application
Coordinating
Application

Collective
Resource

Transport
Internet

Connectivity

Link

Fabric

multiple
resources:
ubiquitous
infrastructure services, appspecific
distributed services
Sharing single resources:
negotiating access, controlling
use
Talking to things:
communication (Internet
protocols) & security
Controlling things locally:
Access to, & control of,
resources

Key Components
Layered Grid Architecture: Fabric Layer

Just what you would expect: the diverse mix of resources that
may be shared
Individual computers, Condor pools, file systems, archives,
metadata catalogs, networks, sensors, etc., etc.
Defined by interfaces, not physical characteristics

Communication
Internet protocols: IP, DNS, routing, etc.

Security: Grid Security Infrastructure (GSI)


Uniform authentication, authorization, and message
protection mechanisms in multi-institutional setting
Single sign-on, delegation, identity mapping
Public key technology, SSL, X.509, GSS-API
Supporting infrastructure: Certificate Authorities, certificate
& key management,

Key Components
Layered Grid Architecture:Resource Layer

The architecture is for the secure negotiation, initiation,


monitoring, control, accounting, and payment of sharing
operations on individual resources.
Information Protocols (inform about the structure and state
of the resource)
Management Protocols (negotiate access to a shared
resource)
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

Key Components
Layered Grid Architecture:Collective layer
Coordinating multiple resources
Contains protocols and services that capture
interactions among a collection of resources
It supports a variety of sharing behaviours
without placing new requirements on the
resources being shared
Sample services: directory services, co-allocation,
brokering
and
scheduling
services,
data
replication services, workload management
services, collaboratory services

Key Components
Layered Grid Architecture: Collective Layer

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.

20

Key Components
Layered Grid Architecture:Applications layer
There are user applications that operate within
the 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 services
Well-defined APIs also exist to work with these
services

Key Components
Grid architecture in practice

Key Components
Where Are We With Architecture?
No official standards exist
But:
Globus Toolkit has emerged as the de facto
standard for several important Connectivity,
Resource, and Collective protocols
Technical specifications are being developed
for architecture elements: e.g., security,
data, resource management, information

Services in the Web and the Grid


Web services
Define a technique for describing software
components to be accessed, methods for accessing
these components, and discovery methods that
enable the identification of relevant service providers
A distributed computing technology (like CORBA,
RMI)
They allow us to create loosely coupled client/server
applications.
Platform and language independent since they use
XML language.
Most use HTTP for transmitting messages (such as
the service request and response)

Services in the Web and the Grid


Web Services: Disadvantages
Overhead : Transmitting data in XML is not as
convenient as binary codes.
Lack of versatility: They allow very basic forms of
service invocation (Grid services make up this
versatility).
Stateless:
Non-transient:
They cant remember what you have
done from one invocation to another
They outlive all their clients.

7/22/16

MCC/MIERSI Grid Computing

25

Services in the Web and the Grid


Web Services Architecture
Find Web services which
meet certain requirements
(Universal Description, Discovery
and Integration)

Services describe their


own properties and
methods
(Web Services Description
Format
Language)of requests(client)

and responses (server)

(Simple Object Access Protocol)

Message transfer protocol


(Hypertext Transfer Protocol)

Services in the Web and the Grid


Invoking a Typical Web Service

Services in the Web and the Grid


Web Service Addressing
URI: Uniform Resource Identifiers
URI and URL are practically the same
thing.
Example:
http://webservices.mysite.com/weather/us/Wea
therService

It can not be used with web browsers, it


is meant for softwares.

7/22/16

MCC/MIERSI Grid Computing

28

Services in the Web and the Grid


Web Service Application

Picture from Globus 3 Tutorial Notes


7/22/16

MCC/MIERSI Grid Computing

29

Services in the Web and the Grid


What is a Grid Service?
It provides a set of well defined interfaces and
that follows specific conventions.
It is a web service with improved
characteristics and services.
Improvement:
Potentially Transient
Stateful
Delegation
Lifecycle management
Service Data
Notifications
Examples : computational resources,
programs, databases
7/22/16

MCC/MIERSI Grid Computing

30

Services in the Web and the Grid


Factories

Services in the Web and the Grid


GSH & GSR
GSH: Grid Service Handle (URI)
Unique
Shows the location of the service
GSR: Grid Service Reference
Describes how to communicate with the
service
As WS use SOAP, our GSR is a WSDL file.

7/22/16

MCC/MIERSI Grid Computing

32

Services in the Web and the Grid


Open Grid Services Architecture (OGSA)
OGSA defines what Grid services are, what they
should be capable of, what type of technologies
they should be based on.
OGSA does not give a technical and detailed
specification. It uses WSDL.

7/22/16

MCC/MIERSI Grid Computing

33

Services in the Web and the Grid


Open Grid Services Infrastructure (OGSI)
It is a formal and technical specification of the
concepts described in OGSA.
The Globus Toolkit 3 is an implementation of
OGSI.
Some other implementations are OGSI::Lite
(Perl)1 and the UNICORE OGSA demonstrator2
from the EU GRIP project.
OGSI specification defines grid services and
builds upon web services.

7/22/16

MCC/MIERSI Grid Computing

34

OGSA
Open Grid Services Architecture(OGSA) describes a serviceoriented architecturefor agrid computing environment for business
and scientific use. It was developed within the Open Grid Forum,
which was called the Global Grid Forum (GGF).

OGSA is a distributed interaction and computing architecture


based
around
services,
assuring
interoperability
on
heterogeneous systems so that different types of resources
can communicate and share information.
OGSA is based on several otherWeb servicetechnologies, such
as theWeb Services Description Language(WSDL) and
theSimple Object Access Protocol(SOAP), but it aims to be
largely independent of transport-level handling of data.
OGSA has been described as a refinement of a Web services
architecture, specifically designed to support grid requirements

OGSA Working Group collects requirements and


maintains a set of informational documents that
describe the architecture.
A set of normative specifications andprofilesthat
document the precise requirements for a
conforming hardware or software component;
Software components that adhere to the OGSA
specifications and profiles, enabling deployment of
grid solutions that are interoperable even though
they may be based on implementations from
multiple sources.

The Grid Service =


Interfaces + Service Data
Reliable invocation
Authentication
Service data access
Explicit destruction
Soft-state lifetime

GridService

Service
data
element

other interfaces

Service
data
element

Service
data
element

Implementation

Hosting environment/runtime
(C, J2EE, .NET, )

Notification
Authorization
Service creation
Service registry
Manageability
Concurrency

Open Grid Services Architecture, described


these capabilities:
Infrastructure services, Execution
Management services, Data services, Resource
Management services, Security services, Selfmanagement services, Information services

You might also like