1 / 26

Automatic software deployment using user-level virtualization for cloud-computing

Automatic software deployment using user-level virtualization for cloud-computing. Future Generation Computer System (2013) Youhui Zhang, Yanhua Li, Weimin Zheng. Outline. Introduction The framework Performance test Conclusion. Introduction (1).

gino
Télécharger la présentation

Automatic software deployment using user-level virtualization for cloud-computing

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. Automatic software deployment using user-level virtualization for cloud-computing Future Generation Computer System (2013) Youhui Zhang, Yanhua Li, Weimin Zheng

  2. Outline • Introduction • The framework • Performance test • Conclusion

  3. Introduction (1) • Infrastructure cloud service providers deliver virtual hardware and system software in their datacenters, based on the demand from customers • It is necessary to deploy application software in similar way

  4. Virtual Appliances (VAs) • It is a pre-built software • VA-based method can reduce time and expenses

  5. VA drawbacks • Lack of flexibility • Inefficiency of storage

  6. Lack of flexibility • Customer needs software Aand B to work together in a virtual machine, but the provideronly has two separate VAs containing A and B respectively • The provider has to create a new VM template to combine A and Btogether

  7. Inefficiency of storage • OS has to be combined. Therefore, the storage overhead

  8. Introduction (2) • This paper introduces mechanisms to isolate application software from OS • Application software can be deployed in a fine granularity to increase the flexibility and decrease the storage overhead • We call such application software as on-demand software

  9. Function1 - Software preparation • Cover software into the on-demand mode • On-demand software is stored in the software depository for users’ selection

  10. Preparation of on-demand software • software can be regarded as containing three parts: • Part1 includes all resources provided by the OS • Part2 contains what are created/ modified/ deleted by the installation process • Part3 is the data created/modified/deleted during the run time

  11. Preparation of on-demand software(cont’ d)

  12. Preparation of on-demand software(cont’ d) • Snapshot is taken to build the on-demand software

  13. Function2 - Software selection • A customer can choose the wanted OS, as well as any number of software in separated stages

  14. Function3 - On-demand deployment • When the customer actually uses the chosen software, will it be streamed from the data server and run locally without installation.

  15. The runtime environment of on-demand software (cont’ d) • The resource modified will be moved into Part 3

  16. The runtime environment of on-demand software • Construct a runtime environment where software can locate and access any necessary resources • Runtime environment redirects all accesses for Parts 2 and 3 to the actual storage positions and guides other visits (for Part 1) to the local OS

  17. User-level file system • On-demand software is stored in the central depository and presented as files/ folders on a virtual local drive in the customer’s VM

  18. Function4 - Software customization • The VA-based solution, it is difficult to implement this function efficiently

  19. On-demand software VS Virtual appliance(VA)

  20. System overview

  21. Optimizations • Content-addressable storage • Data cache

  22. Content-addressable storage • On-demandsoftware is partitioned into shards • Compute the hash valueof every shard, and the same values mean the corresponding shardsare identical.

  23. Data cache • The replace strategy is based on the usagefrequency

  24. Comparisons of start-up time.

  25. Comparisons of running time

  26. Conclusion • This paper provides a framework to decouple application software from VM images to improve the deployment flexibility for cloud computing • Compared with VA-based solutions, it also improves the storage efficiency • Users’ customization can been separated inherently and efficiently for reuse

More Related