Embed Size (px)
Citation preview
VMFlock: VM Co-Migration Appliance for the Cloud
Samer Al-Kiswany
With: Dinesh Subhraveti Prasenjit Sarkar Matei Ripeanu
2
Why VM Migration across Data Centers ?
For Cloud Users:• Freedom, Not locked to one cloud.
• Private and public clouds.
For the Cloud provider:• Load balancing across data centers• Accommodate scheduled maintenance• Arbitration of energy cost
Requires: Efficient migration and fast instantiation of VM still images across data centers.
3
Challenges
• Applications often deployed on multiple VMs (VM Flock)
• Large VM image size (GBs)
• Limited WAN bandwidth
• Strict Cloud API
• Limited resources
(compute, memory, IO)
4
Opportunities
• Similarities across VM flock images
• Similarities across VM repositories
• VM boot time access pattern
5
VMFlock Migration System
An appliance for migrating and bootstrapping multiple VM images across data centers.
VMFlockMS achieves (compared to alternatives):• Up to 10x better compression rate• Up to 3.5x faster migration time
Properties:• High performance• Scalable• Load balanced• Easy to adopt
6
Outline
• Introduction
• VMFlockMS Design
Migration Appliance Design
VM Bootstrap component Design
• Evaluation
• Conclusion
7
VMFlockMS Design
Migrationnodes
VM Repository
VM Repository
Source Destination
VM
VMLaunchPad
Migrationnodes
VM
VMProfiler
• Migration components
Similarities across VM flock images
Similarities across VM repositories
• Bootstrap components
VM boot pattern
8
Migrationnodes
VM Repository
VM Repository
Source Destination
Migrationnodes
Similarities across VM flock images
Similarities across VM repositories
Migration Components Design
Deduplication challenges:• CPU and IO intensive workload• Metadata size
9
Migration Components Design
VM Repository
Source
Destination
10
Migration Components Design
VM Repository
Source
Destination
11
Migration Components Design
VM Repository
Source
Destination
12
Migration Components Design
VM Repository
Source Destination
VM Repository
13
Bootstrap Components Design
Migrationnodes
VM Repository
VM Repository
Source Destination
VM
VMLaunchPad
Migrationnodes
VM
VMProfiler
14
Outline
• Introduction
• VMFlockMS Design
Migration Appliance Design
VM Bootstrap component Design
• Evaluation
• Conclusion
15
Evaluation – Setup
Images • Application: Spree e-commerce (spree, sql, storage node)
– 7.9 GB• Same-OS (Fedora: desktop, developer, server, plain) –
10.6 GB• Diff-OS (Fedora, openSUSE, Ubuntu) – 10.6 GB
Alternatives • Gzip-All • Gzip-Separate (parallel Gzip)• Dedup-separate [Hirofuchi 09, Bradford 07, Sapuntzakis 02]
16
Evaluation – Setup
Testbed • 2 machines at Almaden and 2 at T.J. Watson• 1 machine at each side works as a VM repository
Courtesy Google Maps
17
Evaluation – Compression Rate
No VM images at destination
0
5
10
15
20
25
30
35
40
45
Gzip All GzipSeparate
DedupSeparate
VMFlockMS
Co
mp
res
sio
n r
ate
(%
)
Diff-OSSame-OSApp
0
5
10
15
20
25
30
35
40
Gzip All GzipSeparate
DedupSeparate
VMFlockMS
Co
mp
res
sio
n r
ate
(%
)
Diff-OSSame-OSApp
Single VM image at destination
Achieves up to 10x better compression rate.
18
Evaluation – Migration Time
VMFlockMS achieves up to 2x better migration time.
0
20
40
60
80
100
120
Gzip All GzipSeparate
DedupSeparate
VMFlockMS1KB
VMFlockMS8KB
VMFlockMS128KB
Mig
ratio
n ti
me
(min
)
Migration time for the application flock
19
Evaluation – Migration Time
VMFlockMS achieves up to 3.5x better migration time.
Migration time for the application flock using the VM repository emulator (emulating 4 SAS disks)
0
5
10
15
20
25
30
35
40
45
Gzip All GzipSeparate
DedupSeparate
VMFlockMS
Mig
rati
on
tim
e (
min
)
20
Evaluation – Boot Time
• VM Flock needs less then 20MB to boot.• Most of the data already at destination• VM flock boot in less than 1 min• VMFlockMS overhead less than 3%
21
Summary
VMFlockMS: An appliance for migrating and bootstrapping multiple VM images across data centers.
Properties:• High performance• Scalable• Load balanced• Easy to adopt
Where else:• Scientific data sets migration• Long execution pipelines
22
Thank you
