1 / 22

VMFlock: VM Co-Migration Appliance for the Cloud

VMFlock: VM Co-Migration Appliance for the Cloud. Samer Al-Kiswany With: Dinesh Subhraveti Prasenjit Sarkar Matei Ripeanu. Why VM Migration across Data Centers ?. For Cloud Users: Freedom, Not locked to one cloud. Private and public clouds. For the Cloud provider:

sian
Download Presentation

VMFlock: VM Co-Migration Appliance for the Cloud

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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. • Properties: • High performance • Scalable • Load balanced • Easy to adopt • VMFlockMS achieves (compared to alternatives): • Up to 10x better compression rate • Up to 3.5x faster migration time

  6. Outline • Introduction • VMFlockMS Design • Migration Appliance Design • VM Bootstrap component Design • Evaluation • Conclusion

  7. VMFlockMS Design • Migration components • Similarities across VM flock images • Similarities across VM repositories • Bootstrap components • VM boot pattern Source Destination Migration nodes Migration nodes VM VM VMProfiler VMLaunchPad VM Repository VM Repository

  8. Migration Components Design • Similarities across VM flock images • Similarities across VM repositories • Deduplication challenges: • CPU and IO intensive workload • Metadata size Source Destination Migration nodes Migration nodes VM Repository VM Repository

  9. Migration Components Design Source Destination VM Repository

  10. Migration Components Design Source Destination VM Repository

  11. Migration Components Design Source Destination VM Repository

  12. Migration Components Design Source Destination VM Repository VM Repository

  13. VM VM VMProfiler VMLaunchPad Bootstrap Components Design Source Destination Migration nodes Migration nodes VM Repository VM Repository

  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 Single VM image at destination Achieves up to 10x better compression rate.

  18. Evaluation – Migration Time Migration time for the application flock VMFlockMS achieves up to 2x better migration time.

  19. Evaluation – Migration Time Migration time for the application flock using the VM repository emulator (emulating 4 SAS disks) VMFlockMS achieves up to 3.5x better migration time.

  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

More Related