S4726 VIRTUALIZATION AN INTRO TO VIRTUALIZATION. Luke Wignall & Jared Cowart Senior Solution Architects GRID

Transcription

1 S4726 VIRTUALIZATION AN INTRO TO VIRTUALIZATION Luke Wignall & Jared Cowart Senior Solution Architects GRID

2 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

3 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.

4 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.

5 VIRTUALIZATION 101: A SIMPLE VISUAL

6 VIRTUALIZATION 101: A LITTLE HISTORY Today The age of the Mainframe Centralized computing First virtualization Thin Clients The PC arrives Decentralized computing Things get complicated PC sprawl Bubble bursts The cloud moves in again Centralized computing Return to Virtualization and Thin Clients The Internet of Things, then the Internet of Everything!

7 SO WHY VIRTUALIZE: RESOURCE OPTIMIZATION! Increased density Improves resource optimization but without sacrificing performance Physical World Virtual World 1:1 1:1 1:1 1:1 1:1 1:1 Many:1

8 SO WHY VIRTUALIZE: RESOURCE OPTIMIZATION! Underutilized hardware VMware in 2007: +20% of physical servers at <0.5% of util, 75% at <5% % % % 80.00% 60.00% 40.00% 20.00% 0.00% Actual Use Forecast Use Cost Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7

9 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 " " E b " M e

10 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

11 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

12 SO WHY VIRTUALIZE: BUT WHAT ABOUT DESKTOPS? Business demanded: Cost savings Flexibility Mobility End users demanded: Frequent refresh More power Mobility BYOD Graphics

13 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

14 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!

15 THE HOW: SERVERS, GOING FROM PHYSICAL TO VIRTUAL Physical Server Virtual Server Virtual Server Same hardware Tiny hypervisor Flexibility Scalability Security Recoverability Hypervisor of choice Same Physical Hardware

16 THE HOW: POWER OF BEING VIRTUAL MOTION! Virtual Server Virtual Server Virtual Server Same Hypervisor of choice Same Hypervisor of choice Same Physical Hardware Same Physical Hardware

17 THE HOW: POWER OF BEING VIRTUAL MOTION! Virtual Server Virtual Server Virtual Server Virtual Server Hypervisor Hypervisor Hypervisor Host Host Host SAN Attached storage holds vdisks Adds more flexibility (motion)

18 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

19 THE HOW: DESKTOPS, GOING FROM PHYSICAL TO VIRTUAL Physical Workstation Virtual Virtual Virtual Virtual Virtual Virtual Virtual Workstation Hypervisor of choice Server hardware Density math Like VM s Flexibility Scalability Security Recoverability Server Physical Hardware

20 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!)

21 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!

22 WHY DOES NVIDIA CARE? CPU VS. GPU CPU Optimized for Serial Tasks GPU Accelerator Optimized for Many Parallel Tasks Physical CPU in host Shared Doing networking NOT a GPU! Impacts density!

23 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)

24 SEGMENTING THE USER POPULATION DESIGNER POWER USER Tier 1 (e.g. design engineers) Designing / Rendering 3D High Definition Graphics KNOWLEDGE WORKER Tier 2 (viewing/editing of 3D drawings) Viewing or working with 3D HD Graphics Tier 3 (typical knowledge workers) Becoming more visual!

25 DESIGNER IMPORTANCE OF GPU POWER USER VIRTUAL WORKSTATION Nice to Have GPU Needs GPU 3D Engineering & Design Apps Office Productivity PLM & Volume Design KNOWLEDGE WORKER VDI / Virtual App Windows 7 Web

26 NVIDIA GRID K2 DESIGNER NVIDIA GRID K1 POWER USER GPU 4 Kepler GPUs 2 High End Kepler GPUs CUDA Cores 768 (192/GPU) 3072 (1536/GPU) KNOWLEDGE WORKER 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) 1 Number of users depends on software solution, workload, and screen resolution

27 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

28 GPU PASS-THROUGH (VDGA) HARDWARE VIRTUALIZATION SOFTWARE App App App VDA App Virtual Driver Virtual Driver GUEST OS Virtual Driver Virtual Driver VIRTUAL MACHINE vcpu vmemory vstorage vnetwork NVIDIA Driver GPU HYPERVISOR SERVER NVIDIA Accelerated Capture CPU Memory Storage Network GPU NVIDIA Pass-Through Client GRID K1 GRID K2 Quadro Quadro K5000

29 GPU VIRTUALIZATION (VGPU) Software App App App VDA App Virtual Driver Virtual Driver Guest OS Virtual Driver Virtual Driver NVIDIA Driver Standard NVIDIA Driver Citrix XenServer Client Virtualization HYPERVISOR VIRTUAL MACHINE vcpu vmemory vstorage vnetwork vgpu GRID vgpu Manager NVIDIA GRID software from NVIDIA GRID K1, K2 Hardware CPU Memory Storage Network Server GPU

30 Graphics Options in Virtualization

31 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.

32 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

33 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

34 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

35 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

36 DENSITY MATH Bottlenecks IOPS? CPU? Networking? GPU? Breathing room Plan for spikes! Babysitting Monitoring (Lakeside promo, Tuesday PM session) Metric tracking

37 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!

38 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.)

39 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!

40 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!

41 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, physical PC s needing 1:1 admin Distributed security concerns

42 CASE STUDY: SERVER DISTRIBUTION OF VDI 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 400 Total End Users Server w/ 64 Users on 2x K1 s Server w/ 16 Users on 2x K1 s Server w/ 64 Users on 2x K1 s Server w/ 0 Users on 2x K1 s Assumption: The recommended number of users/desktops on a server is 64. There is room for some growth on the 7 th server. High Availability: Allows for all users on one host to be vmotioned to this host.

43 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

44 $1,400,000 $1,200,000 CASE STUDY - 10 YEAR CAPEX Phy PC VDI PC Total Exp VDI Total Exp $1,000,000 $800,000 $600,000 $400,000 $200,000 $0 Year 0 Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10

45 QUESTIONS

46 THANK YOU! Keep learning! Subsequent sessions: S Virtual is Better than Physical Delivering a Delightful User Experience from a Virtual Desktop - NEXT! S Delivering High-Performance Remote Graphics with NVIDIA GRID Virtual GPU S NVIDIA GRID for VDI: How To Design And Monitor Your Implementation S If You Build It, Will They Come? Better Question Is, Will They Stay? and so much more, keyword GRID!