GRID COMPUTING

GRID COMPUTING
 A computational grid is a hardware and
software infrastructure that provides
dependable, consistent, pervasive, and
inexpensive access to coordinated and shared
resources in dynamic, multiinstitutional
virtual organizations.
 The sharing is not primarily file exchange but
rather direct access to computers, software,
data, and other resources. The sharing rule is
clearly and carefully defined, enabling a
necessary and high control of resources.”
CLASSIFYING GRID SYSTEMS
 Computational grid:
refers to systems that harness machines of an
administrative domain in a “cycle-stealing”
mode to have higher computational capacity
than the capacity of any constituent machine
in the system.
 Data grid

denotes systems that provide a hardware and

software infrastructure for synthesizing new
information from data repositories that are
distributed in a wide area network.
 Service grid
refers to systems that provide services that are
not provided by any single local machine.
This category is further divided as on
demand (aggregate resources to provide new
services)
collaborative (connect users and applications
via a virtual workspace)
and multimedia (infrastructure for real-time
multimedia applications).
GRID APPLICATIONS
 A grid is considered to be an infrastructure
that bonds and unifies globally remote and
diverse resources in order to provide
computing support for a wide range of
applications.
 The different types of computing offered by
grids can be categorized according to the
main challenges that they present from the
grid architecture point of view.
1.DISTRIBUTED
SUPERCOMPUTING:
 This type of computing allows applications to
use grids to aggregate computational
resources in order to reduce the completion
time of a job or to tackle problems that
cannot be solved on a single system.
 The technical challenges include the need to
coschedule scarce and expensive resources,
the scalability of protocols and algorithms to
tens or hundreds of thousands of nodes, the
design for latency-tolerant algorithms,
achieving and maintaining high performance
computing across heterogeneous systems.
HIGH-THROUGHPUT COMPUTING
 In high-throughput computing, the grid is
used to schedule large numbers of loosely
coupled or independent tasks, with the goal
of putting unused processor cycles often
from idle workstations to work.
 Chip design and parameter studies are
normally applications of this type of
computing
ON-DEMAND COMPUTING:
 On-demand applications use grid capabilities to
couple remote resources into local applications in
order to fulfill short-term requirements. These
resources cannot be cost-effective or conveniently
located and it may be computation, software, data
repositories, specialized sensors, and so on.
 The challenging issues in on-demand applications
derive primarily from the dynamic nature of
resource requirements and the potentially large
populations of users and resources. These issues
include resource location, scheduling, code
management, configuration, fault tolerance,
security, and payment mechanisms.
DATA-INTENSIVE COMPUTING:
 Data-intensive applications analyze and treat
information and data which are maintained in
geographically distributed repositories, digital
libraries and databases, and aggregated by grid
capabilities. Modern meteorological forecasting
systems which make extensive use of data
assimilation to incorporate remote satellite
observations and high-energy physics are typical
applications of data-intensive computing.
 The challenge in data-intensive applications is the
scheduling and configuration of complex, high-
volume data flows through multiple levels of
hierarchy
COLLABORATIVE COMPUTING:
 In collaborative computing, applications are
concerned primarily with enabling and
enhancing human-to-human interactions. Such
applications often provide a virtual shared
space and are concerned with enabling the
shared use of computational resources such as
data archives and simulations.
 Challenging issues of collaborative applications
from a grid architecture perspective are the
realtime requirements imposed by human
perceptual capabilities and the rich variety of
interactions that can take place.
GRID ARCHITECTURE
 A grid has a layered, extensible, and open
architecture which facilitates the
identification for general classes of
components.

 Components within each layer share common

characteristics but can be built on
capabilities and behaviors provided by any
lower layer
FABRIC LAYER
 The grid fabric layer provides interfaces to
local control of resources which may be logical
entities, computer clusters, or distributed
computer pools.

 Fabric components make resources virtual by

implementing the local, resource-specific
operations that occur on specific resources
(whether physical or logical). There is thus a
interdependence between the functions of
resource implemented at the fabric level and
the shared operations supported.
 The principal resources which the fabric
layer supports and operations of these
resources are shown as follows:
1. Computational resources
2. Storage Resources
3. Network Resources
4. Code Repositories
5. Catalogs
1.COMPUTATIONAL RESOURCE
 Operations are required for starting programs
and for monitoring and controlling the
execution of the resulting processes.
Management mechanisms are needed to
control the resources and inquiry functions
are required for determining hardware and
software characteristics as well as relevant
state information such as current load and
queue state in the case of scheduler-
managed resources.
2.STORAGE RESOURCES
 Putting and getting files operations and
