Server Virtualization: Success - VDI: not so much... Why?


Published on

Slides from Ron Oglesby's presentation at BriForum Chicago 2011.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • ObjectivesUnique complimentary value to vmware guysAre you willing to engage
  • Server Virtualization: Success - VDI: not so much... Why?

    1. 1. Server Virtualization: SuccessVDI: not so much…Why?.Ron Oglesby @ronoglesby<br />NOT A UNIDESK COMMERCIAL<br />
    2. 2. What are we going to talk about<br />Why is Desktop Virtualization on hold?<br />What are the key issues?<br />Common misconceptions about desktop virtualization<br />How to get past these issues<br />Where is all of this going anyway?<br />
    3. 3. VDI Has Awesome Potential <br />Increase operational efficiency<br />Simple provisioning, patching, repair for IT<br />Improve business continuity & agility<br />Workers access desktopsfrom any office,BYOPC, home PC, or mobile device<br />Increase security<br />Data stays inside the data center<br />Go green<br />Thin clients use less power than PCs(5W vs. 60W) and last 3-6 years longer<br />
    4. 4. So why was server virtualization so successful? <br />
    5. 5. Server virtualization rocked!<br />
    6. 6. Server Virtualization was easy!<br />CAPEX savings was EASY to show<br />Savings were HUGE!<br />Already in the datacenter – It’s a form factor change!<br />Standardization was a GOOD THING!<br />OPEX was simply a nice by product<br />Let’s face it, a P2V was a simple migration process<br />
    7. 7. So why is VDI on ‘hold’ in so many organizations?<br />
    8. 8. So what about VDI? Not easy?<br />Host Servers<br />Storage<br />Brokers<br />Image Management<br />Protocols?<br />Disk IO issues<br />Personalization<br />Loss of Control<br />
    9. 9. VDI: More complex than it should be?<br />Copyright © 2010 Unidesk Corporation. All Rights Reserved.<br />Profile Mgmt<br />App Mgmt<br />Storage Footprint<br />Client Mgmt<br />Image/OS Mgmt<br />
    10. 10. Desktop Virtualization is not as easy<br />CAPEX is almost impossible to show<br />OPEX is pretty much the only savings available<br />Desktops have to be “moved”<br />Users don’t “like” standardization<br />Let’s face it, there isn’t an “easy” migration process to virtual desktops<br />A number of “secondary” products are needed<br />
    11. 11. So what are the key issues in these desktop projects?<br />
    12. 12. Pick 2 (or sometimes 1!)<br />VDI SuccessTriangle<br />
    13. 13. Key Issues<br />Single image management comes w/ a price<br />Personalization means loss of single image management<br />Personalized desktops increase storage costs (foot print)<br />VDI itself has higher IO requirements than servers!<br />All of this on top of user acceptance issues<br />No good offline tools today<br />Brokers don’t always scale to the thousands very well<br />
    14. 14. Do you have a desktop Virtualization strategy?<br />
    15. 15. Start with your current Desktop Strategy<br />
    16. 16. Make sure your VDI project FITS!!!<br />VDI – <br />(Kudos to VMware) Tied Virtual Desktops to VDI.<br />VDI is another tool…<br />Terminal Services…<br />App Virtualization…<br />Client side virtualization?<br />
    17. 17. Personalization: What do you and the users see?<br />What you see:<br />What users see:<br />
    18. 18. So what makes up a virtual desktop?<br />Profile<br />Typical view of desktop<br />This does not match reality<br />OS and up are hopelessly merged<br />Applications<br />Operating System<br />Hypervisor<br />Hardware<br />
    19. 19. How we want to manage the desktop<br />Profile<br />User customization often includes application installation, application add-ins and ties to the machine<br />Applications<br />Applications can tie to SIDs, UUIDs, and GUIDs on the machine – Machine specific settings<br />Operating System<br />Hypervisor<br />All of this makes it tough to extract and maintain a “user environment” through changes to gold images<br />Hardware<br />
    20. 20. Disk IO… the common problem. <br />Footprint can be reduced via numerous technologies<br />IO… not so much<br />Server IO loads? What is/was typical<br />Desktop IO load<br />What is all this RAID penalty stuff?<br />
    21. 21. Disk IO Solutions?<br />Man in the middle solutions? Atlantis type solutions?<br />Hybrid Arrays? Dell/EQL XVS – EMC FAST?<br />Homemade!?! ZFS <br />Local Disk? SSD or even distributed rotating media<br />
    22. 22. Management and personalization<br />Generally there are numerous trade-offs<br />Single image mgmt and you lose “persistent” desktops<br />Use persistent desktops – you lose single image mgmt and move right back to traditional desktop mgmt<br />Single image mgmt reduces storage footprint (linked clones, provisioning server) but at the cost of personalization. <br />Do existing Mgmt tools fit the VDI world or your use case? Possibly. <br />
    23. 23. Management Solutions?<br />Block based provisioning alone NOT the solution<br />Layering technology is one option<br />The Unidesk and Moka5’s of the world<br />Multiple tools <br />Stack provisioning tools w/ a profile/User environment manager<br />Apps – App virt not the key to everything. <br />
    24. 24. So what should I be on the look out for?<br />
    25. 25. Common Mistakes in VDI<br />Designing the hardware first<br />To many variables to choose hardware out of the gate;<br />Just duplicating Server Virt hardware<br />Believing everything the vendors say…<br />Buying software because the “vendor said” it would do what I needed<br />The vendor said I could get 120 Desktops on this system<br />Not configuring the Disk subsystem properly<br />Forgetting about “personalization” of the desktop<br />
    26. 26. Key “Check Boxes” for your design<br />Define what you are delivering and to who<br />Ensure your design covers the following:<br />Base OS delivery and updating<br />Application delivery and updating<br />Personalization and profile mgmt<br />Broker configuration and requirements<br />Pool Vs Persistent desktop decisions<br />Storage configuration (foot print and IO load)<br />WAN and LAN use cases<br />
    27. 27. Hardware Recommendations<br />Smaller servers w/ more cores<br />Good storage controllers<br />More memory<br />Local disk, SSD, centralized disk, centralized SSD<br />Build redundancy through quantity<br />Think back to the old “MetaFrame Days”<br />
    28. 28. So what about Windows 7<br />
    29. 29. Win 7<br />Will change the memory and CPU footprint<br />Face it XP Pro is like a decade old<br />Vendors UNDER SPEC their VMs in scale testing!<br />Storage foot print?<br />WinXP SP3 w/ hot fixes is about 2.8 GB<br />Base Win7…. 10-13GB<br />Lots of talk. Expect ramp ups during PC replacement cycle.<br />Good time to change the environment<br />
    30. 30. Q&AOpen Discussion<br />Ron Oglesby<br /><br />Twitter: @ronoglesby<br />