Slides from June 7, 2011 presentation by Ron Oglesby, presented by ILTA, and sponsored by Unidesk and Pano Logic on why server virtualization was so successful and what has been holding back desktop virtualization. Presentation also features Tom Crowe of Wyche.
Unpacking Value Delivery - Agile Oxford Meetup - May 2024.pptx
Server Virtualization - Smashing Success! Desktop Virtualization - Not So Much. Why?
1. Webinar: Server Virtualization: SuccessVDI: Not So Much…Why? Ron OglesbyVMware vExpert Citrix CTP Microsoft MVPChief Solution Architect Tom CroweInformation Technology Manager Dave HurlburtTerritory Manager
5. Server virtualization is easy! CAPEX savings is EASY to show Savings are HUGE! Already in the datacenter – it’s a form factor change! Standardization is a GOOD THING! OPEX is simply a nice byproduct Let’s face it – a P2V is a simple migration process
6. So why is VDI ‘on hold’ in so many organizations?
7. VDI is not so easy! Host Servers Storage Brokers Image Management Protocols Disk IO issues Personalization Loss of Control
8. VDI ROI isn’t as clear CAPEX is tough to show OPEX is pretty much the only savings available Desktops have to be “moved” Users don’t like “standardization” Let’s face it, there isn’t an “easy” migration process to virtual desktops A number of “secondary” products are needed
10. It’s really not about the brokers anymore View™ XenDesktop® Fast protocol PCoIP Non-persistent desktop provisioning & storage reduction Composer/Linked Clones Basic profile mgmt. RTO asset acquisition Fast protocol ICA/HDX Non-persistent desktop provisioning & storage reduction Provisioning Server Basic profile mgmt. Sepago asset acquisition
11. It’s about the tradeoffs (pick 2, or maybe 1) VDI SuccessTriangle
12. Key issues in more detail Single image management comes with a price Personalization means loss of single image management Personalized desktops increase storage costs(footprint) VDI itself has higher IO requirements than servers! All of this on top of user acceptance issues No good offline tools today Brokers don’t always scale to the thousands very well
16. The Storage Challenge Capacity footprint can be reduced via numerous technologies IO… not so much Desktop IOPS rules of thumb? Low: 3-4 Med: 6-12 Heavy:16-20 What is all this RAID penalty stuff? Must design to handle the IO load
17. The Management Challenge Generally there are big trade-offs Aim for single image management and you lose “persistent” desktops that sustain user persona Use persistent desktops and you lose single image management (and move right back to traditional,higher OpEx desktop management) Single image management reduces storage footprint(linked clones, PVS) but at the cost of personalization Do existing management tools fit the VDI world or your use case?
19. Common mistakes in VDI Designing the hardware first Too many variables to choose hardware out of the gate Just duplicating server virtualization hardware won’t work Believing everything the vendors say “The vendor said I could easily virtualize all of my apps.” “The vendor said I could get 120 desktops per host.” Not configuring the disk subsystem properly Forgetting about “personalization” of the desktop
20. Key “check boxes” for your design Define what you are delivering and for whom Ensure your design covers the following: Base OS delivery and updating Application delivery and updating (even the complex apps) Personalization (including user-installed apps) Broker configuration and requirements Non-persistent vs. persistent desktop use cases Storage configuration (capacity footprint AND IO load) WAN, LAN, and offline use cases
21. Hardware recommendations Smaller servers with more cores Good storage controllers More memory NEW: solid state drive (SSD) Hybrid arrays combineSSD and SAS in single array with intelligent data placement to solve IOPS and capacity problems NEW:zero clients Less energy & fewer breakable parts vs. thin clients Build redundancy through quantity
22. Software recommendations NEW: desktop layering solutions Eliminate “pick 1 or 2” tradeoffs Combine single image patching, easy app delivery, full user personalization, and storage savings in one solution
36. Technology Shared with virtual servers Cisco 3750G switches HP Lefthand P4500 iSCSI SAN vSphere 4 Advanced Pano Logic Zero-Client usingPano Broker No OS on the hardware Unidesk VDI Provisioning and Management OS and App deployment and User personalization
37. Technology Servers HP Proliant DL360 G6 2 x Xeon E5504 @ 2 Ghz (8 cores total) 36 GB memory 2 x 72 GB SAS for boot and logging 6 x 1 Gb NIC ports HP Lefthand P4500 SAN 2 nodes 12 x 450 GB SAS per node 2 x 1 GB NICs Desktop VMs Windows XP SP3 1 GB memory 30 GB “hard drive” thin 8 GB user data Consolidation of ~25 desktops per vSphere host
38. Zero-client with no OS on the hardware No local desktop support concerns Small desktop footprint: 3.5” x 3.5” x 2.0” Low power usage: 6.5W max, < 0.2W sleep Pano Broker Included with Pano device purchase Simple management interface Integrates seamlessly with vSphere Pano Remote Access Windows 2008 Terminal Services Gateway Pano USB dongle is simple to use
39. OS, Application, and User State virtualization Desktop is composed at boot with all required apps and OS layers Persistence of user persona regardless of desktop Single-image management for OS and Apps, reduced SAN storage Security updates applied to primary OS or App layer pushed out immediately or on schedule; guarantees all updates are applied
40. Unidesk Application layers make it easy to deliver any app Packaging requires only a normal installation (Setup), then assign the layer to 1 or more desktops
41. Testing and Rollout Pilot group was pivotal - ~2 months Rollout to groups, do not convert an entire practice area at a time. ~ 1 month to deliver to all users Monitor host performance closely performance with 25 VMs is different than 5. Be aware of specific apps and how they impact a host. Anti-virus adds 3-5% to idle CPU of VM, x25 VMs can be a problem.
42. VDI Reality … 18 months later User feedback is important Easy to improve performance for users All devices are now more tightly connected Visibility into the user experience is difficult without additional tools Peripherals are difficult Saved money over traditional desktops? Not yet but getting there Would I do it again? YES!
44. Pano Logic Profile Founded in August 2006 Headquarters North America: Redwood City, CA EMEA: Munich, Germany Investors Foundation Capital Goldman Sachs Mayfield Fund FY2010/11 – Doubled Revenue Over 250 Channel Partners 1000+ Customers 75,000 + Zero Client Deployed Fujitsu Zero Client Monitor, Powered by Pano eWeek’s “Analyst Choice”, January 2011 PANO LOGIC CONFIDENTIAL
46. The Pano System Three Components Pano zero client Pano Direct Service Pano Manager The Pano System is a Cloud-Ready Architecture Pano Remote Pano Zero Client 2. Pano Software 1. Pano Zero Client No Processor No OS No Drivers No Security Holes No Storage No Firmware No Moving Parts Purpose-Built for VDI Device Management User Provisioning Standardization Hardware Upgrades Innovative zero protocol
Hello and thank you for your interest learning more about how pano logic is radically changing how businesses manage their desktop computing.
The Secret sauce. Stretching the I/O bus. The applications and peripherals are basically faked as being local to virtual server you have installed our solution on. Hence, no endpoint drivers to install, or firmware updates to deploy at the end point. If your applications and peripherals are Windows native, they just work 99% of the time.
We built the solution to support VMware with the long term objective of being agnostic to the Hypervisor in the data center. We recently introduced support for Citrix XenDesktop 4 & 5, as well as Microsoft’s HypervV. We have saved 100’s of organizations thousands of dollars in License fees by deploying the our own broker that is inclusive of the solution. However, we can also hand off the broker functionality to products like VMware View. The goal is to allow the customer freedom of choice on the back end, we would like to be the end point regardless of your back end virtual infrastructure.