management mechanisms are required.
Inquiry functions are needed for determining
hardware and software characteristics as
well as relevant load information such as
available space and bandwidth utilization.
3.NETWORK RESOURCES
 Management mechanisms and inquiry
functions should be provided to control
network transfers and to determine network
characteristics and load
4.CODE REPOSITORIES
 Management for managing versioned source
and object code are needed mechanisms
5.CATALOGS
 Catalog query and update operations must
be implemented, for example: a relational
database.
CONNECTIVITY LAYER
 The core communication and authentication
protocols required for grid-specific network
transactions are defined at the connectivity
layer which enables the exchange of data
between fabric layer resources. The identity
of users and resources is verified by
authentication protocols which have the
following characteristics: single sign on,
delegation, integration with various local
security solutions, and user-based trust
relationships.
 These utilize the existing internet protocols
such as IP, Domain Name services, various
routing protocols such as BGP and so on.
 Another is GSI (Grid security infrastructure)
which is a security protocol.
RESOURCE LAYER
 The resource layer defines protocols (APIs and SDKs) for
the secure negotiation, initiation, monitoring, control,
accounting, and payment of sharing operations on
individual resources.
 There are two primary classes of resource layer
protocols:
1. Information protocols
2. Management protocols.
Information protocol are used to obtain information about
the structure and state of a resource and management
protocols are used to negotiate access to a shared
resource.
Resource layer protocols are concerned entirely with
individual.
COLLECTIVE LAYER
 The collective layer contains protocols and
services(APIs and SDKs) that are not
associated with any specific resource but
rather are global in nature and capture
interactions across collections of resources.
A wide variety of sharing behaviors and
operations is implemented, such as directory
services, monitoring and diagnostics services,
data replication services, etc.
APPLICATIONS LAYER:
 The applications layer comprises the user
applications that operate within a VO
environment.
OPEN GRID SERVICE
ARCHITECTURE
 Open Grid Services Architecture (OGSA) is a
set of standards defining the way in which
information is shared among diverse
components of large, heterogeneous grid
systems.
 In this context, a grid system is a scalable
wide area network (WAN) that supports
resource sharing and distribution. OGSA is a
trademark of the Open Grid Forum.
 The OGSA is jointly developed by academia
and the IT industry under coordination of a
working group in the Global Grid Forum
(GGF). The standard was specifically
developed for the emerging grid and cloud
service communities.
 The OGSA was built on two basic software
technologies:
 the Globus Toolkit widely adopted as a grid
technology solution for scientific and
technical computing, and
 web services (WS 2.0) as a popular
standards-based framework for business and
network applications.
OGSA ARCHITECTURE LAYERS
1. Physical and logical resource layer
2. Web services layer
3. OGSA Grid service layer
4. Grid Application Layer
PHYSICAL LAYER
 Physical resources are managed at this
layer : CPU, storage ,Servers ,network
 Logical Resources: Database Managers,
workFlow Managers etc.
 Logical resources manages physical
resources.
WEB SERVICE LAYER
 Web services will interact with other software using
