Distributed and Cloud Computing

K. Hwang, G. Fox and J. Dongarra

Chapter 4: Cloud Platform Architecture

over Virtualized Datacenters
Adapted from Kai Hwang
University of Southern California

Copyright © 2012, Elsevier Inc. All rights reserved. 1 1-1

CLOUD COMPUTING AND SERVICE MODELS

 Public, Private, and Hybrid Clouds

 Centralized versus Distributed Computing
 Public Clouds
 Private Clouds
 Hybrid Clouds
 Data-Center Networking Structure
 Cloud Development Trends

2
Public, Private & Hybrid Clouds

3
 Public Clouds vs. Private Clouds :
Characteristics Public clouds Private clouds
Technology Leverage existing IT infrastructure and
leverage and Owned by service providers personnel; owned by individual
ownership organization

Creating and managing VM instances within

Management of
proprietary infrastructure; promote Client managed; achieve customization
provisioned
standardization, preserves capital and offer higher efficiency
resources
investment, application flexibility

Workload
Handle workload without communication Handle workload dynamically, but can
distribution
dependency; distribute data and VM better balance workloads; distribute
methods and
resources; surge workload is off-loaded data and VM resources
loading policies

Security and Access is limited; provide pre-

Publicly accessible through remote
data privacy production testing and enforce data
enforcement interface privacy and security policies

Example Google App Engine, Amazon AWS,

platforms Microsoft Azure
IBM RC2

Copyright © 2012, Elsevier Inc. All rights reserved. 4 1-4

5
CLOUD COMPUTING AND SERVICE MODELS

 Cloud Ecosystem and Enabling Technologies

 Cloud Design Objectives
 Cost Model
 Cloud Ecosystems
 Surge of Private Clouds

6
7
Cloud Ecosystem and Enabling Technologies
 Cloud Design Objectives
 Shifting computing from desktops to data centers
 Service provisioning and cloud economics
 Scalability in performance
 Data privacy protection
 High quality of cloud services
 New standards and interfaces

8
Cost-Effectiveness in Cloud Computing
vs. Datacenter Utilization
(Courtesy of M. Ambrust, et al 2009)

Copyright © 2012, Elsevier Inc. All rights reserved. 9 1-9

Copyright © 2012, Elsevier Inc. All rights reserved. 10 1 - 10
CLOUD COMPUTING AND SERVICE MODELS

 Infrastructure-as-a-Service (IaaS)
 Infrastructure as a Service

11
Infrastructure as a service (IaaS)
Most basic cloud service model
Cloud providers offer computers, as physical or more often
as virtual machines, and other resources.
Virtual machines are run as guests by a hypervisor, such
as Xen or KVM.
Cloud users deploy their applications by then installing
operating system images on the machines as well as their
application software.
Cloud providers typically bill IaaS services on a utility
computing basis, that is, cost will reflect the amount of
resources allocated and consumed.
Examples of IaaS include: Amazon CloudFormation (and
underlying services such as Amazon EC2), Rackspace
Cloud, Terremark, and Google Compute Engine.
12
Copyright © 2012, Elsevier Inc. All rights reserved. 13 1 - 13
Some IaaS Offerings from Public Clouds :

Copyright © 2012, Elsevier Inc. All rights reserved. 14 1 - 14

15
Platform as a service (PaaS)
Cloud providers deliver a computing platform
typically including operating system, programming
language execution environment, database, and
web server.
Application developers develop and run their
software on a cloud platform without the cost and
complexity of buying and managing the underlying
hardware and software layers.
Examples of PaaS include: Amazon Elastic
Beanstalk, Cloud Foundry, Heroku, Force.com,
EngineYard, Mendix, Google App Engine, Microsoft
Azure and OrangeScape.

16
PaaS Offerings from Public Clouds

Copyright © 2012, Elsevier Inc. All rights reserved. 17 1 - 17

18
Software as a service (SaaS)
Cloud providers install and operate application
software in the cloud and cloud users access the
software from cloud clients.
The pricing model for SaaS applications is
typically a monthly or yearly flat fee per user, so
price is scalable and adjustable if users are added
or removed at any point.
Examples of SaaS include: Google Apps,
innkeypos, Quickbooks Online, Limelight Video
Platform, Salesforce.com, and Microsoft Office 365.

19
 DATA-CENTER DESIGN AND INTERCONNECTION
NETWORKS
Warehouse-Scale Computer (WSC)
 Provides Internet services
 Search, social networking, online maps, video sharing, online
shopping, email, cloud computing, etc.
 Differences with HPC “clusters”:
 Clusters have higher performance processors and network
 Clusters emphasize thread-level parallelism, WSCs emphasize
request-level parallelism
 Differences with datacenters:
 Datacenters consolidate different machines and software into
one location
 Datacenters emphasize virtual machines and hardware
heterogeneity in order to serve varied customers
(Courtesy of Hennessy and Patterson, 2012)

Copyright © 2012, Elsevier Inc. All rights reserved. 20 1 - 20

