Cloud computing vs grid computing

8neutron8 8,416 views 26 slides Jun 25, 2012
Slide 1
Slide 1 of 26
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26

About This Presentation

No description available for this slideshow.


Slide Content

“A pool of abstracted, highly scalable, and
managed computer infrastructure capable
of hosting end-customer applications and
billed by consumption
1

“Cloud computing is an emerging approach
to shared infrastructure in which large pools
of systems are linked together to provide IT
services.”

SaaS
›Software as a Service
›Storage as a Service
PaaS – Platform as a Service
IaaS – Infrastructure as a Service

In SaaS no need to buy expensive licensed applications
Examples: SalesForce, Gmail, Yahoo! Mail, Quicken Online
 Instead of selling you a copy of Microsoft Word for $300, a
cloud computing model would "rent" word processing
software to you through the Internet for perhaps 5 dollars a
month.
Advantages: Free, Easy,  repair a single central copy of the
product online
Disadvantages: Limited functionality, no control or access to
underlying technology,  you have to trust into the online
software vendors.

“Containers”
“Closed” environments
Examples: Google App Engine(support only java &
python), ,Force.com(support 16 languages)[5] ,Windows
Azure(.Net,java,Php), Mosso, Engine Yard, Joyent
Advantages: Good for developers, more control than
“Application” Clouds, tightly configured
Disadvantages: Restricted to what is available, other
dependencies

Provide “Compute” and “Storage” clouds
Virtualization layers (hardware/software)
Examples: Amazon EC2, GoGrid, Amazon S3, Nirvanix, Linode
Advantages: Full control of environments and infrastructure
Disadvantages: premium price point, limited competition

Infrastructure as a Service (IaaS) provides
the user with virtual infrastructure, such as
servers and data storage space. This is
where virtualization fits into the cloud.
Platform as a Service (PaaS) provides the
user with development environment
services where the user can create and run
home-grown applications.
Software as a Service (SaaS) provides the
user with access to already created
applications that are operating in the
cloud.

•Layers equate structure
•Building blocks: Infrastructure, Platforms,
Applications

1000’s of Cloud Applications currently
Handful of Cloud Platforms
Elite group of Cloud Infrastructure
providers
# of Marketplace providers

Provides extension to Cloud Infrastructure and Platforms with
basic functionality
Examples: Amazon SimpleDB, Amazon SQS, Google BigTable
Advantages: Extends functionality of Compute & Storage
Clouds to integrate with other clouds
Disadvantages: Sometimes requires use of specific Platforms
or Infrastructure

Sits on top of various Cloud Infrastructures for management
Examples: RightScale, Appistry
Advantages: Provides more options for Cloud environments
Disadvantages: Dependent on Cloud Providers

Colocation Managed Cloud
Time Weeks to Months Days to Weeks Minutes
Scalability Slowest, Rigid &
Costly
Slower, somewhat
flexible, Costly
Instant, Flexible,
Pay-per-usage
Cost High Costly, sometimes
month/year
contracts,
No contracts,
usage based, no
upfront costs
“Green” Low Low High - virtualized
Pricing model Buy Servers & Colo
costs whether
used or not
Rent Servers &
Hosting costs
whether used or
not
Rent based on
usage only

Technology has evolved
People demand more control
Instant gratification
Managed is not dynamic enough
Cloud Computing -“Enabling Technology”
to move from Traditional Hosting to
Cloud Hosting

Ease of Use
Scalability
Risk
Reliability
Cost

Deploy infrastructure with a mouse or API
›No cabling, screwdrivers, racking, unboxing,
buying
›Middle of the night
›Do it yourself remotely from anywhere anytime

2.Control your infrastructure with your
application demands.
3.No need to purchase expensive hardware's
for scalability.

1.Nothing to buy
2.Cancel immediately
3.Change instantly, even operating
systems
4.Throw it out
5.Rebuild it instantly after testing
RISK

1.Based on High quality hardware
2.Design for failures:
›Automatically spin up replacements
›Use multiple clouds

1.Pay for only what you use
2.No need to buy in advance
3.Zero Capital Outlay
4.No contracts

Grid computing is the ability to process
information by utilizing a collection of
networked heterogeneous information-
processing components (hardware and
software), all of which are provisioned from
various geographical locations and across
organizational boundaries.[5]

In grid computing the concept of Virtual
Organizations (VOs) rises. Which means that
all resources were owned by a single
organization.
 Two key outcomes exist in grids:
3.The Open Grid Service Architecture (OGSA)
4.The Globus Toolkit.
OGSA means how grids are created and
maintained.

The Globus Toolkit is a software
middleware package. All that is required
is to install and configure Globus and
then create all required resources and
services.
grid security approach is the Grid
Security Infrastructure (GSI) which has
been implemented in
the Globus Toolkit

NAREGI ( National Research Grid Initiative) is a
grid project that focuses on the research and
development of grid middleware.
The test contains almost 3000 CPUs and is
capable of 17 teraflops of processing power,
offered from various research institutions
throughout Japan.
BOINC is an Open-source software
for volunteer computing and grid computing.
BOINC is supported by the National Science
Foundation(SETI@home, Climateprediction.net)

1.Neither grids nor clouds have a commonly
accepted definition.
2.Grids are publicly funded and operated,
whereas clouds are privately funded and
operated.
3.Grids and clouds are instantiations of
distributed systems, which is a common
feature of them.
4.Grids evolve slowly and clouds evolve fast,
and The level of expertise to use a cloud is
significantly lower than that of a grids.

1.Paul Lancaster Business Development
Manager, GoGrid Site:
http://www.GoGrid.com
2.http://www. amazon.com
3.http://wikipedia.org
4.http://saasevolution.blogspot.com
5.Grids vs. Clouds , Michael Brock and
Andrzej Goscinski ,School of Information
Technology , Deakin University ,Australia
6.http://boinc.berkeley.edu/