Intro Cloud Computing

84
Introduction to ‘Cloud Computing’ చచచచచచచచచ 9/19 - 2009

description

This is a breif demonstration about Cloud Computing.

Transcript of Intro Cloud Computing

Page 1: Intro Cloud Computing

Introduction to ‘Cloud Computing’

చక్ర�వర్తి�9/19 - 2009

Page 2: Intro Cloud Computing

Expertise level• Using Computer for email• Use computer for programming since

– 0 to 2 yrs– 2 to 4 yrs– 4 yrs and Above

• Will learn later• I’m here because of my friend / philosopher /

blah .. blah .. • ఏదో.. టైమ్పాస్

Page 3: Intro Cloud Computing

What, How and Why

• Do I care• Why do I care• I don’t care• ..

• కెరీర్ ఇం�కామొదలవ�లేద�, ఇంప్పు�డెం�ద�క్ర�?

Page 4: Intro Cloud Computing
Page 5: Intro Cloud Computing

Agenda

• The hype – stats• Industry definitions• History – a review of computing• Issues that matter• Origin• Grid vs Cloud• Details

Page 6: Intro Cloud Computing

The hype

Cluster ComputingCloud ComputingGrid Computing 

Page 7: Intro Cloud Computing

The hype

Page 8: Intro Cloud Computing

Some Definitions

Page 9: Intro Cloud Computing
Page 10: Intro Cloud Computing

definitions

Page 11: Intro Cloud Computing

.. Moving computing and data away from the desktop and the portable PC and simply displaying the results of computing that takes place in a centralized location and is then transmitted via the internet on the user's screen ..

- John Makroff

Page 12: Intro Cloud Computing

.. a computing paradigm shift where computing is moved away from personal computers or an individual application server to a "cloud" of computers ..

- Wikipedia

Page 13: Intro Cloud Computing

.. the idea of relayin on Web-based applications and storing data in the "cloud" of the internet

- MIT Technology Review

Page 14: Intro Cloud Computing

.. it starts with the premise that the data services and architecture should be on servers, We call it cloud computing - they should be in a 'cloud' somewhere..

- Eric Schmidt

Page 15: Intro Cloud Computing

Some other ..• Common, Location-independent, Online Utility on Demand*

– Common implies multi-tenancy, not single or isolated tenancy – Utility implies pay-for-use pricing– on Demand implies ~infinite, ~immediate, ~invisible scalability

• Alternatively, a “Zero-One-Infinity” definition:** 0 On-premise infrastructure

Acquisition costAdoption costSupport cost

1 Coherent and resilient environment – not a brittle “software stack”

Scalability in response to changing needIntegratability/Interoperability with legacy assets and other servicesCustomizability/Programmability from data, through logic, up into theuser interface without compromising robust multi-tenancy

* Joe Weinman, Vice President of Solutions Sales, AT&T, 3 Nov. 2008** From The Jargon File: “Allow none of foo, one of foo, or any number of foo”

Page 16: Intro Cloud Computing

.. the trend towards online services that run in a web browser and store users information in a provider's data center ..

- చక్ర�వర్తి�

Page 17: Intro Cloud Computing

location

Page 18: Intro Cloud Computing

location

computations & data are not in the place they used to be in..

Page 19: Intro Cloud Computing

location

why does it matter? a bunch of geeky stuff..

Page 20: Intro Cloud Computing

possession implies control

control implies power

Page 21: Intro Cloud Computing

history

of computing, how is changed

Page 22: Intro Cloud Computing

distributed central

Page 23: Intro Cloud Computing

history of evolution of computing

Page 24: Intro Cloud Computing
Page 25: Intro Cloud Computing
Page 26: Intro Cloud Computing
Page 27: Intro Cloud Computing
Page 28: Intro Cloud Computing

SUN 3 workstation

Page 29: Intro Cloud Computing

Centralized

Low CostExpert Management

Distributed

Rich user InterfaceUser Autonomy

Page 30: Intro Cloud Computing

Server

Client

Client

Client

Client

Client Server – 80s & 90s

Page 31: Intro Cloud Computing