Design Considerations for WSC:
 Cost-performance
 Small savings add up
 Energy efficiency
 Affects power distribution and cooling
 Work per joule
 Dependability via redundancy
 Network I/O
 Interactive and batch processing workloads
 Ample computational parallelism is not important
 Most jobs are totally independent
 “Request-level parallelism”
 Operational costs count
 Power consumption is a primary constraint when designing system
 Scale and its opportunities and problems
 Can afford customized systems since WSC require volume purchase

(Courtesy of Hennessy and Patterson, 2012)

Copyright © 2012, Elsevier Inc. All rights reserved. 21 1 - 21

Typical Datacenter Layout

Copyright © 2012, Elsevier Inc. All rights reserved. 22 1 - 22

 Power and Cooling Requirements
 Cooling system also uses water (evaporation and spills)
 E.g. 70,000 to 200,000 gallons per day for an 8 MW facility

 Power cost breakdown:

 Chillers: 30-50% of the power used by the IT equipment
 Air conditioning: 10-20% of the IT power, mostly due to fans

 How many servers can a WSC support?

 Each server:
 “Nameplate power rating” gives maximum power consumption
 To get actual, measure power under actual workloads
 Oversubscribe cumulative server power by 40%, but monitor power
closely
(Courtesy of Hennessy and Patterson, 2012)

Copyright © 2012, Elsevier Inc. All rights reserved. 23 1 - 23

 (Courtesy of Luiz Andre Barroso and Urs Holzle, Google Inc., 2009)

Copyright © 2012, Elsevier Inc. All rights reserved. 24 1 - 24

Measuring Efficiency of a WSC
 Power Utilization Effectiveness (PEU)
 = Total facility power / IT equipment power
 Median PUE on 2006 study was 1.69
 Performance
 Latency is important metric because it is seen by
users
 Bing study: users will use search less as
response time increases
 Service Level Objectives (SLOs)/Service Level
Agreements (SLAs)
 E.g. 99% of requests be below 100 ms

(Courtesy of Hennessy and Patterson, 2012)

Copyright © 2012, Elsevier Inc. All rights reserved. 25 1 - 25

A fat-tree Interconnection of modular data Centers

26
Modular Data Center

27
Data-Center Management Issues
 Making common users happy
 Controlled information flow
 Multiuser manageability
 Scalability to prepare for database growth
 Reliability in virtualized infrastructure
 Low cost to both users and providers
 Security enforcement and data protection
 Green information technology

28
Cloud Computing
 WSCs offer economies of scale that cannot
be achieved with a datacenter:
 5.7 times reduction in storage costs
 7.1 times reduction in administrative costs
 7.3 times reduction in networking costs
 This has given rise to cloud services such as
Amazon Web Services
 “Utility Computing”
 Based on using open source virtual machine and
operating system software
(Courtesy of Hennessy and Patterson, 2012)

Copyright © 2012, Elsevier Inc. All rights reserved. 29 1 - 29

ARCHITECTURAL DESIGN OF COMPUTE AND
STORAGE CLOUDS
 1. A Generic Cloud Architecture Design
 Cloud Platform Design Goals
 Enabling Technologies for Clouds
 Generic Cloud Architecture

30
Enabling Technologies for The Clouds

Copyright © 2012, Elsevier Inc. All rights reserved. 31 1 - 31

32
ARCHITECTURAL DESIGN OF COMPUTE AND
STORAGE CLOUDS
 2. Layered Cloud Architectural Development
 Market-Oriented Cloud Architecture
 Quality of Service Factors

33
Cloud Computing as A Service

Copyright © 2012, Elsevier Inc. All rights reserved. 34 1 - 34

Copyright © 2012, Elsevier Inc. All rights reserved. 35 1 - 35
 Virtualization Support and Disaster Recovery
 Hardware Virtualization
 Virtualization Support in Public Clouds
 Storage Virtualization for Green Data Centers
 Virtualization for IaaS
 VM Cloning for Disaster Recovery

36
Virtualized
servers,
storage , and
network for
cloud platform
construction

Copyright © 2012, Elsevier Inc. All rights reserved. 37 1 - 37

Copyright © 2012, Elsevier Inc. All rights reserved. 38 1 - 38
VM Cloning for Disaster Recovery
 1.Service Availability and Data Lock-in Problem
 2.Data Privacy and Security Concerns
 3.Unpredictable Performance and Bottlenecks
 4.Distributed Storage and Widespread Software
Bugs
 5.Cloud Scalability, Interoperability, and
Standardization
 6.Software Licensing and Reputation Sharing

39
Challenges/Issues in Cloud Computing

40
Copyright © 2012, Elsevier Inc. All rights reserved. 40 1 - 40
Challenges in Cloud Computing (1)
 Concerns from The Industry (Providers)
 Replacement Cost
 Exponential increase in cost to maintain the infrastructure
 Vendor Lock-in
 No standard API or protocol can be very serious
 Standardization
 No standard metric for QoS is limiting the popularity
 Security and Confidentiality
 Trust model for cloud computing
 Control Mechanism
 Users do not have any control over infrastructures

