EE 660: Computer Architecture Cloud Architecture: Virtualization

Size: px

Start display at page:

Download "EE 660: Computer Architecture Cloud Architecture: Virtualization"

Blaze Osborne
5 years ago
Views:

1 EE 660: Computer Architecture Cloud Architecture: Virtualization Yao Zheng Department of Electrical Engineering University of Hawaiʻi at Mānoa Based on the slides of Prof. Roy Campbell & Prof Reza Farivar

2 Agenda Introduction to Virtualization Implementations of Virtualization OS based Virtualization: Xen Containers: Dockers

3 Sharing Resources Economics of Clouds requires sharing resources How do we share a physical computer among multiple users? Answer: Abstraction Introduce an abstract model of what a generic computing resource should look like The physical computer resource then provides this abstract model to many users

4 Layers of Abstraction Introduce an abstract model of what a generic computing resource should look like The physical computer resource then provides this abstract model to many users Virtualization avoids creating dependencies on physical resources

5 Layers of Abstraction Introduce an abstract model of what a generic computing resource should look like The physical computer resource then provides this abstract model to many users Virtualization avoids creating dependencies on physical resources

6 Virtualization: Foundation of Cloud Computing Virtualization allows distributed computing models without creating dependencies on physical resources Clouds are based on Virtualization offer services based mainly on virtual machines, remote procedure calls, and client/servers provide lots of servers to lots of clients (e.g. phones) Simplicity of use and ease of programming requires allowing client server paradigms to be used to construct services from lots of resources

7 Types of virtualization Native, full Hardware assisted Para-virtualization OS level Containers Jails Chroot Zones Open-VZ à Virtuozzo

8 Background The Virtual Machine concept isn t new IBM mainframes implemented it in 1960s Features of Classical Virtualization : FIDELITY: software s execution on the virtual machine is identical -- except for timing -- to its execution on actual hardware PERFORMANCE: the vast majority of a guest s instructions are executed without any intervention SAFETY: all hardware resources are controlled by the Virtual Machine Manager

9 Native and Full Virtualization the virtual machine simulates enough hardware to allow an unmodified "guest" OS (one designed for the same CPU) to be run in isolation. Examples: VirtualBox Virtual PC Vmware QEMU Apps Guest OS Apps Guest OS.. Space reserved Manag for video Do not put anything ement here Hypervisor (VMM) Hardware

Intel VT (IVT) AMD virtualization (AMD-V) Examples: VMware Fusion Parallels

10 Hardware enabled virtualization the virtual machine has its own hardware and allows a guest OS to be run in isolation. Intel VT (IVT) AMD virtualization (AMD-V) Examples: VMware Fusion Parallels Desktop for Mac Parallels Workstation Apps Apps Apps Guest Guest Guest.. OS OS OS Hardware VM Hardware VM Hardware

Paravirtualization the virtual machine does not necessarily simulate hardware, but instead (or in addition) offers a special API that can only be used by modifying the

11 Paravirtualization the virtual machine does not necessarily simulate hardware, but instead (or in addition) offers a special API that can only be used by modifying the "guest" OS. Examples: XEN Apps Apps Modified Guest OS Stub Modified Guest OS Stub.. Space reserved Manag for video Do not put anything ement here Hypervisor (VMM) Hardware

12 Operating system-level virtualization virtualizing a physical server at the operating system level, enabling multiple isolated and secure virtualized servers to run on a single physical server. Examples: Linux-Vserver Solaris Containers FreeBSD Jails Chroot CGroups Private Server Private Server.. Private Server Operating Do System not put anything here Hardware

13 The Software-defined Network 3. Well-defined open API App App App 2. At least one good operating system that is extensible and possibly open source Network Operating System 1. Open interface to hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

N2e2twork OS Virtualization Layer x86 (Computer) Virtualization or Slicing OpenFlow Computer Industry Network Industry

