1 / 54

UNIT-2 Virtualization for Datacenter Automation to serve millions of clients, simultaneously

Department of computer science and Engineering cloud computing prepared by G.vijaya kumar Asst.professor. UNIT-2 Virtualization for Datacenter Automation to serve millions of clients, simultaneously. Server Consolidation in Virtualized Datacenter

laveran
Download Presentation

UNIT-2 Virtualization for Datacenter Automation to serve millions of clients, simultaneously

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. Department of computer science and Engineeringcloud computingprepared byG.vijayakumarAsst.professor

  2. UNIT-2 Virtualization for Datacenter Automationto serve millions of clients, simultaneously • Server Consolidation in Virtualized Datacenter • Virtual Storage Provisioning and Deprovisioning • Cloud Operating Systems for Virtual Datacenters • Trust Management in virtualized Datacenters

  3. Difference between Traditional Computer and Virtual machines (Courtesy of VMWare, 2008)

  4. Virtual Machine, Guest Operating System,and VMM (Virtual Machine Monitor): The Virtualization layer is the middleware between the underlying hardware and virtual machines represented in the system, also known as virtual machine monitor (VMM) or hypervisor.

  5. (Courtesy of VMWare, 2008)

  6. Virtualization Ranging from Hardware to Applications in Five Abstraction Levels

  7. Virtualization at ISA (Instruction Set Architecture) level: • Emulating a given ISA by the ISA of the host machine. • e.g, MIPS binary code can run on an x-86-based host machine with the help of ISA emulation. • Typical systems: Bochs, Crusoe, Quemu, BIRD, Dynamo • Advantage: • It can run a large amount of legacy binary codes written for various processors on any given new hardware host machines • best application flexibility • Shortcoming & limitation: • One source instruction may require tens or hundreds of native target instructions to perform its function, which is relatively slow. • V-ISA requires adding a processor-specific software translation layer in the complier.

  8. Virtualization at Hardware Abstraction level:Virtualization is performed right on top of the hardware. • It generates virtual hardware environments for VMs, and manages the underlying hardware through virtualization. • Typical systems: VMware, Virtual PC, Denali, Xen • Advantage: • Has higher performance and good application isolation • Shortcoming & limitation: • Very expensive to implement (complexity)

  9. Virtualization at Operating System (OS) level: • It is an abstraction layer between traditional OS and user placations. • This virtualization creates isolated containers on a single physical server and the OS-instance to utilize the hardware and software in datacenters. • Typical systems: Jail / Virtual Environment / Ensim's VPS / FVM • Advantage: • Has minimal starup/shutdown cost, low resource requirement, and high scalability; synchronize VM and host state changes. • Shortcoming & limitation: • All VMs at the operating system level must have the same kind of guest OS • Poor application flexibility and isolation.

  10. Virtualization at OS Level

  11. Virtualization for Linux and Windows NT Platforms

  12. Advantages of OS Extension for Virtualization • VMs at OS level has minimum startup/shutdown costs • OS-level VM can easily synchronize with its environment • Disadvantage of OS Extension for Virtualization All VMs in the same OS container must have the same or similar guest OS, which restrict application flexibility of different VMs on the same physical machine.

  13. Library Support level: • It creates execution environments for running alien programs on a platform rather than creating VM to run the entire operating system. • It is done by API call interception and remapping. • Typical systems: Wine, WAB, LxRun , VisualMainWin • Advantage: • It has very low implementation effort • Shortcoming & limitation: • poor application flexibility and isolation

  14. Virtualization with Middleware/Library Support

  15. The vCUBE for Virtualization of GPGPU

  16. User-Application level: • Itvirtualizes an application as a virtual machine. • This layer sits as an application program on top of an operating system and exports an abstraction of a VM that can run programs written and compiled to a particular abstract machine definition. • Typical systems: JVM , NET CLI , Panot • Advantage: • has the best application isolation • Shortcoming & limitation: • low performance, low application flexibility and high implementation complexity.

  17. More Xs mean higher merit

  18. Hypervisor • A hypervisor is a hardware virtualization technique allowing multiple operating systems, called guests to run on a host machine. This is also called the Virtual Machine Monitor (VMM). • Type 1: bare metal hypervisor • sits on the bare metal computer hardware like the CPU, memory, etc. • All guest operating systems are a layer above the hypervisor. • The original CP/CMS hypervisor developed by IBM was of this kind. • Type 2: hosted hypervisor • Run over a host operating system. • Hypervisor is the second layer over the hardware. • Guest operating systems run a layer over the hypervisor. • The OS is usually unaware of the virtualization

  19. Major VMM and Hypervisor Providers

  20. The XEN Architecture (1)

  21. The XEN Architecture (2)

  22. The XEN Architecture (3)

  23. Full Virtualization vs. Para-Virtualization • Full virtualization • Does not need to modify guest OS, and critical instructions are emulated by software through the use of binary translation. • VMware Workstation applies full virtualization, which uses binary translation to automatically modify x86 software on-the-fly to replace critical instructions. • Advantage: no need to modify OS. • Disadvantage: binary translation slows down the performance. • Para virtualization • Reduces the overhead, but cost of maintaining a paravirtualized OS is high. • The improvement depends on the workload. • Para virtualization must modify guest OS, non-virtualizable instructions are replaced by hypercalls that communicate directly with the hypervisor or VMM. • Para virtualization is supported by Xen, Denali and VMware ESX.

  24. Full Virtualization

  25. Binary Translation of Guest OS Requests using a VMM:

  26. Para- Virtualization with Compiler Support. The KVM builds offers kernel-based VM on the Linuxplatform, based on para-virtualization

  27. VMWare ESX Server for Para-Virtualization

  28. Conclusions on CPU, Memory and I/O Virtualization : • CPU virtualization demands hardware-assisted traps of sensitive instructions by the VMM • Memory virtualization demands special hardware support (shadow page tables by VMWare or extended page table by Intel) to help translate virtual address into physical address and machine memory in two stages. • I/O virtualization is the most difficult one to realize due to the complexity if I/O service routines and the emulation needed between the guest OS and host OS.

  29. Multi-Core Virtualization: VCPU vs. traditional CPU Figure 3.16 Four VCPUs are exposed to the software, only three cores are actually present. VCPUs V0, V1, and V3 have been transparently migrated, while VCPU V2 has been transparently suspended. (Courtesy of Wells, et al., “Dynamic Heterogeneity and the Need for Multicore Virtualization”, ACM SIGOPS Operating Systems Review, ACM Press, 2009 [68] )

  30. Virtual Cores vs. Physical Processor Cores

  31. (Courtesy of Marty and Hill, 2007)

  32. Virtual Clusters in Many CoresSpace Sharing of VMs -- Virtual Hierarchy (Courtesy of Marty and Hill, 2007)

  33. Virtual Cluster Characteristics • The virtual cluster nodes can be either physical or virtual machines. Multiple VMs running with different OSs can be deployed on the same physical node. • A VM runs with a guest OS, which is often different from the host OS, that manages the resources in the physical machine, where the VM is implemented. • The purpose of using VMs is to consolidate multiple functionalities on the same server. This will greatly enhance the server utilization and application flexibility. • VMs can be colonized (replicated) in multiple servers for the purpose of promoting distributed parallelism, fault tolerance, and disaster recovery. • The size (number of nodes) of a virtual cluster can grow or shrink dynamically, similarly to the way an overlay network varies in size in a P2P network. • The failure of any physical nodes may disable some VMs installed on the failing nodes. But the failure of VMs will not pull down the host system.

  34. Virtual Clusters vs. Physical Clusters

  35. Live Migration of Virtual Machines

  36. Virtual Cluster Projects

  37. Cluster-on-Demand (COD Project) at Duke University

  38. VIOLIN Project at Purdue University

  39. Parallax for VM Storage Management

  40. Cloud OS for Building Private Clouds

More Related