CLOUD COMPUTING

Grid Architecture and Tools

Dr. Adeel Asghar

Courtesy:
NUML RWP
Dr Gnanasekaran
adeel.asghar@numl.edu.pk Thangavel
 The Hourglass Model

• Focus on architecture issues

Applications
– Propose set of core services as basic
Diverse global services
infrastructure
– Used to construct high-level, domain-specific
solutions (diverse)
• Design principles
Core
– Keep participation cost low services
– Enable local control
– Support for adaptation
– “IP hourglass” model

Local OS
• The architecture consists of four layers.

• The lowest fabric layer provides interfaces to

local resources at a specific site. These interfaces
are tailored to allow sharing of resources within a
virtual organization.

• The connectivity layer consists of small, standard

collection of communication protocols for
supporting grid transactions that span the usage
of multiple resources. In addition, the connectivity
layer will contain security protocols to authenticate
users and resources.

• The next layer in the hierarchy is the collective layer. It deals with handling access to multiple
resources and typically consists of services for resource discovery, allocation and scheduling of tasks
onto multiple resources, data replication, and so on.

• The application layer consists of the applications that operate within a virtual organization and which
make use of the grid computing environment.
 Example:
Data Grid Architecture
App Discipline-Specifc Data Grid Application

Collective Coherency control, replica selection, task management, virtual data catalog,
(App) virtual data code catalog, …

Collective Replica catalog, replica management, co-allocation, certifcate authorities,

(Generic) metadata catalogs,

Resource Access to data, access to computers, access to network performance data, …

Connect Communication, service discovery (DNS), authentication, authorization,

delegation

Fabric Storage systems, clusters, networks, network caches, …

 Simulation tools
• GridSim is a Java-based toolkit for modeling, and
simulation of distributed resource management and
scheduling for conventional Grid environment.

• GridSim is based on SimJava, a general purpose discrete-

event simulation package implemented in Java.

• All components in GridSim communicate with each other

through message passing operations defined by SimJava.

http://www.gridbus.org/gridsim
http://www.buyya.com/gridsim/
 Salient features of the GridSim
• It allows modeling of heterogeneous types of resources.
• Resources can be modeled operating under space- or time-
shared mode.
• Resource capability can be defined (in the form of MIPS
(Million Instructions Per Second) benchmark.
• Resources can be located in any time zone. Weekends
• and holidays can be mapped depending on resource’s
local time to model non-Grid (local) workload.
• Resources can be booked for advance reservation.
• Applications with different parallel application models can be
simulated.
 Salient features of the GridSim
• Application tasks can be heterogeneous and they can be CPU
or I/O intensive.
• There is no limit on the number of application jobs that can be
submitted to a resource.
• Multiple user entities can submit tasks for execution
simultaneously in the same resource, which may be time-
shared or space-shared. This feature helps in building
schedulers that can use different market-driven economic
models for selecting services competitively.
• Network speed between resources can be specified.
• It supports simulation of both static and dynamic schedulers.
• Statistics of all or selected operations can be recorded and
they can be analyzed using GridSim statistics analysis
methods.
 Cloud: Definition
“A large-scale distributed computing paradigm that is driven by
economies of scale, in which a pool of abstracted, virtualized,
dynamically-scalable, managed computing power, storage,
platforms, and services are delivered on demand to external
customers over the Internet.”

(According to Foster, Zhao, Raicu and Lu, Cloud Computing and Grid
Computing 360-Degree Compared, 2008)
Cloud: just a new name for Grid?

• YES:
– Reduce the cost of computing
– Increase reliability
– Increase flexibility (third party)
Cloud: just a new name for Grid?

• NO:
– Great increase demand for computing
(clusters, high speed networks)
– Billions of dollars being spent by Amazon,
Google, Microsoft to create real commercial
large-scale systems with hundreds of
thousands of computers – www.top500.org
shows computers with 100,000+ computers
– Analysis of massive data
Cloud: just a new name for Grid?

• Nevertheless YES:
– Problems are the same in clouds and grids
– Common need to manage large facilities
– Define methods to discover, request and use
resources
– Implement highly parallel computations
Clouds: key points of the definition

• Differences related to traditional

distributed paradigms:
– Massively scalable
– Can be encapsulated as an abstract entity
that delivers different levels of service
– Services can be dynamically configured (via
virtualization or other approaches) and
delivered on demand
 Clouds: reasons for interest

• Rapid decrease in hardware cost, increase

in computing power (multi-cores etc.) and
storage capacity
• Exponentially growing data size
• Widespread adoption of Services
Computing and Web 2.0 apps
Clouds: relation with other paradigms
Web 2.0, Clouds, and Internet of Things

HTC: High - Throughput Computing HPC: High - Performance Computing P2P: Peer to Peer
MPP: Massively Parallel Processors
 What is a Service Oriented Architecture (SOA)?

• A method of design, deployment, and management of

both applications and the software infrastructure
where:
– All software is organized into business services that
are network accessible and executable.
– Service interfaces are based on public standards for
interoperability.
 Key Characteristics of SOA
• Quality of service, security and performance are specified.
• Software infrastructure is responsible for managing.
• Services are cataloged and discoverable.
• Data are cataloged and discoverable.
• Protocols use only industry standards.
 What is a “Service”?

• A Service is a reusable component.

• A Service changes business data from one state to
another.
• A Service is the only way how data is accessed.
• If you can describe a component in WSDL, it is a
Service.
 Organization of Infrastructure Services

Infrastructur
e Services
(Enterprise Information)

Data Security Computing Communication Application

Services Services Services Services Services
 Organization of Data Services

Data
Services

Discovery Management Collaboration Interoperability Semantic

Services Services Services Services Services
 Data Interoperability Policies
• Data is an enterprise resource.

• Single-point entry of unique data.

• Enterprise certification of all data definitions.

• Data stewardship defines data custodians.

• Zero defects at point of entry.

• De-conflict data at source, not at higher levels.

• Data aggregations from sources data, not from reports.

 Organization of Security Services

Security
Services

Transfer Protection Certifca tion Systems Authentication

Services Services Services Assurance Services
 Security Services = Information Assurance
• Conduct Attack/Event Response
• Ensure timely detection and appropriate response to attacks.
• Manage measures required to minimize the network’s
vulnerability.
• Secure Information Exchanges
• Secure information exchanges that occur on the network with a
level of protection that is matched to the risk of compromise.
• Provide Authorization and Non-Repudiation Services
• Identify and confirm a user's authorization to access the network.
 Organization of Computing Services

Computing
Services

Computing Resource Control & Con fguration Financial

Facilities Planning Quality Services Management
 Computing Services
• Provide Adaptable Hosting Environments

– Global facilities for hosting to the “edge”.

– Virtual environments for data centers.

• Distributed Computing Infrastructure

– Data storage, and shared spaces for information sharing.
• Shared Computing Infrastructure Resources
– Access shared resources regardless of physical access device.
 Organization of Communication Services

Communication
Services

Interoperability Spectrum Connectivity Continuity of Resource

Services Management Arrangements Services Management
 Communication Services
• Provide Information Transport

– Transport information, data and services anywhere.

– Ensures transport between end-user devices and servers.
– Expand the infrastructure for on-demand capacity.
 Organization of Application Services

Application
Services

Component Code Binding Maintenance Experimental

Portals
Repository Services Management Services