3. Agenda:
PART I
1. What is and for what we need virtualization?
2. Typesof virtualization:
1. Virtualization of (1) OS and (2) App
2. Two types of hypervisor
3. Containers
3. Virtualization tools:
1. T1.VMware VSphere ESXi
2. T1.Hyper-V
3. T2.VMware Workstation / Virtualbox
4. E.Docker
5. E.XenApp
4. Q&A
PART II
1. What HAmeans?
2. How to reach HA:
1. Data Backups, Recovery and Replication
2. Network Load Balancing (NLB)
3. Scalable Architecture (Azure example)
4. Failover Cluster
5. Geographically Distributed Disaster Recovery
3. Q&A
5. 1.Whatisandforwhatweneedvirtualization?
Virtualizationrefers to the creation of avirtual resource such as a server, desktop, operating system, file,
storage or network
• Toencapsulate and isolate test environment from other apps/distractors
• Toeasy test solutions on many different systems
• ...
7. 2.2.Twotypesofhypervisor:
• Type-1/native/bare-metalhypervisors
• These hypervisors rundirectlyonthehost'shardwaretocontrolthe
hardwareandtomanageguestoperatingsystems.Examples:
• Xen,
• Oracle VM Server for SPARC/x86,
• Microsoft Hyper-V,
• VMware ESX/ESXi.
• Type-2/ hostedhypervisors
• These hypervisors runona conventionaloperatingsystem(OS)justasother
computerprogramsdo.A guest operating system runsasaprocesson the
host. Type-2 hypervisors abstract guest operating systems from the host
operating system. Examples:
• VMware Workstation/Player,
• VirtualBox,
• Parallels Desktop for Mac
• KVM for Linux and bhyve for FreeBSD*.
8. 2.3.Containers
• Containers are an abstraction at the applayer that
packages code and dependencies together. Multiple
containers can run on the same machine and share
the OS kernel with other containers.
• ContainersprovideOS-levelprocessisolation
whereas virtual machines offer isolation at the
hardware abstraction layer (i.e., hardware
virtualization).
• In IaaS use cases machine virtualization is an ideal
fit, while containersarebestsuitedfor
packaging/shippingportableandmodularsoftware.
• Containers take up less space than VMs (container i
mages are typicallytens of MBsin size), and
start almost instantly.
9. 3.Virtualizationtools
T1.VMwarevSphereESXi
VMwareESXi(formerly ESX;ElasticSkyX) is an enterprise-class, type-1hypervisor developed byVMware for deploying
and serving virtual computers. As a type-1hypervisor, ESXi is not a software application that is installed on an OS;
instead, it includes and integrates vital OS components, such as a kernel.
10. T1.Hyper-V
Hyper-Vis a "type1" or "native" hypervisor.That means it has direct access to the physical machine's hardware. The
standalone version of Hyper-Vwill run on "bare metal" — that is, you don't have to install it on an underlying host
operating system.
Hyper-Vwas first released alongside Windows Server 2008, and has been available without charge for all the Windows
Server and some client operating systems since.
12. E.Docker
A container image is a lightweight, stand-alone, executable package of a pieceof software that includes
everything needed to run it: code,runtime,systemtools,systemlibraries,settings.Available for bothLinux
and Windows (native support since W10) basedapps, containerized software will always run the same,
regardless of the environment.
What allows Docker?
Container virtualization
Build, pack, ship and run
applications as containers
Build once, run in many places
Isolated and content agnostic
13. E.XenApp
XenApp is an application virtualization solution that allows universal access to virtual apps,desktops, and data
from any device.
It delivers centrally-hosted Windows applications to local devices without the necessity of installing them. It is
the flagship product for Citrix and was formerly known under the names WinFrame, MetaFrame, and Presentation
Server.
16. 1.WhatHAmeans?
HighAvailability(HA)refers to a system or component that is continuously operational for a desirably long
length of time
i.e. HA at level 99.999% means that the downtime is less than 5.26 minutes per year
http://searchdatacenter.techtarget.com/definition/high-availability
23. 2.2.NetworkLoadBalancing(NLB)
• NLB is a feature that distributes network traffic among multiple servers or virtual machines within a
cluster to avoid overloading any one host and improveperformance
• NLB as WS2012 built-in feature vshardware LB
• NLB vsALB (application)
• Small company vs bigenterprise
• NLB vsDBLB(DB Clustering)
http://searchservervirtualization.techtarget.com/definition/Network-Load-Balancing-NLB
28. 2.4.FailoverCluster
If one of the servers, or nodes, fails, another
node in the cluster can take over its workload
without any downtime.
http://lh4.ggpht.com/_p2ZBNGf_7w8/TbDNNN07n8I/AAAAAAAAGfo/TMKBHwMsAew/image_thumb%5B26%5D.png?imgmax=800
29. WindowsAzureHyper-VRecoveryManager
Hyper-V Recovery Manager uses the
capabilities provided by WindowsServer's
Hyper-VReplicafeaturetobackupVMs
froma primarydatacentertoa
secondarydatacenter.In the event of an
outage at the primary data center,
Hyper-V Recovery Manager automatesthe
failoverprocessto bring workloads
back up at the secondary site with
minimal downtime. Hyper-V Recovery
Manager can also beused to test the
recovery process
https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/65/88/metablogapi/7080.clip_image004[8].png
searchservervirtualization.techtarget.com/definition/Windows-Azure-Hyper-V-Recovery-Manager
30. VMMperformancemanagement
VMMDynamic Optimization
During Dynamic Optimization, VMM migrates virtual
machines within a host cluster to improve load
balancing among hosts and to correct any
placement constraint violations for virtual
machines.
VMMPower Optimization
Power Optimization is an optional feature of
Dynamic Optimization, and it is only available when a
host group is configured to migrate virtual
machines through Dynamic Optimization. Through
Power Optimization, VMM helpstosaveenergyby
turningoffhoststhatarenotneededtomeet
resourcerequirementswithina hostclusterand
turns the hosts back on when they are needed again.
https://technet.microsoft.com/en-us/library/gg675109(v=sc.12).aspx