Copyright © 2012, Elsevier Inc. All rights reserved. 41 1 - 41

 Challenges in Cloud Computing (2)
 Concerns from Research Community :
 Conflict to legacy programs
 With difficulty in developing a new application due to lack of control
 Provenance
 How to reproduce results in different infrastructures
 Reduction in Latency
 No specially designed interconnect used
 Very low controllability in layout of interconnect due to abstraction
 Programming Model
 Hard to debug where programming naturally error-prone
 Details about infrastructure are hidden
 QoS Measurement
 Especially for ubiquitous computing where context changes
Copyright © 2012, Elsevier Inc. All rights reserved. 42 1 - 42
Public Clouds and Service Offerings

43
Copyright © 2012, Elsevier Inc. All rights reserved. 44 1 - 44
Platform as a Service (PaaS): Google App Engine
 This platform allows users to develop and host web application in Google
datacenters with automatic scaling according to the demand.

 It is a free service for a certain limit and it only requires a Gmail account to
access the services. After the free limit is exceeded the customers are
charged for additional storage, bandwidth and instance hours.

 The current version supports Java, Python and Go as the programming

languages and Google plans to add more languages in the future.

 All billed App Engine applications have a 99.95% uptime SLA. App Engine is
designed to sustain multiple datacenter outages without any downtime.

 The app engine has a few restrictions - can only execute code called from
an HTTP request, Java applications may only use a subset from the JRE
standard edition and Java application cannot create new threads.

Copyright © 2012, Elsevier Inc. All rights reserved. 45 1 - 45

Google AppEgine (GAE)

Copyright © 2012, Elsevier Inc. All rights reserved. 46 1 - 46

Copyright © 2012, Elsevier Inc. All rights reserved. 47 1 - 47
AWS – a leader in providing public IaaS services.
services
 EC2 (Elastic compute cloud allows users to rent virtual computers to run their own
computer applications. It allows scalable deployment. A user can create, launch, and
terminate server instances as needed, paying by the hour for active servers.
 S3 (simple storage service) provides the object-oriented storage service for users.
 EBS (Elastic block service) provides the block storage interface which can be used to
support traditional applications.
 Amazon DevPay is a simple to use online billing and account management service that
makes it easy for businesses
 MPI clusters uses hardware-assisted virtualization instead of para-virtualization and users
are free to create a new AMIs
 AWS import/export allows one to ship large volumes of data to and from EC2 by shipping
physical discs.
 Brokering systems offer a striking model for controlling sensors and providing office support
of smartphones and tablets.
 Small-business companies can put their business on the Amazon cloud platform. Using
AWS they can service a large number of internet users and make profits through those paid
services.
Copyright © 2012, Elsevier Inc. All rights reserved. 48 1 - 48
Amazon Web Services (AWS)

Copyright © 2012, Elsevier Inc. All rights reserved. 49 1 - 49

Amazon’s Lesson
 Down for 3 days since
4/22/2011
 1000x of businesses went
offline. E.g. Pfizer, Netflix,
Quora, Foursquare,Reddit
 SLA contract
 99.95% availability
(<4.5hour down ）
 10% penalty, otherwise

Copyright © 2012, Elsevier Inc. All rights reserved. 50 1 - 50

Microsoft Azure Cloud :
This is essentially a PaaS Cloud.

• Windows Azure run its cluster hosted at Microsoft's datacenters

that manages computing and storage resources.
• One can download Azure development kit to run a local version
of Azure. It allows Azure applications to be developed and
debugged one the windows 7 hosts.
• All cloud services can interact with traditional MS software
applications such as Windows Live, Office Live, Exchange Online,
etc.
• If offers a Windows-based cloud platform using Microsoft
virtualization technology.
• Applications are built on VM’s deployed on the data-center
services.
• Azure manages all servers, storage and network resources
of the data center.

Copyright © 2012, Elsevier Inc. All rights reserved. 51 1 - 51

Microsoft Windows Azure

Copyright © 2012, Elsevier Inc. All rights reserved. 52 1 - 52

Cloud Services and Major Providers

Copyright © 2012, Elsevier Inc. All rights reserved. 53 1 - 53

Copyright © 2012, Elsevier Inc. All rights reserved. 54 1 - 54
Ex'  X

Security and Trust Barriers

in Cloud Computing
 Protecting datacenters must first secure cloud resources and
uphold user privacy and data integrity.

 Trust overlay networks could be applied to build reputation

systems for establishing the trust among interactive
datacenters.

 A watermarking technique is suggested to protect shared data

objects and massively distributed software modules.

 These techniques safeguard user authentication and tighten

the data access-control in public clouds.

 The new approach could be more cost-effective than using the

traditional encryption
Copyright © and firewalls
2012, Elsevier Inc. All rights to secure the55clouds.
reserved. 55
1 - 55
Security Aware Cloud Platform

56
Cloud Service Models & Security Measures

57