Your SlideShare is downloading. ×
  • Like

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

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

  • 840 views
Published

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 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
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
840
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
29
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

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