ServerClient

Page 32: Intro Cloud Computing

ServerClient

Page 33: Intro Cloud Computing
Page 34: Intro Cloud Computing

Data Store

S Q L

C #

JavaScript

HTML

XML

ASP.NET

Intermediary Application – Cloud Implementation Strategy

Page 35: Intro Cloud Computing

enterprise impact

Page 36: Intro Cloud Computing

Cultural Challenges

Page 37: Intro Cloud Computing

Integration is hard

ExpensiveInfrastructure

Data

Page 38: Intro Cloud Computing

Data Integration

Adds meaning

Page 39: Intro Cloud Computing

Data Integration is hard

InvisibleHard to quantify Discounted

Page 40: Intro Cloud Computing

Financial & Logistics Challenges

Page 41: Intro Cloud Computing

Cost v. BenefitTime (Cost v. Benefit)

Page 42: Intro Cloud Computing

Traditional Software Purchase

Purchase softwarePurchase hardwareFind space in data centerCreate migration planSetup development & testConfigure systemsConfigure databasesConfigure networksMore…

Page 43: Intro Cloud Computing

The Easy Way

Get a login

Page 44: Intro Cloud Computing

Data Integration is hard

Costs don’t match benefits

Page 45: Intro Cloud Computing

How do we make integration easier, and deliver benefits more

quickly?

Page 46: Intro Cloud Computing

Define Cloud Computing

Page 47: Intro Cloud Computing

How do we make integration easier, and deliver benefits more quickly?Cloud computing is a way to make integration easier, and deliver benefits more quickly

Page 48: Intro Cloud Computing

Turn a commodity into a utility

integration^

Necessary, but not

differentiating

Page 49: Intro Cloud Computing

Not everything’s a commodity

Page 50: Intro Cloud Computing

Web Server Farms. Commodity.

Page 51: Intro Cloud Computing

Much Enterprise Software. Commodity

Page 52: Intro Cloud Computing

Email. A commodity.

Page 53: Intro Cloud Computing

Messaging. Maybe not a commodity.

Page 54: Intro Cloud Computing

What if… we just gave IT a platform to create their own data models, interfaces, and processes on a dynamic infrastructure [that met corporate requirements] & simply existed as needed?

Page 55: Intro Cloud Computing

Results in elevated IT relevance

Page 56: Intro Cloud Computing

Other Results…

Focus on integration will evolve to a more disciplined approach

Match expenses to benefits

Enable new classes of applications

Page 57: Intro Cloud Computing

Best Practices

Page 58: Intro Cloud Computing

Mediation. A secret weapon.

Page 59: Intro Cloud Computing

Service Level Management. Don’t even start with “my piece is working fine!”

Page 60: Intro Cloud Computing

Security. It’s not (only) what you think it needs to be.

Page 61: Intro Cloud Computing

Build a culture of collaboration.

Page 62: Intro Cloud Computing

Example: Google Apps

Cloud Application(Google Docs)

Cloud Client(Mozilla Firefox)

Cloud hardware(Apps Server)

Cloud Platform(Apps Engine)

Cloud Services(Word Processing)

BigTable

Cloud storage(BigTable DB)

Page 63: Intro Cloud Computing

issues that matter

Page 64: Intro Cloud Computing

Implications

possession of data

Page 65: Intro Cloud Computing

privacy

our data is hold by 3rd party

Page 66: Intro Cloud Computing

security

portability and preservation

Page 67: Intro Cloud Computing

“possession” of computation

Page 68: Intro Cloud Computing

market power

Page 69: Intro Cloud Computing

how big is the problem?

Page 70: Intro Cloud Computing

location

Page 71: Intro Cloud Computing

Understanding Cloud Computing

Page 72: Intro Cloud Computing

Origin

• “.. Comes from the early days of the Internet where we drew the network as a cloud… we didn’t care where the messages went… the cloud hid it from us” – Kevin Marks, Google

• First cloud around networking (TCP/IP abstraction)• Second cloud around documents (WWW data

abstraction)• The emerging cloud abstracts infrastructure complexities

