Introduction to Cloud Computing

(1)

Introduction to Cloud Computing

Iván Carrera

Institute of Informatics - UFRGS

September 2013

(2)

Virtualization Characteristics of Cloud Computing Service Models and Deployment Architecture of Services High Avalaibility Architecture

Outline

Virtualization

Characteristics of Cloud Computing Service Models and Deployment Architecture of Services

High Avalaibility Architecture

Iván Carrera Introduction to Cloud Computing

(3)

References

I Mell, P., & Grance, T. (2011). The NIST denition of cloud computing (draft).NIST special publication, 800, 145.

I Bojanova, I., & Samba, A. (2011, March). Analysis of Cloud Computing Delivery Architecture Models. In Advanced

Information Networking and Applications (WAINA), 2011 IEEE Workshops of International Conference on (pp. 453-458).

IEEE.

I Panorama du Cloud Computing, Didier Donsez, Noël de Palma, Alain Tchana, LIG ERODS. ICAR 2013 Cloud Computing.

(4)

Section 1 Virtualization

(5)

(6)

Denitions

Cloud Computing

I a computational model for enabling ubiquitous, convenient, on-demand network access to a shared pool of congurable computing resources

I that can be rapidly provisioned and released with minimal management eort or service provider interaction.

I 5 essential characteristics,

I 3 service models, and

I 4 deployment models.

(7)

Denitions

Cloud Infrastructure

I the collection of hardware and software that enables the ve essential characteristics of cloud computing.

I It can be viewed as containing both a physical layer and an abstraction layer.

I The physical layer consists of hardware: server, storage and network components.

I The abstraction layer consists of software deployed across the physical layer, which manifests the essential cloud

characteristics.

(8)

Denitions

Essential Characteristics

I On-demand self-service. A consumer can unilaterally provision computing capabilities.

I Broad network access. Capabilities are available over the network and accessed through standard mechanisms.

I Resource pooling. Resources are pooled to serve multiple consumers using a multi-tenant model.

I Rapid elasticity. Capabilities can be elastically provisioned and released, in some cases automatically.

I Measured service. Cloud systems automatically control and optimize resource use by leveraging a metering capability.

(9)

Denitions

Economic Models

I Free Free-tier period.

I On-demand Duration and quantity of used resources (bandwidth, I/O, CPU time, RAM).

I Year/Month Subscription Levels of SLA, QoS.

I Auction Spot instances.

I Re-sellers 3rd party sellers.

(10)

Denitions

Benets

I Quick allocation/des-allocation (on-demand) of resources.

I 24/7 access from a browser.

I Ease of use.

I Smaller TCO.

I lesser personnel

I pay for what you use

I Ease of payment.

I not need for a big budget

I using vs. payment

(11)

Denitions

Challenges

I Security and Trust.

I Warranty of service (SLA).

I Energetic eciency/impact.

I Detailed monitoring for billing.

I Standardization.

I to ease interoperability and portability

I For applications and customized hardware.

(12)

Section 3 Service Models and Deployment

(13)

Service Models

Software as a Service (SaaS).

I The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure.

I The applications are accessible from various client devices through either a thin client interface, or a program interface.

I The consumer does not manage or control the underlying cloud infrastructure:

I network, servers, operating systems, storage, or even individual application capabilities

(14)

Service Models

Platform as a Service (PaaS).

I The capability provided to the consumer is to deploy applications onto the cloud infrastructure

I using programming languages, libraries, services, and tools supported by the provider.

I network, servers, operating systems, storage, or even individual application capabilities

(15)

Service Models

Infrastructure as a Service (IaaS).

I The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources

I where the consumer is able to deploy and run arbitrary software,

I including operating systems and applications.

I but has control over operating systems, storage, and deployed applications

(16)

Service Models

(17)

Service Models

(18)

Deployment Models

Private cloud.

I provisioned for exclusive use by a single organization

I It may be owned, managed, and operated by the organization, or a third party,

I and it may exist on or o premises.

Community cloud.

I provisioned for exclusive use by a specic community of consumers from organizations that have shared concerns

I It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or o premises.

(19)

Deployment Models

Public cloud.

I provisioned for open use by the general public.

I It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them.

I It exists on the premises of the cloud provider.

Hybrid cloud.

I a composition of two or more distinct cloud infrastructures that remain unique entities,

I but are bound together by standardized or proprietary technology that enables data and application portability.

(20)

Service Models

Actors in a Cloud

I Provider Owner of the hardware.

I Re-seller Gives users services, but doesn't own the hardware.

I User

I Developer Produces tools for cloud.

(21)

(22)

Azure Platform

(23)

Elastic Compute Cloud

(24)

Section 5 High Avalaibility Architecture

(25)

References

I ARC202 Architecting for High Availability - AWS re: Invent 2012 by Amazon Web Services on Nov 29, 2012

I Weygant, P. S. (2001). Clusters for High Availability: A Primer of HP Solutions. Prentice Hall.

(26)

Denitions

Amazon Web Services (AWS)

I Cloud provider

I Platform for highly available systems

I Reliable, costable, failure-tolerant,

I with minimun human interaction.

(27)

Denitions

High Availability

(28)

Denitions

High Availability

I Availability

I Period of time when services are available, or time required for a system response

I any loss is considered an interruption

I Highly available

I A system designed to avoid service losses, reducing and managing failures

I It is required for important services (life, health, wealth)

I Any loss is not acceptable

(29)

Denitions

IT High Availability

I As important as electric energy

I Is not the same as unlimited availability and always will relate to the service

(30)

(31)

(32)

(33)

(34)

(35)

(36)

(37)

(38)

(39)

(40)

(41)

(42)

(43)

(44)

(45)

(46)

(47)

So, can your grid do that?

Introduction to Cloud Computing