xml.
 OGSI(open grid service infrastructure provides
consistent way to interact with grid services.
Web service Layer consists of five interfaces:
1. Factory: Provide way for creation of new grid
service
2. Life cycle: Manage grid service Life cycle
3. State management: Manages grid service states
4. Service groups :collection of indexed grid service
5. Notifications: manages notifications between
services and resources.
OGSA ARCHITECTED SERVICE
LAYER
 Classified into three categories:

1. Grid Core Services(Services Management,

Service Communication, Policy
service ,Security Services)
2. Grid Program execution
services(Parallelsim, virtualization of
resource processing )
3. Grid Data services
GRID APPLICATION LAYER
 Applications used in Grid architecural
services
CONCERNS:
 How do I establish identity and negotiate
authentication?
 How is policy expressed and negotiated?
 How do I discover services?
 How do I negotiate and monitor service level
agreements?
 How do I manage membership of, and communication
within, virtual organizations?
 How do I organize service collections hierarchically so
as to deliver reliable and scalable service semantics?
 How do I integrate data resources into computations?
How do I monitor and manage collections of services?
 Analysis of these use cases and other
relevant input led us to identify
characteristics of Grid environments and
applications, and functional and non-
functional requirements that appear both
important and broadly relevant.
Authors: Open Grid Services Architecture I.
Foster, Argonne & U.Chicago (Editor) http://forge.gridforum.org/projects/ogsa-wg H. Kishimoto, Fujitsu (Editor) A.
Savva, Fujitsu (Editor) D. Berry, NeSC A. Djaoui, CCLRC-RAL A. Grimshaw, UVa B. Horn, IBM F. Maciel, Hitachi F.
Siebenlist, ANL R. Subramaniam, Intel J. Treadwell, HP J. Von Reich, HP 24 July 2006
FINDINGS
INTEROPERABILITY AND SUPPORT FOR DYNAMIC
AND HETEROGENEOUS ENVIRONMENTS
 The need to support heterogeneous systems leads
to requirements that include the following:
1. Resource virtualization. Essential to reduce the
complexity of managing heterogeneous systems
and to handle diverse resources in a unified
way.
2. Common management capabilities. Simplifying
administration of a heterogeneous system
requires mechanisms for uniform and consistent
management of resources. A minimum set of
common manageability capabilities is required.
3. Resource discovery and query.
Mechanisms are required for discovering
resources with desired attributes and for
retrieving their properties. Discovery and
query should handle a highly dynamic and
heterogeneous system.
4. Standard protocols and schemas.
Important for interoperability. In addition,
standard protocols are also particularly
important as their use can simplify the
transition to using Grids.
RESOURCE SHARING ACROSS
ORGANIZATIONS
Resource sharing requirements include:
1. Global name space. To ease data and
resource access. OGSA entities should be able
to access other OGSA entities transparently,
subject to security constraints, without
regard to location or replication.
2. Metadata services. Important for finding,
invoking, and tracking entities. It should be
possible to allow for access to and
propagation, aggregation, and management of
entity metadata across administrative
domains.
3. Site autonomy. Mechanisms are required for
accessing resources across sites while
respecting local control and policy .
4. Resource usage data. Mechanisms and
standard schemas for collecting and
exchanging resource usage (i.e.,
consumption) data across organizations—for
the purpose of accounting, billing, etc
OPTIMIZATION
 Optimization refers to techniques used to
allocate resources effectively to meet
consumer and supplier requirements.
Optimization applies to both suppliers
(supply-side) and consumers (consume-side)
of resources and services.
QUALITY OF SERVICE (QOS)
ASSURANCE
 QoS assurance requirements include:

1. Service level agreement. QoS should be represented by

agreements which are established through negotiation
between service requester and provider prior to service
execution. Standard mechanisms should be provided to create
and manage agreements.
2. Service level attainment. If the agreement requires
attainment of Service Level, the resources used by the service
should be adjusted so that the required QoS is maintained.
Therefore, mechanisms for monitoring service quality,
estimating resource utilization, and planning for and adjusting
resource usage are required.
3. Migration. It should be possible to migrate executing services
or applications to adjust workloads for performance or
availability.
 JOB EXECUTION
 OGSA must provide manageability for
execution of user-defined work (jobs)
throughout their lifetime. Functions such as
scheduling, provisioning, job control and
exception handling of jobs must be
supported, even when the job is distributed
over a great number of heterogeneous
resources.
DATA SERVICES
 Policy specification & management
 Data storage
 Data access
 Data transfer
 Data location management
 Data update
 Data persistency
THE OPEN GRID SERVICES
ARCHITECTURE
 The Globus Project and IBM initiated a
development effort to align Grid
technologies with Web services technologies,
using the Open Grid Services Architecture.
OGSA enables the integration of services and
resources across distributed, heterogeneous,
dynamic environments and communities
 OGSA defines the Grid service concept,
based on principles and technologies from
both the Grid computing and Web services
communities.
 Web services describe the software
components to be accessed, methods for
accessing the components, and discovery
methods that let users and applications
identify relevant service providers.

 Web services are independent of

programming languages and system software
 The OGSA model adopts three Web services
standards:
1. Simple object access protocol (SOAP)
2. WSDL , and
3. Web Services Inspection Language
SIMPLE OBJECT ACCESS
PROTOCOL
 SOAP is a lightweight protocol for exchange of
information in a decentralized, distributed
environment.
 It is an XML based protocol that consists of
three parts: an envelope that defines a
framework for describing what is in a message
and how to process it, a set of encoding rules
for expressing instances of application-defined
datatypes, and a convention for representing
remote procedure calls and responses.
 SOAP can potentially be used in combination
with a variety of other protocols.
WEB SERVICES DESCRIPTION LANGUAGE (WSDL)

 Web Services Description Language Version

2.0 (WSDL 2.0) provides a model and an XML
format for describing Web services.
 WSDL 2.0 enables one to separate the
description of the abstract functionality
offered by a service from concrete details of
a service description such as “how” and
“where” that functionality is offered.
WSIL
 Web Services Inspection Language (WSIL) is a
service discovery mechanism.

 WSIL provides a distributed service discovery

method that supplies references to service
descriptions at the service provider's point-
of-offering, by specifying how to inspect a
Web site for available Web services. The
WSIL specification defines the locations on a
Web site where you can look for Web service
descriptions.
CLOUD ARCHITECTURE
 Cloud architecture refers to how various
cloud technology components, such as
hardware, virtual resources, software
capabilities, and virtual network systems
interact and connect to create cloud
computing environments. It acts as a
blueprint that defines the best way to
strategically combine resources to build a
cloud environment for a specific business
need.
CLOUD ARCHITECTURE COMPONENTS

 A frontend platform
 A backend platform
 A cloud-based delivery model
 A network (internet, intranet, or intercloud)
FRONTEND PLATFORM
 Frontend of the cloud architecture refers to
the client side of cloud computing system.
 In cloud computing, frontend platforms
contain the client infrastructure—user
interfaces, client-side applications, and the
client device or network that enables users to
interact with and access cloud computing
services. For example, you can open the web
browser on your mobile phone and edit a
Google Doc. All three of these things describe
frontend cloud architecture components.
2. BACKEND :
 Backend refers to the cloud itself which is
used by the service provider. It contains the
resources as well as manages the resources
and provides security mechanisms. Along
with this, it includes huge storage, virtual
applications, virtual machines, traffic control
mechanisms, deployment models, etc.
 Application –
Application in backend refers to a software or platform
to which client accesses. Means it provides the service
in backend as per the client requirement.
 Service –
Service in backend refers to the major three types of
cloud based services like SaaS, PaaS and IaaS. Also
manages which type of service the user accesses.
 Runtime Cloud-
Runtime cloud in backend provides the execution and
Runtime platform/environment to the Virtual machine.
 Storage –
Storage in backend provides flexible and scalable
storage service and management of stored data.
A CLOUD-BASED DELIVERY
MODEL
 The types of services available to use vary depending on the
cloud-based delivery model or service model you have
chosen. There are three main cloud computing service
models:
 Infrastructure as a service (IaaS): This model provides on-
demand access to cloud infrastructure, such as servers,
storage, and networking. This eliminates the need to
procure, manage, and maintain on-premises infrastructure.
 Platform as a service (PaaS): This model offers a computing
platform with all the underlying infrastructure and software
tools needed to develop, run, and manage applications.
 Software as a service (SaaS): This model offers cloud-based
applications that are delivered and maintained by the
service provider, eliminating the need for end users to
deploy software locally.
 Infrastructure –
Cloud Infrastructure in backend refers to the hardware and
software components of cloud like it includes servers, storage,
network devices, virtualization software etc.
 Management –
Management in backend refers to management of backend
components like application, service, runtime cloud, storage,
infrastructure, and other security mechanisms etc.
 Security –
Security in backend refers to implementation of different
security mechanisms in the backend for secure cloud resources,
systems, files, and infrastructure to end-users.
 Internet –
Internet connection acts as the medium or a bridge between
frontend and backend and establishes the interaction and
communication between frontend and backend.
CLOUD ARCHITECTURE LAYERS

 Hardware: The servers, storage, network devices,

and other hardware that power the cloud.
 Virtualization: An abstraction layer that creates
a virtual representation of physical computing
and storage resources. This allows multiple
applications to use the same resources.
 Application and service: This layer coordinates
and supports requests from the frontend user
interface, offering different services based on the
cloud service model, from resource allocation to
application development tools to web-based
applications.
TYPES OF CLOUD ARCHITECTURE

 Public,
 private,
 Hybrid.
 Community
PUBLIC
 Public cloud architecture uses cloud
computing resources and physical
infrastructure that is owned and operated by
a third-party cloud service provider.
PRIVATE CLOUD
 refers to a dedicated cloud that is owned and
managed by your organization. It is privately
hosted on-premises in your own data center,
providing more control over resources and
more security over data and infrastructure.
HYBRID CLOUD ARCHITECTURE
 uses both public and private cloud
architecture to deliver a flexible mix of
cloud services. A hybrid cloud allows you to
migrate workloads between environments,
allowing you to use the services that best
suit your business demands and the
workload.
COMMUNITY CLOUD
 Community cloud is a cloud infrastructure
that allows systems and services to be
accessible by a group of several organizations
to share the information. It is owned,
managed, and operated by one or more
organizations in the community, a third
party, or a combination of them.