of servers, applications, data, and heterogeneous platforms– (“muck” as Amazon’s CEO Jeff Bezos calls it)

Page 73: Intro Cloud Computing

3 Cloud Service Models

• Cloud Software as a Service (SaaS)– Use provider’s applications over a network

• Cloud Platform as a Service (PaaS)– Deploy customer-created applications to a cloud

• Cloud Infrastructure as a Service (IaaS)– Rent processing, storage, network capacity, and other

fundamental computing resources

• To be considered “cloud” they must be deployed on top of cloud infrastructure that has the key characteristics

Page 74: Intro Cloud Computing

Service Model ArchitecturesCloud Infrastructure

IaaS

PaaS

SaaS

Infrastructure as a Service (IaaS) Architectures

Platform as a Service (PaaS)Architectures

Software as a Service (SaaS)

Architectures

Cloud Infrastructure

SaaS

Cloud Infrastructure

PaaS

SaaS

Cloud Infrastructure

IaaS

PaaS

Cloud Infrastructure

PaaS

Cloud Infrastructure

IaaS

Page 75: Intro Cloud Computing

4 Cloud Deployment Models

• Private cloud – enterprise owned or leased

• Community cloud– shared infrastructure for specific community

• Public cloud– Sold to the public, mega-scale infrastructure

• Hybrid cloud– composition of two or more clouds

Page 76: Intro Cloud Computing

Common Cloud Characteristics

• Cloud computing often leverages:– Massive scale– Virtualization– Non-stop computing– Free software– Geographic distribution– Service oriented software – Autonomic computing– Advanced security technologies

Page 77: Intro Cloud Computing

is this GRID Computing?

Page 78: Intro Cloud Computing
Page 79: Intro Cloud Computing

Clouds aren’t all the same

• Not every cloud is a “grid”– Grids imply dynamic arrival/departure– Electrical analogy has limits: CPU cycles aren’t substitutable

• Most clouds are not “compute clusters”– Clusters are typically monocultures: just one type of node– Applications may require tuning to a particular cluster size

• Some clouds are servers in virtual slices– Virtualized servers can be quickly provisioned– Spin-up of instances = new management task– Hardware gets cheaper, management…not so much

• Enterprise cloud computing implies API leverage

– Immediate focus on function; immediate delivery of value

– Using appropriate frameworks enables a huge head start

Page 80: Intro Cloud Computing

Single tenancy gives each customer a dedicated software stack – and each layer in each stack still requires configuration, monitoring, upgrades, security updates, patches, tuning and disaster recovery.

On a multi-tenant platform, all applications run in a single logical environment: faster, more secure, more available, automatically upgraded and maintained. Any improvement appears to all customers at once.

Shared infrastructure

Other apps

ServerOS

DatabaseApp Server

StorageNetwork

App 1

ServerOS

DatabaseApp Server

StorageNetwork

App 2

ServerOS

DatabaseApp Server

StorageNetwork

App 3

Single-Tenant (vs) Multi-Tenant Architecture

Page 81: Intro Cloud Computing

Coherent Code Base and Managed InfrastructureCoherent Code Base and Managed Infrastructure

Your Clicks

Your Code

User Interface

Logic

Database

Metadata representations:Partitioned data, logic and customizations for multiple customers

Build strategic applications

Customize any aspect

Upgrade when convenient

Retain IP ownership

The technical part : Why multi-tenant matters

Page 82: Intro Cloud Computing

Virtual ServersVirtual Servers

Virtual ServersVirtual Servers

Virtual Servers

PaaS for theInquiring Developer

“Servers as a Service” PaaS as anApplication Framework

Infrastructure as a Service

Database as a Service

Integration as a Service

Logic as a Service

UI as a Service

Infrastructure as a Service Infrastructure as a Service

Database as a Service

Python App Server

~Familiar Developer ModelRapid Scalability

OfferingInnovative Technology

Supports Large-Scale SaaSDeep-Dyed Multitenancy

Database as a Service

PaaS Taxonamy : Proliferating Platforms

Page 83: Intro Cloud Computing
Page 84: Intro Cloud Computing

Thank you