Cloud Computing

Vania Marangozova-Martin

ibd.forge.imag.fr
 Some remarks on cloud definitions
u Anonymous:
[...] unfortunately the marketing guys got hold of the
term before the technicians had known what Cloud
Computing is [...]

V.Marangozova-Martin IBD 2
Some cloud computing definitions
u UCBerkeley RADLabs:
Cloud computing has the following characteristics:
(1) The illusion of infinite computing resources...
(2) The elimination of an up-front commitment by Cloud users...
(3). The ability to pay for use...as needed...
business perspective
u Wikipedia:
Cloud computing, also on-demand computing, is a kind of
Internet-based computing that provides shared processing
resources and data to computers and other devices on demand.
It is a model for enabling ubiquitous, on-demand access to a
shared pool of configurable computing resources"
technical perspective

V.Marangozova-Martin IBD 3
Some cloud computing definitions (2)
u Gartner: ...a style of computing in which scalable and
elastic IT-enabled capabilities are delivered as a service
to external customers using Internet technologies.

u National Institute of Standards and Technology

(NIST) Cloud computing is a model for enabling
ubiquitous, convenient, on-demand network access to a
shared pool of configurable computing resources (e.g.,
networks, servers, storage, applications, and services)
that can be rapidly provisioned and released with
minimal management effort or service provider
interaction.

V.Marangozova-Martin IBD 4
A more somplified definition

u Cloud computing is a specialized form of

distributed computing that introduces
utilization models for remotely provisioning
scalable and measured resources.

From
Cloud Computing: Concepts, Technology and
Architecture, Thomas Erl, Prentice Hall, 2013

V.Marangozova-Martin IBD 5
Understanding Cloud Computing:
A little bit of history

u Utility computing: John McCarthy , 1961

v If computers of the kind I have advocated become the
computers of the future, then computing may someday be
organized as a public utility just as the telephone system is a
public utility. ... The computer utility could become the basis of
a new and important industry.
u 1990s, Salesforce.com pioneered the notion of bringing
remotely provisioned services into the enterprise.
u 2002, Amazon launched Amazon Web Services (AWS)
v A suite of enterprise-oriented services that provide remotely
provisioned storage, computing resources, and business
functionality.
u 2006, Amazon Elastic Compute Cloud (EC2)
V.Marangozova-Martin IBD: Fundamental Cloud Computing 6
Drivers for cloud computing
u Capacity Planning
v the process of determining and fulfilling future demands of an
organizations IT resources, products, and services
Lead Strategy: adding capacity to an IT resource in anticipation of demand
Lag Strategy: adding capacity when the IT resource reaches its full capacity
Match Strategy: adding IT resource capacity in small increments, as demand
increases
u Cost Reduction
v A direct alignment between IT costs and business performance can be
difficult to maintain
cost of acquiring new infrastructure
cost of its ongoing ownership
u Agility
v Businesses need to adapt and evolve to successfully face change
v respond to business change by scaling its IT resources

V.Marangozova-Martin IBD: Fundamental Cloud Computing 7

Major Technology Innovations
that made the cloud possible

u Clustering
v concept of
built-in redundancy
and failover

u Grid Computing
v more distributed,
large-scale,
ubiquitous,
v cloud computing is a
descendant
V.Marangozova-Martin IBD: Fundamental Cloud Computing 8
Major Technology Innovations
that made the cloud possible (2)

u Virtualization
v allows physical IT resources to provide multiple virtual
images of themselves so that their underlying
processing capabilities can be shared by multiple
users.

V.Marangozova-Martin IBD: Fundamental Cloud Computing 9

Enabling technologies

u Broadband Networks and Internet

Architecture
u Data Center Technology

u Web Technology

u Multitenant Technology

u Service Technology

V.Marangozova-Martin IBD: Fundamental Cloud Computing 10

Terminology (1)
u Cloud
v distinct IT environment that is designed for the
purpose of remotely provisioning scalable and
measured IT resources
v As a specific environment used to remotely provision
IT resources, a cloud has a finite boundary

V.Marangozova-Martin IBD: Fundamental Cloud Computing 11

Terminology (2)

u IT Resource
v a physical or virtual IT-related artifact that can be
either software-based, or hardware-based

V.Marangozova-Martin IBD: Fundamental Cloud Computing 12

Terminology (3)

u Cloud Consumer
v the party that uses cloud-based IT resources
u Cloud Provider
v the party that provides the IT resources

V.Marangozova-Martin IBD: Fundamental Cloud Computing 13

Terminology (4)

u Scaling
v the ability of the IT resource to handle increased
or decreased usage demands

V.Marangozova-Martin IBD: Fundamental Cloud Computing 14

