IP Expo 2009 - How To Build scalable Environments Today - Wednesday 7th October - 14.30 - 15.00


Published on

Desktop Virtualisation has rapidly become a viable solution for office and remote workers. Attend this session to learn more about the technology behind
desktop virtualisation and how it allows you to build a scalable desktop infrastructure and deliver a rich end-user experience.

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

IP Expo 2009 - How To Build scalable Environments Today - Wednesday 7th October - 14.30 - 15.00

  1. 1. Desktop virtualisation – how to build scalable environments today<br />Toby Coleridge, Systems Engineer<br />Citrix Systems<br />
  2. 2. Agenda<br />Architectural Overview<br />Scalability Considerations and Results<br />Sizing and Design<br />High Availability<br />
  3. 3. Architectural Overview<br />
  4. 4. Desktop Delivery Components: VirtualDesktops<br />Scalability Focus<br />Desktop Delivery Controller<br />2<br />Operating Systems, Apps, and user Profiles are provisioned on demand<br />1<br />Users login and request their desktop<br />User Settings<br />Apps<br />User Profiles<br />App Delivery<br />3<br />Users desktop is delivered <br />OS<br />Users<br />Desktop Provisioning<br />Virtual Desktop<br />Virtual DesktopHosting Infrastructure<br />(XenServer, Hyper-v, ESX)<br />Provisioning Server<br />
  5. 5. Making Connections<br />Desktop Delivery Controller<br />Domain Controller<br />2. find “best” virtual desktop<br />7. acquire license and determine policies<br />ADOU<br />3. start VM<br />9. apply profile<br />1. authenticate <br />Portable Profiles<br />5. register<br />Scalability Considerations and Results<br />XenApp<br />10. deliver apps<br />6. connect using ICA<br />8. login<br />Provisioning Server<br />LAN Connected UsersDesktop Appliances<br />Xen, Hyper-V, VM<br />4. PXE-boot VM andstream OS<br />Full range of authentication methods supported through web interface technology<br />Full support for SmartAccess and ICA session policies<br />SAN<br />Data Center<br />
  6. 6. Demonstration<br />
  7. 7. Scalability Considerations and Results<br />
  8. 8. XenDesktop Component Versions<br />XD3 FP1<br />
  9. 9. Scalability Metrics Definition<br />
  10. 10. Methodology<br />The results are based on Citrix proprietary methodology measuring scalability while preserving a great user experience. These numbers cannot be compared with 3rd-party claims.<br /><ul><li>Aggressive workload (more than real-life):
  11. 11. Mainstream office worker:
  12. 12. Office 2007: Outlook (~1257KB pst file), Word (2 ~265KB files), IE7 (2 tabs w. Flash content), Excel (~1325KB file), Acrobat Reader, Powerpoint (~1195KB file)
  13. 13. High-rate of user actions:
  14. 14. Script runs in 18 minute intervals, for 60 minutes (a doc opened and closed every 2min)
  15. 15. Logon Storm (9am scenario):
  16. 16. Sessions launched at a rate of 5 sessions/sec, spread over 100 hosts (4,500 logons in 15min)</li></li></ul><li>Desktop Delivery ControllerScalability Metrics<br />Metric 1: Connection Rate<br />Represents a brokered connection<br />Sustained rate of desktop connections?<br />1<br />Desktop Delivery Controller<br />Metric 2: Desktop Heartbeat<br />Ongoing heartbeat load is very light<br />2<br />1<br />1<br />2<br />Users<br />Virtual Desktop Infrastructure<br />XenServer<br />XenServer<br />Hypervisor<br />
  17. 17. Desktop Delivery Controller 3.0Measured Scalability <br />All figures derived from Citrix proprietary methodology - provided for sizing guidance only, NOT suitable for comparative purposes<br />Notes:<br />* Peak CPU utilization at 60%<br /><ul><li>Hardware – Dual quad core, 1.8 GHz, 16 GB RAM
  18. 18. 2 GB RAM sufficient as RAM is not a limiting factor</li></li></ul><li>Desktop Delivery ControllerBest Practices<br />1<br />Desktop Delivery Controller<br />Best Practice: <br />‘Scale up’ the delivery controller to address ‘9am scenario’ <br /><ul><li>Single server
  19. 19. Faster processor
  20. 20. More cores</li></ul>Best Practice: <br />‘Scale out’ the delivery controller to address heartbeats<br /><ul><li>Add more servers </li></ul>2<br />Users<br />Virtual Desktop Infrastructure<br />XenServer<br />XenServer<br />Hypervisor<br />
  21. 21. XenServerScalability Metrics <br />Desktop Delivery Controller<br />Metric 1: Single Server Density<br />Stack represents a desktop<br />How many desktops on a single server?<br />Users<br />Metric 4: ICA bandwidth<br />Line represents an ICA session<br />How much bandwidth per desktop?<br />Metric 3: IOPS/desktop<br />Yellow represents streamed image<br />How many IOPS/desktop?<br />Resource Pool<br />Metric 2: # of Hosts/Resource Pool<br />Each box represents a virtualized host<br />How many desktops/resource pool?<br />Virtual Desktop Infrastructure<br />XenServer<br />XenServer<br />XenServer<br />
  22. 22. XenServer 5.0MeasuredScalability<br />HP Blade Server BL460<br />All figures derived from Citrix proprietary methodology - provided for sizing guidance only, NOT suitable for comparative purposes<br />Notes:<br /><ul><li>Tests run as of April 2009
  23. 23. Tests run with WinXP; 512 MB of memory allocated per VM, aggregated 8Gbps of network bandwidth / host
  24. 24. No Dedicated Pool Master required as of XenServer 5.0
  25. 25. RAM-bound for these hardware specs – other bottlenecks expected (CPU, network) as RAM is added</li></li></ul><li>XenServerBest Practices<br />Desktop Delivery Controller<br />Users<br />Best Practice: Separate VM boots from Logons<br />Use Idle Pool Settings<br /><ul><li>Pre-launches desktops
  26. 26. Spread out desktop launches
  27. 27. Faster desktop start-up times for users
  28. 28. Save energy/cost via timed shutdown</li></ul>1<br />Virtual Desktop Infrastructure<br />XenServer<br />XenServer<br />XenServer<br />
  29. 29. Provisioning ServerScalability Metrics<br />Metric: Provisioning Server Density<br />No of target devices (virtual desktops)<br />How many desktops per Provisioning Server?<br />Desktop Delivery Controller<br />Hosted Desktop Streaming<br />PC<br />Users<br />PXE-boot VM and stream OS<br />OS<br />Local Desktop Streaming<br />Provisioning Server<br />Virtual Desktop Infrastructure<br />XenServer<br />XenServer<br />Hypervisor<br />
  30. 30. Provisioning Server 5.0Measured Scalability<br />All figures derived from Citrix proprietary methodology - provided for sizing guidance only, NOT suitable for comparative purposes<br />Notes:<br />1Running on Windows Server 2008 64bit (for enhanced caching capability)<br />2 Write-back cache on local VM storage (ie. on shared storage)<br />3 Lack of separation of bootupvs logon events impacts concurrency. Also, diskless-endpoints require handling of write-back cache through PvS server<br /><ul><li>Hardware – Dual quad core, 2.3 GHz, 8 GB RAM, dual 1Ge NICs
  31. 31. Network throughput generally the bottleneck - RAM and CPU not limiting factors </li></li></ul><li>Provisioning ServerBest Practices<br />3<br />Desktop Delivery Controller<br />Best Practice: vDisk Placement<br /><ul><li>Store on LUN for backup & recovery
  32. 32. Cache locally on Provisioning Server for better performance (run on 64bit OS)</li></ul>Best Practice: Cluster Provisioning Servers for:<br /><ul><li>Load balancing</li></ul>2<br />vDisk<br />OS<br />OS<br />OS<br />PXE-boot VM and stream OS<br />Users<br />Best Practice: Proximity to hypervisor for:<br /><ul><li>Improved bandwidth
  33. 33. Effective NIC-teaming</li></ul>1<br />SAN<br />NAS<br />Best Practice: Write Cache Placement:<br /><ul><li>Store on XenServer guest VM via a LUN
  34. 34. Supports XenMotion and HA</li></ul>4<br />Virtual Desktop Infrastructure<br />XenServer<br />XenServer<br />Hypervisor<br />
  35. 35. Storage Considerations<br />Sizing can be done by I/O or Capacity<br />Storage can severely impact performance<br />Disk technologies and considerations<br />
  36. 36. Sizing and Design<br />
  37. 37. Sizing Based on User Types<br />Office user<br />Only using one-two application(s) at a time<br />Idle time<br />Lower memory and CPU requirements<br />Power user<br />Using multiple applications at a time<br />Consumes more processor and memory of the VM<br />Environment Assessment<br />Identify your user groups<br />Categorize based on usage habits<br />Helps align hardware requirements with user needs<br />
  38. 38. Sizing Based on Applications<br />Online (fka Hosted)<br />Applications run remotely on a XenApp server<br />Application processing occurs on XenApp server<br />Running multiple applications has little impact on virtual desktop utilization<br />Offline (fka Streamed)<br />Applications streamed to the virtual desktop upon request<br />Processing occurs on the virtual desktop<br />Slightly higher utilization when compared to installed applications<br />Installed<br />Applications part of the virtual desktop OS build<br />Processing occurs on the virtual desktop<br />May drive the need for multiple vDisks<br />For best practices on selecting app delivery model, see “XenDesktop – Design Handbook” available at http://support.citrix.com.article/ctx120760<br />
  39. 39. Pooled Desktops: Storage Efficiencies<br />Stack for every user<br />Desktops assembled on-demand<br />Network Storage<br />Network Storage<br />Hypervisor<br />Xen, Hyper-V, VM, Blades<br />VDI without XenDesktop<br /><ul><li>Single image for every desktop
  40. 40. Apps installed in VM
  41. 41. Apps execute in VM
  42. 42. Desktops managed individually
  43. 43. Single infrastructure choice
  44. 44. Same problems, in a new location</li></ul>VDI with XenDesktop<br /><ul><li>Single shared OS image to store & maintain
  45. 45. Central single App set to store & maintain
  46. 46. Apps can execute centrally or in VM
  47. 47. Profiles managed centrally – consistent UX
  48. 48. Open - supports most standard infrastructure
  49. 49. Lower TCO</li></li></ul><li>High Availability<br />
  50. 50. Overcoming Failures<br />XenServer 5.0<br /><ul><li>If the hypervisor fails</li></ul>VM<br />VM<br />VM<br />VM<br />XenServer Resource Pool<br />Hypervisor server fails<br />Virtual machines are restarted to available hypervisor <br />XenServer #1<br />XenServer #2<br />Virtual machines moved back when hypervisor restored<br />
  51. 51. Overcoming Failures<br />Desktop Delivery Controller 3.0<br /><ul><li>Multiple XenDesktop controllers within the farm</li></ul>VM<br />VM<br />VM<br />VM<br />XenDesktop Farm<br />Virtual desktops periodically “ping” their controller<br />If a Controller goes offline<br />Virtual desktops re-register to new controllers<br />
  52. 52. Overcoming Failures<br />Provisioning Server 5.0<br /><ul><li>Multiple Provisioning Servers within the environment
  53. 53. Shared enterprise storage hosts golden desktop image(s)</li></ul>VM<br />VM<br />VM<br />VM<br />Storage<br />Provisioning Server Farm<br />Virtual desktops continuously receive operating system stream<br />If Provisioning Server taken offline<br />Virtual desktops re-acquire stream by contacting other Provisioning Servers<br />
  54. 54. Overcoming Failures<br />XenDesktop – End-to-End High-Availability Solution<br />
  55. 55. Questions?<br />