14 Trend Virtualized OS + Virtualized Network App App App App App App Windows Mac W W (O (O in d S ) o w s L in in u x M a Linux O (OS) a c S S c OS NCO C ox o n n tr t o rol e le r r 1 1 (Network OS) C C o o n n tr t o ro l l e le r r N2e2twork OS Virtualization Layer x86 (Computer) Virtualization or Slicing OpenFlow Computer Industry Network Industry Simple common stable hardware substrate below + programmability + strong isolation model + competition above = faster innovation

Linu Lxinxux x86 (Computer) App Mac M O a a c

Industry App C C o o n n t t r r o ol NOX (Ne

Network Industry App CCoonnttrroollele Nr

15 Trend Then Add Virtualized Storage App WWininddoo Wwiwnsdsows (O(SO(O)SS)) App Linu Linu Lxinxux x86 (Computer) App Mac M O a a c S S c OS Virtualization Layer Computer Industry App C C o o n n t t r r o ol NOX (Ne e er r tw1 1 ork OS) App Slicing OpenFlow Network Industry App CCoonnttrroollele Nr retwork O2 2S App C C o o n n tr t o ro l l e le r r 1 1 HDFS App Virtualization App Controller Controller H2B2ase Distributed FS Storage Area Network Storage Industry

16 Agenda Introduction to Virtualization Implementations of Virtualization OS based Virtualization: Xen Containers: Dockers

17 Types of Virtualization Native, full Hardware assisted Para-virtualization OS level Containers Jails Chroot Zones Open-VZ à Virtuozzo

18 Native and Full Virtualization The virtual machine simulates enough hardware to allow an unmodified "guest" OS (one designed for the same CPU) to be run in isolation. Examples: VirtualBox Virtual PC Vmware QEMU Win4Lin XEN/Virtual Iron

19 x86 poses some problems Certain x86 instructions were impossible to truly virtualize in that classical sense For example, the smsw instruction can be executed at any privilegelevel, and in any processor mode, revealing to software the current hardware status (e.g., PE, PG, ET) Intel s Vanderpool Project endeavored to remedy this (using new processor modes)

20 VT-x Virtualization Technology for x86 CPUs Two new processor execution-modes VMX root mode (for VM Managers) VMX non-root mode (for VM Guests) Ten new hardware instructions A six-part VMCS data-structure A variety of control-options for VMs

21 Interaction of VMs and VMM VM #1 (Guest) VM #2 (Guest) VM Exit VM Exit VM Entry VM Entry VMXON VM Monitor (Host) VMXOFF

22 Hardware Enabled Virtualization The virtual machine has its own hardware and allows a guest OS to be run in isolation. Intel VT (IVT) AMD virtualization (AMD-V) Examples: VMware Fusion Parallels Desktop for Mac Parallels Workstation

23 Partial Virtualization The virtual machine simulates multiple instances of much (but not all) of an underlying hardware environment, particularly address spaces.

24 Paravirtualization The virtual machine does not necessarily simulate hardware, but instead (or in addition) offers a special API that can only be used by modifying the "guest" OS. Terminologies Hypervisor, hypercall Enomalism Examples: XEN, KVM, Win4Lin 9x

Operating System-Level Virtualization Virtualizing a physical server at the operating system level, enabling multiple isolated and secure virtualized

25 Operating System-Level Virtualization Virtualizing a physical server at the operating system level, enabling multiple isolated and secure virtualized servers to run on a single physical server. Examples: Parallels Workstation Linux-VServer, Virtuozzo OpenVZ, Solaris Containers FreeBSD Jails Chroot?

26 Operating System-Level Virtualization Hypervisor (VM) One real HW, many virtual HWs, many Oss High versatility can run different Oss Lower density, performance, scalability <<Lowers>> are mitigated by new hardware features (such as VT-D) Containers (CT) One real HW (no virtual HW), one kernel, many userspace instances Higher density, natural page sharing Dynamic resource allocation Native performance: [almost] no overhead

27 Thinner Containers, Better Performance Containers Share host OS and drivers Have small virtualization layer Naturally share pages Hypervisors Have separate OS plus virtual hardware Hardware emulation requires VMM state Have trouble sharing guest OS pages Containers are more elastic than hypervisors Container slicing of the OS is ideally suited to cloud slicing families on one server Hypervisors only advantage in IaaS is support for different OS

28 What Is the Trade-Off? 10

29 Feature Comparison Hypervisor Container Multiple Kernels X Load Arbitrary Modules Space X reserved for video Local Administration All Live Migration OpenVZ Live System Update X Zap 11

30 Agenda Introduction to Virtualization Implementations of Virtualization OS based Virtualization: Xen Containers: Dockers

31 Xen 3.0 Guest VM

32 Xen 3.0 Guest VM Driver Domain Map Virtual Devices CFQ for disk HTB for network

33 Xen 3.0 Guest VM I/O Path Process to Guest OS Guest OS to IDD

34 Xen 3.0 Guest VM Security Isolation Hypervisor Access Physical Level PCI Address Virtual Memory

35 Xen 3.0 Guest VM Security Isolation Hypervisor Access Physical Level PCI Address Virtual Memory Resource Control Hypervisor Allocate Resources Schedule VMs

36 Agenda Introduction to Virtualization Implementations of Virtualization OS based Virtualization: Xen Containers: Dockers

37 Overview Docker containers wrap up a piece of software in a complete filesystem that contains everything needed to run: code, runtime, system tools, system libraries anything you can install on a server. This guarantees that the software will always run the same, regardless of its environment it is running in. (Docker Inc., n.d.)

38 Overview Docker automates the deployment of applications inside software containers Additional layer of abstraction and automation of operating system level virtualization on Linux.

39 History of Docker Solomon Hykes started Docker in France as an internal project within dotcloud, a platform-as-a-service company Docker was released as open source in 13 March 2013 libcontainer library written in the Go programming language. Latest version (31 May 2016) Docker team, Red Hat, IBM, Google, Cisco Systems and Amadeus IT Group.

40 Docker Structure

41 Containers built with Docker

42 Basics of Docker C o n t a i n e r A Push Docker Container Image Registry Component A s Docker File Source Code Repository Build Docker Engine Developer Linux Host C o n t a i n e r A C o n t a i n e r B C o n t a i n e r C Destination Linux Host D o c k e r search Pull Run

43 Changes and Updates App A Bins + Libs Original Container A p p Diffs packaged in Update Container A p p Docker Container Image Registry App A Update copies of container App A Get Update Bins + Libs Bins + Libs Docker Engine Docker Engine

Module 1: Virtualization. Types of Interfaces

Module 1: Virtualization. Types of Interfaces Module 1: Virtualization Virtualization: extend or replace an existing interface to mimic the behavior of another system. Introduced in 1970s: run legacy software on newer mainframe hardware Handle platform