Cloud Characteristics
u On-demand usage
v the consumer decides what and how many IT
resources he/she needs
u Ubiquitous access
v wide access (devices, protocols, )
to cloud services
u Multitenancy (and resource pooling)
v one instance serves different consumers
v related to virtualzation
v IT resources can be dynamically assigned and
reassigned
V.Marangozova-Martin IBD 15
Cloud Characteristics (2)
u Elasticity
v automated ability of a cloud to transparently scale IT
resources
v related to cost optimization
u Measured usage
v ability of a cloud platform to keep track of the usage of
its IT resources, primarily by cloud consumers
v related to cost management
u Resiliency
v distribution of redundant implementations of IT
resources across physical locations

V.Marangozova-Martin IBD 16
Cloud Deployment:
Public-/Hybrid-/Private-Cloud

V.Marangozova-Martin IBD 17
Private/public cloud
u Private cloud is cloud infrastructure operated
solely for a single organization
v complex, costly, risky
v but may improve business significantly
u A cloud is called a "public cloud" when the
services are rendered over a network that is
open for public use. Public cloud services may
be free.
v Public cloud service providers like Amazon AWS,
Microsoft and Google own and operate the
infrastructure at their data center and access is
generally via the Interne
V.Marangozova-Martin IBD 18
Cloud Delivery Models

u Infrastructure-as-a-Service(IaaS)

u Platform-as-a-Service(PaaS)

u Software-as-a-Service(SaaS)

u Differ in what is provided to the consumer

V.Marangozova-Martin IBD 19
V.Marangozova-Martin IBD 20
V.Marangozova-Martin IBD 21
IaaS

u Include hardware, network, connectivity,

operating systems, and other raw IT
resources.
u IaaS provides IT resources that are
virtualized and packaged into bundles that
simplify up-front runtime scaling and
customization of the infrastructure

V.Marangozova-Martin IBD 22
IaaS

V.Marangozova-Martin IBD 23
IaaS

V.Marangozova-Martin IBD 24
IaaS
u Developers create virtual machines (VMs) on
demand
v They have full access to these VMs
u Strengths:
v Can control and configure environment
v Familiar technologies
u Weaknesses:
v Must control and configure environment
v Requires administrative skills to use

V.Marangozova-Martin IBD 25
PaaS

u PaaS represents a pre-defined ready-to-use

environment typically comprised of already
deployed and configured IT resources
v predefined network, storage, computing services
v predefined ways of using them
v predefined development environments

V.Marangozova-Martin IBD 26
PaaS

V.Marangozova-Martin IBD 27
PaaS

V.Marangozova-Martin IBD 28
PaaS

u Developers provide an application, which the

platform runs
v They dont work directly with VMs
u Strengths:
v Provides higher-level services than IaaS
v Requires essentially no administrative skills
u Weaknesses:
v Allows less control of the environment
v Can be harder to migrate existing software

V.Marangozova-Martin IBD 29
SaaS

u A software program positioned as a shared,

reusable cloud service

V.Marangozova-Martin IBD 30
SaaS

V.Marangozova-Martin IBD 31
Relational Storage

u Traditional relational storage in the cloud

v With support for SQL
u Strengths:
v Familiar technologies
v Many available tools, e.g., for reporting
v Limited data lock-in
v Can be cheaper than on-premises relational
storage
u Weaknesses:
v Scaling to handle very large data is challenging
V.Marangozova-Martin IBD 32
No SQL Storage (Scale-out)

u Massively scalable storage in the cloud

u Strengths:
v Scaling to handle very large data is
straightforward
v Can be cheaper than relational storage
u Weaknesses:
v Unfamiliar technologies
v Few available tools
v Significant data lock-in

V.Marangozova-Martin IBD 33
Storage Blobs

u Storage for Binary Large OBjects in the cloud

v Such as video, back-ups, etc.
u Strengths:
v Globally accessible way to store and access large
data
v Can be cheaper than on-premises storage
u Weaknesses:
v Provides only simple unstructured storage

V.Marangozova-Martin IBD 34
Cloud Overview
Private Public
Computing Storage
IaaS IaaS PaaS Relationa Scale-Out Blobs
l
For
Hyper-V Hosters: Windows SQL Windows Windows
Microsoft
Micros Cloud Hyper-V Azure Azure Azure Azure
Tables Blobs
oft Cloud
Cloud Cloud
VMwar For
VMWare vCloud Hosters: Foundry Foundry
Storage
e vCloud Frameworks

Elastic Relational Simple

Elastic
Amazo
Amazon Eucalyptus Compute
Cloud Beanstalk
Database
Service
SimpleDB Storage
Service
n (EC2) (RDS) (S3)

