3d cubes building blocks stacked 3x3x3 powerpoint presentation templates.
Intro to Virtualization 101 - NVIDIA · We were happy in our cubes ... Designing / Rendering 3D...
Transcript of Intro to Virtualization 101 - NVIDIA · We were happy in our cubes ... Designing / Rendering 3D...
S4726 VIRTUALIZATION 101 - AN INTRO TO VIRTUALIZATION
Luke Wignall & Jared Cowart Senior Solution Architects | GRID
AGENDA § Virtualization 101
— The Definition
— The History
— The Benefits
§ Fundamentals of virtualization technology — Servers (VMs)
— Desktops (VDI) — Applications
§ Why does NVIDIA care about virtualization? — The power of GPUs
§ ROI examples
VIRTUALIZATION 101: WIKIPEDIA DEFINITION… § Virtualization, in computing, refers to the act of creating
a virtual (rather than actual) version of something, including but not limited to a virtual computer hardware platform, operating system (OS), storage device, or computer network resources.
§ The term "virtualization" traces its roots to 1960s mainframes, during which it was a method of logically dividing the mainframes' resources for different applications. Since then, the meaning of the term has evolved to the aforementioned.
VIRTUALIZATION 101: SIMPLE DEFINITIONS… § Server virtualization allows you to run multiple virtual
machines on a single physical server.
§ Desktop virtualization allows you to run multiple desktop machines on a single physical server, and distribute them.
§ Application virtualization allows you to distribute multiple copies of an application from a single physical server.
VIRTUALIZATION 101: A SIMPLE VISUAL…
VIRTUALIZATION 101: A LITTLE HISTORY…
The cloud moves in… again
§ Centralized computing
§ Return to Virtualization and Thin Clients
§ The Internet of Things, then the Internet of Everything!
1960 1970 1980 1990 2000 2010 Today
The age of the Mainframe
§ Centralized computing
§ First virtualization
§ Thin Clients
The PC arrives
§ Decentralized computing
Things get complicated
§ PC sprawl
§ Bubble bursts
SO WHY VIRTUALIZE: RESOURCE OPTIMIZATION! § Increased density
§ Improves resource optimization but without sacrificing performance
Physical World Virtual World
1:1
1:1
1:1 Many:1
1:1
1:1
1:1
SO WHY VIRTUALIZE: RESOURCE OPTIMIZATION! § Underutilized hardware
— VMware in 2007: +20% of physical servers at <0.5% of util, 75% at <5%
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%
140.00%
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7
Actual Use
Forecast Use
Cost
SO WHY VIRTUALIZE: THE OTHER ADVANTAGES… § Partitioning
— Run multiple operating systems on one physical machine
— Share physical resources between virtual machines
§ Portability — Entire virtual machine is saved as a file, so…
— Move, copy, or export as easily as a file
§ Security — Hardware is isolated from the operating system
— Recovery as easily as restoring a file
§ Agnostic — Migrate a virtual machine between similar, or different, physical servers
14
VMware
Key Properties of Virtual Machines : Continued
Partitioning " Run multiple operating systems on one physical machine
" Divide system resources between virtual machines
Isolation " Fault and security isolation at the hardware level
" Advanced resource controls preserve performance
Encapsulation
" Entire state of the virtual machine can be saved to files
" Move and copy virtual machines as easily as moving and copying files
SO WHY VIRTUALIZE: BUT WHAT ABOUT DESKTOPS? § We thought in terms of the personal computer
— 1:1 computer to worker
— Refreshed every 3-5 years
§ We were happy in our cubes — It was the only place we could connect
§ IT budgets grew with PC sprawl
SO WHY VIRTUALIZE: BUT WHAT ABOUT DESKTOPS? § Resource management issues
— Order in bulk, homogony saves money
— Buy for the most demanding group of users, overkill for rest
— Satisfying end user experience
§ High end users — Each one is custom
— Chained to desk
— Required GPU
§ IT operations staff to manage it all — Security/Anti-virus/Updates/Patches
— Hardware issues
— Distributed/Geography
SO WHY VIRTUALIZE: BUT WHAT ABOUT DESKTOPS? § Business demanded:
— Cost savings
— Flexibility
— Mobility
§ End users demanded: — Frequent refresh
— More “power” — Mobility
— BYOD
— Graphics
SO WHY VIRTUALIZE: AND WHAT ABOUT APPS? § Application virtualization allows distribution of multiple
copies of an application from a single physical server. — Streamed to BYOD — Centrally managed — Ease of support
§ Typical solutions: — Citrix Metaframe…Presentation Server…now XenApp
— VMware ThinApp — Microsoft App-v
— Others…
HOW DOES IT WORK: IT STARTED WITH SERVERS § Eureka! We just lie to the Operating system! § We insert a hypervisor to manage the host hardware § We load “servers” as guests on the host hardware
— Para-virtualized vs. Full
— Enlightened
§ The hypervisor will tell the guest OS whatever we want — Vanilla drivers
— Flexibility
…its like magic!
THE HOW: SERVERS, GOING FROM PHYSICAL TO VIRTUAL
§ Same hardware § Tiny hypervisor § Flexibility § Scalability § Security § Recoverability
Physical Server
Virtual Server
Virtual Server
Hypervisor of choice
Same Physical Hardware
THE HOW: POWER OF BEING VIRTUAL – MOTION!
Virtual Server
Same Hypervisor of choice
Same Physical Hardware
Virtual Server
Virtual Server
Same Hypervisor of choice
Same Physical Hardware
THE HOW: POWER OF BEING VIRTUAL – MOTION!
Attached storage holds vDisks
Adds more flexibility (motion)
Virt
ual S
erve
r
Virt
ual S
erve
r
Hypervisor
Host
SAN
Virt
ual S
erve
r
Hypervisor
Host
Virt
ual S
erve
r
Hypervisor
Host
BACK TO WHY: WHAT ABOUT DESKTOPS THEN? § If servers, why not desktops?
— Administration: Cat herding
— Security: No moat big enough
— Budget: The cost of one of everything
§ End users…they are NOT virtual! — The power of “more”
§ Multi-media is only increasing
— The power of “mine!” § Huge mistake to take things away from end users
— The power of “meh” § Their home PC with Win7 looks better than VDI
§ Huge project dies thanks to CEO receptionist
THE HOW: DESKTOPS, GOING FROM PHYSICAL TO VIRTUAL
§ Server hardware § Density math § Like VM’s
— Flexibility
— Scalability — Security
— Recoverability
Physical Workstation
Hypervisor of choice
Server Physical Hardware
Virtual Workstation
Virtual Workstation
Virtual Workstation
Virtual Workstation
Virtual Workstation
Virtual Workstation
Virtual Workstation
PITFALLS OF VIRTUALIZATION THE DARK SIDE… § Planning
— Devil in the details (SOLUTION: Start simply!)
§ Implementation — KISS (SOLUTION: Start simply!)
— Over deploy to group (GPU) — Metrics/Monitor, optimize after acceptance
§ Resource contention — Density issues (SOLUTION: Add resources)
§ Adoption — “meh” will kill the whole project (SOLUTION: GPU!)
WHY DOES NVIDIA CARE? END USER EXPERIENCE! § Users expect as good or better than physical
— “meh” earns a FAIL
§ Designers require 3D High Definition graphics — Highly paid employees
— Core of the business — Previously NOT an option for VDI
§ CPU is simply not a GPU § Future will be more visual, not less!
WHY DOES NVIDIA CARE? CPU VS. GPU
§ Physical CPU in host — Shared
— Doing networking — NOT a GPU!
§ Impacts density!
CPU Optimized for Serial Tasks
GPU Accelerator Optimized for Many
Parallel Tasks
VISUAL REALISM AND ACCURACY VISUAL REALISM AND ACCURACY VISUAL REALISM AND ACCURACY VISUAL REALISM AND ACCURACY VISUAL REALISM AND ACCURACY WHY DOES NVIDIA CARE? VISUAL REALISM AND ACCURACY
Complex materials surfaces, reflections and shadows Fast and Interactive Performance
Without RealView (without GPU) With RealView (with GPU)
SEGMENTING THE USER POPULATION
Tier 1 (e.g. design engineers) Designing / Rendering 3D High Definition Graphics
Tier 2 (viewing/editing of 3D drawings) Viewing or working with 3D HD Graphics
Tier 3 (typical knowledge workers) Becoming more visual!
DESIGNER
KNOWLEDGE WORKER
POWER USER
Windows 7
Nice to Have GPU Needs GPU
Office Productivity
Web
PLM & Volume Design
3D Engineering & Design Apps
VIRT
UA
L W
ORK
STAT
ION
VD
I / V
irtu
al A
pp
DESIGNER
KNOWLEDGE WORKER
POWER USER
IMPORTANCE OF GPU
GPU 4 Kepler GPUs 2 High End Kepler GPUs
CUDA Cores 768 (192/GPU) 3072 (1536/GPU)
Memory Size 16GB DDR3 (4GB/GPU) 8GB GDDR5 (4GB/GPU)
Max Power 130 W 225 W
Equivalent Quadro with Pass-through Quadro K600 (entry) Quadro K5000 (high end)
NVIDIA GRID K2
1 Number of users depends on software solution, workload, and screen resolution
NVIDIA GRID K1
DESIGNER
KNOWLEDGE WORKER
POWER USER
DELIVERING GPU: THE MISSING INGREDIENT FOR VDI! § NVIDIA Quadro for professional graphics
— The trusted industry standard
— ISVs look for NVIDIA driver
§ All users expect a great visual experience! § The challenge: How to deliver in a virtual environment?
— Avoid physical desktop issues
— Take advantage of virtual benefits
GPU PASS-THROUGH (VDGA)
GUEST OS H
ARD
WA
RE
SOFT
WA
RE
Virtual Driver
Virtual Driver
Virtual Driver
Virtual Driver
VIRT
UA
LIZA
TIO
N
HYPERVISOR
VIRTUAL MACHINE
vCPU vMemory vStorage vNetwork
App App App App VDA
Client NVIDIA Driver
GPU
SERVER CPU Memory Storage Network GPU
GRID K1 GRID K2
Quadro 2000-6000 Quadro K5000
NVIDIA Pass-Through
NVIDIA Accelerated Capture
HYPERVISOR
Guest OS
Server
CPU
GPU VIRTUALIZATION (VGPU)
Har
dwar
e
Memory Storage Network
Soft
war
e
Virtual Driver
Virtual Driver
Virtual Driver
Virtual Driver
Virt
ualiz
atio
n
VIRTUAL MACHINE
vCPU vMemory vStorage vNetwork
App App App App VDA
Client
GPU
NVIDIA Driver
vGPU
GRID vGPU Manager GRID K1, K2
Citrix XenServer
NVIDIA GRID software from NVIDIA
Standard NVIDIA Driver
Graphics Options in Virtualization
A TYPICAL VIRTUALIZATION PROJECT § Phase 1: Analysis & Planning § Phase 2: Design § Phase 3: POC § Phase 4: Rollout § Then let it bake… § …if that goes well then expand.
A TYPICAL VIRTUALIZATION PROJECT
Implementation —Analysis & Planning
Phase
Use Case Analysis: User groups, application sets, workflows, peripherals, network connections, and locations
User Segmentation
Designers and Engineers — use vDGA, vGPU
Editors and Viewers — use vDGA, vSGA, vGPU
A TYPICAL VIRTUALIZATION PROJECT
Implementation —Design Phase Phase
Design Focus Network — type, bandwidth, latency, QoS VM Configuration — vCPU allocation User Density per physical or virtual server VM Density per hypervisor host
Hypervisor configuration Storage infrastructure
A TYPICAL VIRTUALIZATION PROJECT
Implementation — POC Phase Phase
Proof of Concept Select user group
Common set of simple apps
Measurable expectations
Capacity Planning and Sizing
Use POC Results
Use Lakeside, SysTrack
A TYPICAL VIRTUALIZATION PROJECT
Implementation — Rollout Phase Phase
Monitor and Tune VM Configuration (vCPU allocation, memory allocation, etc.)
VM Density per Host, decrease or increase number of VMs
DENSITY MATH § Bottlenecks
— IOPS?
— CPU?
— Networking? — GPU?
§ Breathing room — Plan for spikes!
§ Babysitting — Monitoring (Lakeside promo, Tuesday PM session)
— Metric tracking
THE WHAT: VIRTUALIZATION INGREDIENTS § Server, er…HOST hardware
— RAM, RAM, and more RAM: When to over subscribe
— NICs: Must have clean networking
— Local storage, or no local storage (IOPS?)
§ Hypervisor
§ Storage — SAN
— NAS
— NFS
§ Server, er…GUEST operating system — i.e. Workloads
§ GPU – the missing ingredient!
CASE STUDY ALL SITUATIONS ARE UNIQUE… § … but the math is similar § Knowledge Worker GPU upgrade
— EU Bank
— 400 Users
— Knowledge Workers (tellers, loan officers, etc.)
CASE STUDY: VDI FOR KNOWLEDGE WORKERS § Knowledge Workers are typical POC starting point
— Less costly downtime
— Typically simple apps, common builds
§ Greatest number of desktops to manage — High help desk needs
§ Becoming graphics users — Office 2013 (PowerPoint)
— Flash, HTML5, etc. — Perception is GPU is too costly
§ Many existing deployments stalled — Poor adoption, why? GPU!
CASE STUDY: ASSUMPTIONS § Customer is needing to improve EUC experience in existing
VMware deployment for 400 users § VMware Horizon View is in place, so not factoring that cost. § So, also not factoring in physical PC costs like 400 antivirus
licenses § ESXi is included in View licensing § vSGA is the GPU sharing method § vMotion is a requirement, downtime is unacceptable § 64 VDI’s, using 512MB of FB RAM, per server is max. § What if we gave them high end solution!
CASE STUDY: TYPICAL KNOWLEDGE WORKER PHYSICAL PC
§ Mini Tower or similar
§ Quad Core i5
§ 4GB RAM
§ Integrated HD Graphics
§ Windows 7/8 Pro
§ 24” Monitor
§ Cost: ~$830/user
§ 400 users x $830 = $332,000
§ 400 physical PC’s needing 1:1 admin
§ Distributed security concerns
CASE STUDY: SERVER DISTRIBUTION OF VDI’S
400 Total End Users Server w/
16 Users on 2x K1’s
Server w/ 64 Users on
2x K1’s
Server w/ 64 Users on
2x K1’s
Server w/ 64 Users on
2x K1’s
Server w/ 64 Users on
2x K1’s
Server w/ 64 Users on
2x K1’s
Server w/ 64 Users on
2x K1’s
Server w/ 0 Users on 2x
K1’s
High Availability: Allows for all users on one host to be vMotioned to this host.
Assumption: The recommended number of users/desktops on a server is 64. There is room for some growth on the 7th server.
CASE STUDY: CUTTING EDGE KNOWLEDGE WORKER VDI
HP DL380p 2 Socket, 8 core CPUs 256GB RAM 2TB Local storage 2x GRID K1 GPU cards Cost: ~$21,000 8 servers = $168,000 Windows 7/8 Pro Licenses 400 x $130 = $52,000 HP t410 AiO Thin Client Cost: ~$420/ea 400 users x $420 = $168,000 Total: $388,000 ($970/user) 1 master image to manage Centralized Security
CASE STUDY - 10 YEAR CAPEX
$0
$200,000
$400,000
$600,000
$800,000
$1,000,000
$1,200,000
$1,400,000
Year 0
Year 1
Year 2
Year 3
Year 4
Year 5
Year 6
Year 7
Year 8
Year 9
Year 10
Phy PC VDI PC Total Exp VDI Total Exp
QUESTIONS
THANK YOU! § Keep learning!
— Subsequent sessions: S4783 - Virtual is Better than Physical – Delivering a Delightful User Experience from a Virtual Desktop - NEXT!
S4725 - Delivering High-Performance Remote Graphics with NVIDIA GRID Virtual GPU
S4686 - NVIDIA GRID for VDI: How To Design And Monitor Your Implementation
S4948 - If You Build It, Will They Come? Better Question Is, Will They Stay? …and so much more, keyword “GRID”!