cloud computing presentation v2

8/8/2019 Cloud Computing Presentation v2

1/40

CLOUD COMPUTING

An ISAS Presentation on


2/40

ACKNOWLEDGEMENT

We are thankful to NIIT for providing us such a platform to

prove ourselves and show our potential. We heartily showour gratitude towards Mr. Khownish Chatterjee our

respected faculty who guided us with the candle ofknowledge through the darkness of ignorance.


3/40

OVERVIEW


4/40

INTRODUCTION

Internet based computing working like a electric grid.

Can be used as a metaphor for Internet.

You dont need a software or a server to use them.

Uses the internet and central remote servers.

It is a byproduct and consequence of the ease-of-accessto remote computing sites provided by the Internet.


5/40

CONCEPT

Cloud computing is broken down into threesegments: "applications," "platforms," and"infrastructure.

Concept generally incorporates combinations ofthe following

1. Infrastructure as a service (IaaS)2. Platform as a service (PaaS)

3. Software as a service(SaaS)

Companies with large batch-oriented tasks canget results as quickly as their programs can

scale.

The infrastructure is shared.

The services are accessed on demand in unitsthat vary by service.


6/40

HISTORY

The underlying concept of cloud computing dates back to1960s, when John McCarthy opined that "computationmay someday be organized as a public utility".

The actual term "cloud" borrows from telephony in thattelecommunications companies, who until the 1990sprimarily offered dedicated point-to-point data circuits,

began offering Virtual Private Network (VPN) servicesgiving much lower cost.

Amazon played a key role in the development of cloudcomputing by modernizing their data centers after thedot-com bubble, which, like most computer networks,

were using as little as 10% of their capacity.


7/40

HISTORY

Amazon started providing access to their systems through AmazonWeb Service (AWS) on a utility computing basis in 2006.

In 2007, Google, IBM, and a number of universities embarked on alarge scale cloud computing research project. In early 2008,

Eucalyptus became the first open source AWS API compatibleplatform for deploying private clouds.

March of 2010, Microsoft's CEO, Steve Ballmer, made his strongeststatement of betting the company's future in the cloud byproclaiming "For the cloud, we're all in" and further stating "About75 percent of our folks are doing entirely cloud based or entirelycloud inspired, a year from now that will be 90 percent."


8/40

ROLE IN SERVICE ORIENTEDARCHITECTURE


9/40

FEATURES

Agility.

Cost

Reliability Scalability

security


10/40

FEATURES CONTD.

Location dependency

Multi-tenancy

1. Centralization

2. Peak load capacity3. Utilization and Efficiency.

Maintenance

Metering


11/40

APPLICATION AREAS


12/40

APPLICATION AREAS

Clients would be able to access their applicationsand data from anywhere at any time.

End user to cloud An end user can get easy access

to the cloud applications.

It could bring hardware costs down. You wouldn'tneed to buy the fastest memory with themost memory, because the cloud system would takecare of those needs for you.


13/40

APPLICATION AREAS

A lot of IT organization cant afford to invest insupercomputer-class infrastructure. Yet, the

business could benefit from access to some pretty

compute-intensive analytic applications. Backup and recovery.

Cloud computing systems give these organizationscompany-wide access to computer applications.Instead, the company could pay a metered fee to acloud computing company.


14/40

DEPLOYMENT MODELS


15/40

TYPES OF CLOUDS

1. Public cloud - Resources are dynamicallyprovisioned on a fine-grained.

2. Community Cloud - Established where several

organizations have similar requirements and seekto share infrastructure.

3. Hybrid Cloud - Environment consisting ofmultiple internal and/or external providers "will

be typical for most enterprises".


16/40

TYPES OF CLOUDS CONTD.

4. Private Cloud - The ideawas based upon directcomparison with otherindustries (e.g. theelectricity industry) andthe extensive use of hybridsupply models to balanceand mitigate risks.


17/40

ARCHITECTURE

Typically involves multiple cloudcomponents communicating with each other.

The two most significant components ofcloud computing architecture are known asthe front end and the back end.

The front end is the part seen by the client,i.e. the computer user. This includes theclients network (or computer) and theapplications used to access the cloud via auser interface such as Internet Explorer.

The back end of the cloud computingarchitecture is the cloud itself, comprisingvarious computers, servers and data storagedevices.


18/40

LAYER

Client - consists of computer hardwareand/or computer software.

Applications- Cloud application servicesor "Software as a Service (SaaS)" deliver

software as a service over the Internet.1. Network-based access.

2. Managed from central locations.

3. Closer to a one-to-many model.

4. Centralized feature updating.

Platform - Cloud platform services or"Platform as a Service (PaaS)" deliver acomputing platform and/or solutionstack as a service


19/40

LAYERS CONTD.

Infrastructure- Cloud infrastructure services or"Infrastructure as a Service (IaaS)" deliverscomputer infrastructure, typically a platform

virtualization environment as a service. Server - The servers layer consists of computer

hardware and/or computer software productsthat are specifically designed for the delivery of

cloud services.


20/40

DIFFERENT ASPECTS OF CLOUDCOMPUTING


21/40

COMMERCIAL CLOUD