App
Googl
Google Engine Datastore Blobstore
e
AppForce
Salesforce Database
VMForce .com

V.Marangozova-Martin IBD 35
Cloud Costs

u Cost metrics
v Network Usage:
inbound/outbound traffic, IP allocation, load-balancing,
firewall traffic,
v Server Usage
how many VMs, how long
v Storage Usage
how much space, access rate (I/O)
v Cloud Service Usage
duration of usage, number of users, number of
transactions

V.Marangozova-Martin IBD 36
Cloud Hype

u The cloud is cheaper

u Thecloud business model is growing at an

unparalleled pace without any limit in sight

u In the future everything will be on the cloud

... can we find evidence to support, or refute,

such claims?

37
Gartner Hype Cycle
u Gartner, Inc. is an American information technology
research and advisory firm providing technology related
insight
u Hype Cycle = representing the maturity, adoption and
social application of specific technologies

V.Marangozova-Martin IDS 38
Gartner Hype Cycle

V.Marangozova-Martin IDS 39
Challenges to Adoption

u Understanding of the Paradigm

v Lack of agreement over what exactly constitutes
cloud computing
v Confusion over what benefits cloud computing will
provide, and the trade-offs
v Multi-Tenancy:
How comfortable is an enterprise in storing its data in an
environment shared with other customers?
What is the risk and the mitigation for data leakage?
v Outrageous Vendor Claims and Obfuscation of
Challenges:
Hinder understanding of cloud computing
What exactly are we buying?
40
Challenges to Adoption (continued)

u Understanding of the Paradigm (continued)

v Role changes: The CIO (or equivalent) may need
to evolve to a general contractor in many areas.
v Lock-In:
How difficult would it be to move large volumes of data
to a different cloud (cloud provider)?
This is both a procedural and a technical issue
(format, bandwidth)

41
Challenges to Adoption (continued)

u Implementation and Operations

v Architecture:
There is much disagreement over the necessary
elements for a cloud technical architecture
In addition, SOA is the best approach for interface to
clouds, yet culture for SOA success is immature and
poorly understood.
Discussion over common cloud APIs, but none exist
v Manageability: from the user perspective:
Existing management tools do not seem to be able to
track metrics for applications that may reside on a
varying number of different systems
42
Challenges to Adoption (continued)
u Implementation and Operations (continued)
v Loss of control: Will business elements of the
enterprise bypass the enterprises IT organization?
v Governance:
Is governance antithetical to the concept of cloud?
Will lack of governance aggravate problems already
associated with lack of SOA governance?
v Provisioning: For SaaS, how will applications and
application components be provisioned?
v Licensing: Vendors have been slow to develop
appropriate models.
v Confidence as to reliability, scalability, and security in
public clouds
43
Challenges to Adoption (continued)

u Implementation and Operations (continued)

v Service-Level Agreements: There have been
effectively no substantive guarantees from public
cloud providers.

44
Challenges to Adoption (continued)

u Security and Compliance

v Threat Models: What new models arise in the
cloud? Have we further aggravated issues
already present within SOA and with standard
computing vulnerabilities?
v Cross-Domain Security: How does an
organization extend or federate its authentication
and authorization mechanisms into the cloud?
v Data-at-Rest Security: What encryption and
segregation mechanisms are provided?
v Auditability: Can access to the data be audited?
45
Challenges to Adoption (continued)

u Security and Compliance (continued)

v Accreditation in the Cloud:
How can you tell a cloud is secure?
Is there governing policy and procedures to accredit a
cloud?
What processes and controls must be in place? (Pre-
accredited clouds may actually simplify this process)

46
Challenges to Adoption (continued)
u Security and Compliance (continued)
v Compliance: May preclude cloud paradigm in some cases due to:
Physical chain of custody requirements
Regulatory requirements
v Physical Location:
Do you know what country your cloud resides in?
Would you know if it changed?
What compliance requirements change?
Is there governing law that recognizes the paradigm?
u Conclusions:
v There are many challenges to adoption of the cloud paradigm
v Public clouds and private clouds have different sets of
challenges, with some overlap

47
The last word

u Joni Mitchell summed it up best:

I've looked at clouds from both sides now
From up and down, and still somehow
It's cloud illusions I recall...
I really don't know clouds at all

u The
cloud is a very complex marketplace and
evolving rapidly.
v Economics are the key
v But nobody really understands cloud economics
v There are many barriers to entry
48
References

u Cloud Computing: Concepts, Technology and

Architecture, Thomas Erl, Prentice Hall, 2013
v http://whatiscloud.com
u Ken Birman
http://www.cs.cornell.edu/courses/
CS5412/2015sp/Syllabus.htm

V.Marangozova-Martin IBD 49