Hardware VDI vs. Software VDI

3,347 views

Published on

Pros & Cons of Hardware vs. Software VDI

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,347
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
58
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • There are three major sections to the material covered in this presentation: Why customers around the world are rapidly adopting virtualization and VMware. Where do Blade PC’s and Workstation Blades fit into the picture Implementing virtualization and best practices used to ensure success.
  • All remote PC solutions offer: Data security Lower total costs Remote access Better environmentals let’s talk about how are the remote PC solutions different.
  • Desktop virtualization centrally hosts and delivers a cost efficient desktop environment from within the datacenter by consolidating many physical desktops onto a single server.
  • Desktop virtualization – an overview Improves manageability Centralizes resources and control Increases standardization Reduces cost of administration Enables rapid deployment of desktops Increases flexibility Enables pooling and sharing of desktop infrastructure Seamless desktop experience anywhere Simplifies security Centralizes data Centralizes control Let’s first look at the basic definition and key benefits for desktop virtualization. On the right hand side of the slide is a simple graphic showing a server based architecture for desktop virtualization. The solution starts in the data center on HP ProLiant or BladeSystem servers, with option connectivity to a SAN. Installed on the servers is the virtualization software that provides the many to one desktop to server ratio. This includes HP partners such as VMware, MS Virtual Server, and Citrix. Citrix can be either the tradition terminal services environment, or their new desktop broker product (more info in backup materials). MSVS & VMware are virtualization technologies that house guest OS’s & applications in individual virtual machines on the server. The virtual desktops run within the virtualized software on the servers; Windows XP, for example. Many customers choose to incorporate into the solution a utility which connects clients to the centrally located servers/blade PC’s & data. We’ll talk more about the different solutions and desktop environments, but often customers serve multiple end user environments with multiple virtual desktop infrastructures. The connection manager helps connect the appropriate desktop user to the appropriate hardware and virtualization software solution on the back end. Next a remote protocol is required to interface over the network between the client devices and the servers in the datacenter. MS RDP, Remote Desktop Protocol, is commonly used.
  • User profile and data Enables VMotion
  • Server selection: Number of cores Number of processors Memory expansion for the price AMD vs Intel Blades vs DL User types: Task worker Knowledge worker Heavy user Specialty users: financial traders, engineering workstations, graphics rendering
  • Let’s take a look at the issues that are behind the need for desktop virtualization: This slide only begins to capture the various issues facing IT administrators today Heterogeneous hardware on the desktop requires multiple PC images for each machine High management cost due to labor intensive technical support and administrative inefficiencies. Instead of focusing on new or strategic projects, IT spends time on trivial tasks like resetting passwords or hardware maintenance Of course, security is one of the main issues facing IT today, and constant upgrading and patching of a decentralized workforce makes maintaining a security even more complicated. Enterprise PCs are considered one of the most underutilized IT asset today
  • Hardware VDI vs. Software VDI

    1. 1. Session Title: Hypervisor-based VDI versus blade PCs: What's the real performance and cost difference? Glenda Canfield
    2. 2. Agenda <ul><li>Why virtual desktop infrastructure (vdi)? </li></ul><ul><li>What is vdi? </li></ul><ul><li>HP’s vdi implementation </li></ul><ul><li>What are Blade PC’s / Consolidated Client Infrastructure </li></ul><ul><li>What’s the difference in Administrative Overhead & Cost </li></ul><ul><li>Key points to take away </li></ul>
    3. 3. Remote/Consolidated PC Address Critical Business IT Issues: Improves data security and privacy Centralizes management for lower costs Lowers power and cooling costs Enables IT to address business opportunities Unburden IT: A fundamental shift in how IT manages end-user computing Applies datacenter practices and resources for end-users computing End users continue to have traditional, personalized desktop look-and-feel Remote PC’s
    4. 4. Distributed vs. Remote PCs What is the difference? Personal Computer Windows OS Applications Thin Client RDP/RGS HP Session Allocation Mgr Blade PC Windows OS Applications Thin Clients RDP/ICA Citrix or Terminal Services Application Server Application Server OS Terminal Server/Citrix Multiple users accessing applications per server HP VDI Multiple users accessing virtual PC’s per server HP CCI Single user per Blade PC <ul><li>Distributed PC </li></ul><ul><li>Single user per Desktop PC </li></ul>Current Paradigm Performance Standard Most Flexible Remote PC
    5. 5. Challenges of Desktop Management <ul><li>Remote location </li></ul><ul><ul><li>Little IT Skills locally </li></ul></ul><ul><li>Distributed workforce </li></ul><ul><ul><li>Guest workers and telecommuters </li></ul></ul><ul><ul><li>Off-shoring and outsourcing of business functions </li></ul></ul><ul><li>Complex hardware management </li></ul><ul><ul><li>Multiple makes and models </li></ul></ul><ul><ul><li>Unending hardware upgrade cycles </li></ul></ul><ul><li>Rising cost of PC Management </li></ul><ul><ul><li>OS and application deployment </li></ul></ul><ul><ul><li>Backup and recovery </li></ul></ul><ul><li>Limited control of PCs </li></ul><ul><ul><li>Security of sensitive data </li></ul></ul><ul><ul><li>Compliance with regulations (SOX, HIPPA) </li></ul></ul>
    6. 6. VDI <ul><li>Data security </li></ul><ul><li>corporate security initiatives and legally mandated regulatory compliance </li></ul><ul><li>Ease & control of centralized management </li></ul><ul><li>rising apex associated with upgrading and patching older desktops </li></ul><ul><li>Impact of dual/quad core processors </li></ul><ul><li>dramatically lowers cost per seat </li></ul><ul><li>Broader user base </li></ul><ul><li>Virtualization technology provides a customized virtual desktop experience for the user </li></ul><ul><li>Application compatibility in virtual environment </li></ul><ul><li>Virtualization-savvy customer </li></ul><ul><li>Customer have experience running virtualization software </li></ul>
    7. 7. Desktop virtualization – an overview VM SAN SAN Desktop HP Thin Client PDA VM VM VM VM VM VM VM Connection Broker Request Data Center Internet or LAN/WAN VMware ESX VMware ESX
    8. 8. Desktop Virtualization - Overview <ul><li>Desktop virtualization – an overview </li></ul><ul><li>Improves manageability </li></ul><ul><ul><li>Centralizes resources and control </li></ul></ul><ul><ul><li>Increases standardization </li></ul></ul><ul><ul><li>Reduces cost of administration </li></ul></ul><ul><ul><li>Enables rapid deployment of desktops </li></ul></ul><ul><li>Increases flexibility </li></ul><ul><ul><li>Enables pooling and sharing of desktop infrastructure </li></ul></ul><ul><ul><li>Seamless desktop experience anywhere </li></ul></ul><ul><li>Simplifies security </li></ul><ul><ul><li>Centralizes data </li></ul></ul><ul><ul><li>Centralizes control </li></ul></ul>
    9. 9. VDI Components
    10. 10. VDI Scenario’s <ul><li>Two basic implementation’s </li></ul><ul><li>Static </li></ul><ul><li>1:1 Every user assigned a VM / Blade PC connects by it’s IP address or name </li></ul><ul><li>Dynamic </li></ul><ul><li>Connection broker connects user to a VM / Blade PC in a pool and returns VM / Blade PC to pool when the user disconnects </li></ul>
    11. 11. <ul><li>Core requirements </li></ul><ul><ul><li>Virtualization technology </li></ul></ul><ul><ul><li>Remote protocol </li></ul></ul><ul><ul><li>Desktop OS and applications </li></ul></ul><ul><li>Optional components </li></ul><ul><ul><li>Connection manager </li></ul></ul><ul><li>Providers </li></ul><ul><ul><li>VMware </li></ul></ul><ul><ul><ul><li>VDI & ESX </li></ul></ul></ul><ul><ul><li>Microsoft </li></ul></ul><ul><ul><ul><li>Guest OS, MS V - Motion, RDP, </li></ul></ul></ul><ul><ul><ul><li>and Softricity </li></ul></ul></ul><ul><ul><li>Citrix </li></ul></ul><ul><ul><ul><li>Presentation Server </li></ul></ul></ul><ul><ul><ul><li>XenSource Server </li></ul></ul></ul><ul><ul><ul><li>XenDesktop Broker </li></ul></ul></ul>Software
    12. 12. Servers for VDI <ul><ul><li>Any server on the VMware HCL </li></ul></ul><ul><ul><li>Works with Microsoft Virtual Server </li></ul></ul><ul><ul><li>Some are more favored than others </li></ul></ul><ul><ul><ul><li>Excellent for blades </li></ul></ul></ul><ul><ul><ul><li>Traditional VMware best sellers </li></ul></ul></ul>
    13. 13. VDI User Density
    14. 14. Storage <ul><ul><li>Tremendous storage opportunity </li></ul></ul><ul><ul><li>Storage is the backbone of VDI solutions </li></ul></ul><ul><ul><li>Careful planning is imperative </li></ul></ul><ul><ul><ul><li>How much space per user </li></ul></ul></ul><ul><ul><ul><li>Investment matches the importance of the data </li></ul></ul></ul><ul><ul><ul><li>Architecture does not have to be “user data on VM” so variety of storage may be needed </li></ul></ul></ul>
    15. 15. Sizing considerations <ul><li>Sizing must account for </li></ul><ul><ul><li>Number and type of users on the system </li></ul></ul><ul><ul><li>Disk/storage controllers </li></ul></ul><ul><ul><li>Memory resources </li></ul></ul><ul><ul><li>Network sizing and latency </li></ul></ul><ul><ul><ul><li>Data redirection </li></ul></ul></ul><ul><ul><ul><li>Printing </li></ul></ul></ul><ul><ul><ul><li>Local device redirection </li></ul></ul></ul><ul><ul><ul><li>Remote desktop protocol </li></ul></ul></ul><ul><ul><li>Server selection vs. Blade PC’s vs. Workstation Blades </li></ul></ul>
    16. 16. CCI / Blade PC’s <ul><li>What are they? </li></ul><ul><li>How are they Managed? </li></ul><ul><li>What’s the use case? </li></ul><ul><li>How much do they cost? </li></ul>
    17. 17. What is CCI/Blade PC’s <ul><li>Created by the Industry Standard Server Team @ HP </li></ul><ul><li>Splintered Off – to become CCI </li></ul><ul><li>Essentially they are Server Blades with far less power and less manageability </li></ul>
    18. 18. How are they managed <ul><li>They have an AI that is used for management </li></ul><ul><li>No ILO Support </li></ul>
    19. 19. What’s the Use Case for Blade PC’s <ul><li>Each user gets their own Hardware Resource </li></ul><ul><li>They have GPU’s in them (most servers do NOT) </li></ul><ul><li>Even if the server had a GPU in it in a Hypervisor Scenario Today you cannot leverage it because of I/O issues </li></ul>
    20. 20. How do they scale <ul><li>Very easy to scale – Each user gets their own blade </li></ul><ul><li>They have less single points of failure than “traditional” VDI </li></ul><ul><li>VMWare /XenSource are complex to scale compared to Blade PC’s </li></ul>
    21. 21. Capacity & Scalability: Machine Density <ul><li>Background </li></ul><ul><li>VMware ESX architecture combined with the demands of a remote desktop computing VM place practical limitations on the number of VMs per physical host </li></ul><ul><ul><li># of VMs per processor core </li></ul></ul><ul><ul><li>memory needs of VMs vs. amount of memory in the host server </li></ul></ul><ul><ul><li>host server subsystems technology (storage, memory, CPU, etc.) </li></ul></ul><ul><li>General Guidelines (actuals vary by implementation) </li></ul><ul><ul><li>sweet spot seems to be 6 VMs per processor core </li></ul></ul><ul><ul><ul><li>lower for heavier loads, higher (maximum 10) for light loads </li></ul></ul></ul><ul><ul><li>consensus seems to be no more than 25% memory over commitment </li></ul></ul><ul><li>Complementary technology </li></ul><ul><ul><li>higher speed CPUs </li></ul></ul><ul><ul><li>more (and faster) memory </li></ul></ul><ul><ul><li>faster storage subsystems </li></ul></ul><ul><ul><li>VMware resource management </li></ul></ul><ul><li>Alternate technology </li></ul><ul><ul><li>HP blade PCs provide a consistent / fixed base for capacity planning </li></ul></ul><ul><ul><li>HP blade PCs provide performance consistent with dedicated hardware </li></ul></ul>Density in a virtualized environment is limited by practical considerations. Driving Factors What density level will meet user performance targets? Evaluation Criteria
    22. 22. Capacity and Scalability: Storage <ul><li>Background </li></ul><ul><li>Carefully size storage as high VM density can require complex configurations as each VM has it’s own storage requirement for the OS, image, applications, etc… </li></ul><ul><li>Incorrect / insufficient storage configuration can result in a direct impact to VDI end users </li></ul><ul><ul><li>VMs and their host servers can be affected by storage bottlenecks </li></ul></ul><ul><li>Tiered storage is one recommendation </li></ul><ul><ul><li>Local storage for ESX boot </li></ul></ul><ul><ul><li>SAN for VMs (iSCSI for low performance / kiosk VMs) </li></ul></ul><ul><ul><li>NAS for redirected user data </li></ul></ul><ul><ul><li>Separate file system (SAN or local) for redirected kernel swap files </li></ul></ul><ul><li>General guidelines </li></ul><ul><li>Limits have been presented by HP and VMWare for configuring SAN storage in a VDI environment </li></ul><ul><ul><li>Best practice is 10 - 20 VMs per LUN (30 maximum) </li></ul></ul><ul><ul><li>100 - 200GB per LUN </li></ul></ul><ul><li>Complementary technology </li></ul><ul><ul><li>HP storage products (SAN, NAS, iSCSI, direct attach) </li></ul></ul><ul><ul><li>HP storage virtualization </li></ul></ul><ul><ul><li>shared storage / streaming for OS and applications </li></ul></ul><ul><li>Alternate technology </li></ul><ul><ul><li>HP blade PCs can utilize either existing local blade PC hard drive or redirected to network storage </li></ul></ul>Density in a virtualized environment present unique challenges to a data center architecture. Driving Factors What storage configuration meets both desired user performance targets and business (e.g. cost) needs? Evaluation Criteria
    23. 23. Performance CPU <ul><li>Background </li></ul><ul><li>VMWare identifies VDI system loads as “highly interactive” environments bound by the limits of the vCPU </li></ul><ul><ul><li>vCPU utilization can be high (up to 100%) and uneven with large / frequent fluctuations </li></ul></ul><ul><li>In general, CPU-bound environments present a higher vCPU virtualization overhead </li></ul><ul><ul><li>VMware scheduler must schedule vCPU execution when resource is available on a physical CPU </li></ul></ul><ul><ul><ul><li>If no resources are available, the machine is left in a “ready” state during which all VM operation is suspended (ready states can range from very minimal to significant) </li></ul></ul></ul><ul><ul><ul><li>CPU resource control (such as reservations and limits) can result in an increase in ready time </li></ul></ul></ul><ul><ul><ul><li>vSMP scheduling in a VDI environment can result in significant scheduling issues </li></ul></ul></ul><ul><li>General guidelines (actuals vary widely by implementation) </li></ul><ul><ul><li>Size VM density accordingly (start small, then increase incrementally) </li></ul></ul><ul><ul><li>Avoid the use of vSMP in a VDI environment </li></ul></ul><ul><ul><li>Monitor key CPU and vCPU performance statistics </li></ul></ul><ul><ul><li>Carefully examine, plan, and gradually implement the use of resource management </li></ul></ul><ul><ul><li>Carefully adjust server specific CPU tuning settings </li></ul></ul><ul><li>Complementary technology </li></ul><ul><ul><li>faster CPUs with more physical cores </li></ul></ul><ul><li>Alternate technology </li></ul><ul><ul><li>HP blade PCs provide dedicated CPU resource for each blade </li></ul></ul>
    24. 24. How Much do they cost <ul><li>1500-2000 per blade not including the enclosure </li></ul>
    25. 25. Categories of Evaluation Metrics Quantitative
    26. 26. What are Workstation Blades
    27. 27. Whats the use case
    28. 28. How do they scale
    29. 29. How much do they cost
    30. 30. Basic Connection Broker Function <ul><ul><li>Client sends a connection request to the connection broker. Some connection brokers offer a specific client to facilitate the connection and most provide the option to connect using a Browser, </li></ul></ul><ul><ul><li>The Connection broker validates the user name. </li></ul></ul><ul><ul><li>Most connection brokers provide the ability for the user to access multiple VM Pools. If the user is permitted to access pools they are prompted with the pool they wish to connect to. </li></ul></ul><ul><ul><li>The connection broker then provides a RDP connection to an available Virtual machine in the pool. </li></ul></ul><ul><ul><li>The Client Connects to the assigned VM </li></ul></ul><ul><ul><li>The Connection Broker is then updated with the machines current status – Active </li></ul></ul><ul><ul><li>When user disconnects the connection broker then makes the virtual machine available to another user. </li></ul></ul>
    31. 31. Protocols <ul><li>Can’t talk about VDI without going through the different protocols </li></ul><ul><li>RGS </li></ul><ul><li>ICA </li></ul><ul><li>RDP </li></ul>
    32. 32. The need for desktop virtualization Heterogeneity High Management Costs Admin Inefficiencies > 70% of TCO ($6,800* / user/ year) ) *Gartner Too tactically focused Low Resource Utilization The desktop is the least utilized resource on the network! Security Threats Data Theft Virus / Malware Phishing Hacking Need for preventive/ proactive measures
    33. 33. What is the best option for you <ul><li>Depends on your end goal </li></ul>
    34. 34. Summary Key Points
    35. 35. Questions?

    ×