22/40

RESEARCH

Universities, vendors and government organizations areinvesting in research.

IBM/Google Academic Cloud Computing Initiative (ACCI).

July 2008, HP, Intel Corporation and Yahoo! announced thecreation of a global, multi-data center, open source test bed

April 2009, the National Science Foundation joined theACCI.

July 2010, HP Labs India announced a new cloud-basedtechnology designed to simplify taking content and makingit mobile-enabled


23/40

INTERCLOUD

The Intercloud is an interconnected global "cloud of clouds.

The term was first used in the context of cloud computing in2007.

Based on the key concept that each single cloud does nothave infinite physical resources.

Raises many challenges concerning cloud federation,security, interoperability, QoS, monitoring and billing.

Combined many computer utilities together was originallydescribed by Douglas Parkhill.


24/40

STORAGE

Data is stored on multiple virtual servers.

Hosting companies operate large data centers.

The data center operators, in the background, virtualizes the

resources according to the requirements of the customer andexpose them as virtual servers.

StorageFacility


25/40

CLOUD VERSUS GRID

Full private cluster isprovisioned.

Individual user can onlyget a tiny fraction of thetotal resource pool.

No support for cloudfederation except

through the clientinterface.

Opaque with respect toresources.

Built so that individualusers can get most, if notall of the resources in a

single request.

Middleware approachtakes federation as a firstprinciple.

Resources are exposed,often as bare metal.

Cloud computing Grid computing

These differences mandate different architectures for each.


26/40

PROS AND CONS OF CLOUD COMPUTING

Governance Security, Privacy and control SLA guarantees Ownership and control Compliance and auditing

Sarbanes and Oxley Act

Reliability Good service provider with 99.999% availability

Cloud independence Vendor locking. Cloud provider goes out of business

Data Security Cloud locking and Loss of control.

Plan for moving data along with Cloud provider

Cost.

Simplicity. Tools. Controls on sensitive data.

Out of business

Big and small Scalability and cost outweigh reliability for small businesses Big businesses may have a problem


27/40

MICROSOFT AND AMAZON FACE CHALLENGES

Globus/Nimbus Client-side cloud-computing interface to Globus-enabled TeraPort cluster at U of C Based on GT4 and the Globus Virtual Workspace Service Shares upsides and downsides of Globus-based grid technologies

Enomalism (now called ECP) Start-up company distributing open source

REST APIs

Reservoir European open cloud project Many layers of cloud services and tools Ambitious and wide-reaching but not yet accessible as an implementation

Eucalyptus Cloud Computing on Clusters Amazon Web Services compatible

Supports kvm and Xen Open Nebulous

Joyent Based on Java Script and Git


28/40

CLOUD INFRASTRUCTURE

Storage Networking Coolant

Control CenterStorage Network Cables


29/40

CLOUD INFRASTRUCTURE

Network operationscenter

Physical Infrastructure Physical Security

Power infrastructure Network Cabling Fire safety


30/40

WHY CLOUD COMPUTING?

Changed the face of IT.

Gives advantage to major companies.

Practical and Effective characteristics.

Introduction toHybrid approach.


31/40

CLOUD COMPUTING AND SOA.

Complementary to each other.

Can be pursued independently.

Cannot replace each other.

Budget issues.

Platform and scalability issues.


32/40

WHAT IS CLOUD?


33/40

CHALLENGES IN IMPLEMENTATION


34/40

THE OBSTACLES

Business Continuity and Service Availability.

Data Lock-In.

Data Confidentiality/Auditability.

Data Transfer Bottlenecks.

Performance Unpredictability.


35/40

THE OBSTACLES CONTD.

Scalable Storage.

Bugs in Large-Scale Distributed Systems.

Scaling Quickly.

Reputation Fate Sharing.

Software Licensing.


36/40

CONCLUSION

We predict cloud computing will grow.

Applications software needs to both scale downrapidly as well as scale up.

Infrastructure software must be aware that it is nolonger running on bare metal.

Hardware systems should be designed at the scaleof a container (at least a dozen racks), which will bethe minimum purchase size.


37/40

CREDITS

Indraneel Banik Majumdar

Cessna Bhattacharya

Probuddho Ganguly

Daipayan Banerjee

Tanusree Majumdar

Md. Faizan Ahmed

Sandip Dutta Biplab dey


38/40

THANK YOU VIEWING OURPRESENTATION


39/40


40/40

GRID COMPUTING

Share Computers and data Evolved to harness inexpensive computers in Data center to solve variety of problems Harness power of loosely coupled computers to solve a technical or mathematical problem Used in commercial applications for drug discovery, economic forecasting, seismic analysis

and back-office Small to big

Can be confined to a corporation

Large public collaboration across many companies and networks Most grid solutions are built on

Computer Agents Resource Manager Scheduler

Compute grids Batch up jobs

Submit the job to the scheduler, specifying requirements and SLA(specs) required forrunning the job Scheduler matches specs with available resources and schedules the job to be run Farms could be as large as 10K cpus

Most financial firms has grids like this Grids lack automation, agility, simplicity and SLA guarantees

back

cloud computing presentation v2

Documents