1. Virtualization 101 Presented by Gaurav Marwaha

2. History The prototypical illustration of full virtualization is in the control program of IBM's CP/CMS operating system – first demonstrated with IBM's CP-40 research system in 1967, then distributed via open source in CP/CMS in 1967-1972, and re-implemented in IBM's VM family from 1972 to the present. Each CP/CMS user was provided a simulated, stand-alone computer. Each such virtual machine had the complete capabilities of the underlying machine, and (for its user) the virtual machine was indistinguishable from a private system. This simulation was comprehensive, and was based on the Principles of Operation manual for the hardware. It thus included such elements as instruction set, main memory, interrupts, exceptions, and device access. The result was a single machine that could be multiplexed among many users.

6. Software Virtualization runs the virtualized operating system on top of a software virtualization platform running on an existing operating system.

7. Hardware Virtualization runs the virtualized operating system on top of a software platform running directly on top of the hardware without an existing operating system. The engine used to run hardware virtualization referred to as a hypervisor.

9. Mobility – can be moved from one host to another quickly

10. Can templatize OS creation or use custom OS

11. Easy to backup – just copy the file

13. Easy management; patch application and virus protection

14. Huge energy savings

15. Better security and problem isolation

17. Instead of capturing the installation process you capture what an application needs to run in an OS

18. Huge energy savings

19. Better security and problem isolation

21. More the better

22. Move to 64bit

23. Can look at Physical Address Extension switch at startup

24. Storage

25. Rely on shared storage

26. Licensing

27. OS licensing – windows has a separate policy for virtual servers

28. Its hypervisor is called ESX

29. Architectures

30. It is important to have a visual diagram else it may become confusing

31. Management

32. Focus on VM management

33. Dependency management

36. Offers a product named xenserver for server virtualization and xendesktop for desktop virtualization

37. Xenserver has four editions ranging from free Express to Platinum edition

38. Microsoft - www.microsoft.com/virtualization

39. Virtual Server and Virtual PC are two products

40. It has a built in hypervisor (Hyper-V) which is part of Windows 2008 server OS

41. VMWare – www.vmware.com

42. Offers very mature server and desktop products

43. Its hypervisor is called ESXOracle (Oracle VM), Novell (Xen), Red Hat (Xen), IBM, Sun (xVM), Virtual Iron, and others also all offer their own hypervisors

44. Software Appliances A software appliance is a software application combined with just enough operating system (JeOS) for it to run optimally on industry standard hardware (typically a server) or in a virtual machine. JeOS is the abbreviation (pronounced "juice") for the concept of Just Enough Operating System as it applies to a software appliance. JeOS is not a generic, one-size-fits-all operating system. Rather, it refers to a customized operating system that precisely fits the needs of a particular application. The application's OS requirements can be determined manually, or with an analytical tool. Therefore, JeOS includes only the pieces of an operating system (often Linux) required to support a particular application and any other third-party components contained in the appliance. This makes the appliance smaller, and possibly more secure than an application running under a full general purpose OS.

45. FIREWALL Virtual Appliance CRM Virtual Appliance Linux Linux What is a Virtual Appliance Firewall SW Pre-built, pre-configured and ready-to-run software application packaged with the OS inside a Virtual Machine. Or packaged inside multiple Virtual Machines Linux Apache mySQL Tomcat Linux

46. Virtual Appliances Virtual appliances are virtual machine templates, sometimes in the Open Virtualization Format (OVF), that contain preconfigured operating systems and applications. Since VMs are self-contained and transportable, they can be delivered in a preconfigured state as virtual appliances. VAPs are most often designed to run on Linux operating systems because of the licensing cost. Few vendors have created VAPs based on Microsoft technologies because they have to become Windows resellers to do so. Some considerations that need addressable when we choose a VAP: Has the OS been hardened? Is the appliance upgradeable? Scalability Microsoft v/s Linux Licensing Custom OS?

47. Application Virtualization

48. Application Virtualization

50. Applications can be deployed in streaming mode to reduce network usage and hard disk requirements

53. Reliability and scalability logic remain hidden giving the illusion of infinite (elastic) capacity.

54. These services are programmatically controlled on-demand

55. Charges are consumption based – no upfront investment

56. Loosely coupled set of services19