Cloud Computing for Beginners

Infrastructure as a Service (IaaS)

By Idan Gabrieli
 Cloud Computing
Virtualization Technologies
UNDER-UTILIZED PHYSICAL SERVERS
Physical Bare-metal Rack Server

Rack Server like a “Pizza Box”

CPU Mem. Storage NICs

Application

Operating System (e.g. Linux)

Physical Server
UNDER-UTILIZED PHYSICAL SERVERS
One App in One Server?

CPU – 15%, Memory – 10% Application (e.g. Email Server)

Operating System (e.g. Linux)

Physical Server

Under-utilized Server 
UNDER-UTILIZED PHYSICAL SERVERS
More than one apps in one server?
Email Server App. File Sharing Server App.

App1 App2

Operating System (e.g. Linux)

Physical Server

Mixing Server-side app is not recommended

Server-side app is optimized to work with a specific OS
Server-side app will require specific computing power and memory capacity
Sharing maintenance down-time
UNDER-UTILIZED PHYSICAL SERVERS
Back to the same problem - Two Apps using Two Servers

Email Service - Server File Sharing Service - Server

App1 App2

OS1 OS2

Physical Server Physical Server

UNDER-UTILIZED PHYSICAL SERVERS
Magnitude is Growing in a Data Center

10% CPU 5% CPU 15% CPU

Email File Sharing Web Server

A HUGE waste of IT resources

Virtualization Technologies
let’s make it virtual
VIRTUALIZATION WITH VIRTUAL MACHINES

Virtual Resource Virtual Resource Virtual Resource

Physical Hardware Servers

VIRTUALIZATION WITH VIRTUAL MACHINES

VM1 VM2 VM3

Hypervisor
Host Server
Physical Servers

….
VIRTUALIZATION WITH VIRTUAL MACHINES
Dynamically allocate/deallocate VMs

VM Profile – CPU, Memory, Storage, Network Interfaces

VM1 VM2 VM3

Hypervisor

Physical Servers
VIRTUALIZATION WITH VIRTUAL MACHINES
Each VM is an isolated environment

Isolated VM1 VM2 VM3

Environment

Guest Guest OS Guest OS Guest OS

Machines
Hypervisor

Physical Servers
VIRTUALIZATION WITH VIRTUAL MACHINES
Apps in Each VM

VM1 VM2 VM3

App-1 App-2 App-3 App-4

Guest OS Guest OS Guest OS

Hypervisor

Physical Servers
VIRTUALIZATION WITH VIRTUAL MACHINES
Back to Our Example

VM1 VM2 VM3

Email S. File Sharing Web Server

Win OS Linux OS Linux OS

Hypervisor

Physical Servers
VIRTUALIZATION WITH VIRTUAL MACHINES
VM Image

Virtual Machine

Install and Configure Application Take a “Snapshoot”

Install and Configure Bin/Libs VM Image (“template”)
Install and Configure Guest OS

VM VM VM

Instances created from the Image

VERTICAL AND HORIZONTAL SCALING
The concept of scaling

Scaling is the process of managing our

cloud resources' capacity to help our application
meet a set of performance requirements
VERTICAL AND HORIZONTAL SCALING
The concept of scaling We need X, Y, Z Now!

Allocate
Resources

Trigger Monitor
Let’s change the capacity! What’s going on?
Scaling Performance

Detect
Over/Under
Utilization

Not enough resources?

Too much resources?
VERTICAL AND HORIZONTAL SCALING

Vertical Scaling (up/down) Horizontal Scaling (out/in)

VM #01
VM #01 VM #01 VM #02

2 x vCPU 4 x vCPU 2 x vCPU 2 x vCPU

1 x GB RAM 2 x GB RAM 1 x GB RAM 1 x GB RAM
MICROSERVICES AND CLOUD-NATIVE APPS

No software change is
needed

Legacy VM1 VM2 VM3

Applications App-1 App-3 App-4
App-2

Guest OS Guest OS Guest OS

Hypervisor

Physical Servers
MICROSERVICES AND CLOUD-NATIVE APPS
Re-design Applications

Cloud-Native Apps

A new software architecture

Microservices
MICROSERVICES AND CLOUD-NATIVE APPS
What are Micro-services?

• Software development architecture

Monolithic
• Design, develop and maintain cloud-native
Application
applications
• Small pieces called micro-services
• A micro-service
• Single function module
• Do one thing and do it well!
• Each micro-service is like a mini-application
• Developed independently and deployed
independently
MICROSERVICES AND CLOUD-NATIVE APPS

50 X Micro-Services

? Virtual Machine

Application
50 X VMs (with 50 x OS…) Bin/Libs

Guest OS
TRADITIONAL VIRTUALIZATION WITH VMs

Virtual Machine Virtual Machine Virtual Machine

Microservice X Microservice Y Microservice Z

Bin/Libs Bin/Libs Bin/Libs

Guest OS Guest OS Guest OS

A HUGE OS Overhead :-(

TRADITIONAL VIRTUALIZATION WITH VMs

Virtual Machine

MS-X MS-Y MS-Z

Bin/Libs

Guest OS
Microservices in VMs ?

Microservices Architecture
Virtual Machine

X Microservice X

Bin/Libs
Y
Guest OS
Virtual Machine

Microservice Y

Bin/Libs

Guest OS
VIRTUALIZATION WITH CONTAINERS
VIRTUALIZATION WITH CONTAINERS

VM1 VM2 VM3

App-1 App-2 App-3 App-4

Guest OS Guest OS Guest OS

Hypervisor

Physical Servers
VIRTUALIZATION WITH CONTAINERS

Host Operating System

Physical Servers
VIRTUALIZATION WITH CONTAINERS
Microservices in containers X

Y
Container Container Container

Z
MS-X MS-Y MS-Z

Container Engine

Host Operating System

Physical Servers
Containerized Application
VIRTUALIZATION WITH CONTAINERS
VMs vs. Containers

VM1 VM2 VM3 Container Container Container

App-1 App-2 App-3 App-4 MS-1 MS-2 MS-3

Guest OS Guest OS Guest OS

Container Runtime Engine

Hypervisor Host Operating System

Physical Servers Physical Servers

THE BENEFITS OF CONTAINERS

Rapid Scalability

Deployment in seconds….
+ -
Deployed in multiple environments + + - -
+ + + - - -
Streamline Faster Software Releases
VIRTUALIZATION WITH CONTAINERS

Low OS
Overheard

Cloud-native Standardized
Applications packing on
Containers software

Virtualization Complex to
Approach Manage
(vs. VMs)
VIRTUALIZATION WITH CONTAINERS

Containers
MIGRATE TO IT BUILD ON IT

IaaS PaaS
Infrastructure as a Service Platform as a Service