Redbook - Pano System on Citrix XenDesktop - Pano Logic

More documents

Recommendations

Info

NetScaler 10 Gbps SAN Backbone SAN Array RAID RAID SAN Array RAID RAID SAN Array RAID RAID DEPLOYING PANO SYSTEM ON CITRIX XENDESKTOP 1,000-SEAT DEPLOYMENT Figure 5: Sample architecture for a 1,000-seat deployment on Citrix XenDesktop Users' Location 1,000 <strong>Pano</strong> Zero Clients This section provides information on sample architectures for 1,000-seat <strong>Pano</strong> <strong>System</strong> deployments on Citrix XenDesktop. DHCP Domain Servers Directory Services 2–4 Infrastructure Servers XenDesktop Controller Provisioning Server Machine Creation Services (XD5, optional) Citrix Provisioning Services (optional) Data Center 100 Mbps LAN 100 Mbps / 1 Gbps Edge Switches 1 Gbps Edge Network <strong>Pano</strong> Controller <strong>Pano</strong> Controller XenDesktop Controller <strong>Pano</strong> Maestro 1 Gbps Core Network <strong>Pano</strong> Controller Scalability Group XenServer/ESX Hypervisor Core Switch 30–40 Desktop Servers Windows XP/7 DVMs <strong>Pano</strong> Direct Service XenDesktop VDA XenServer Tools XenServer/ESX Hypervisor Management Workstation Hardware Sizing and Architecture For a 1,000-seat deployment, typically at least 30 to 40 desktop servers, depending on user workloads, will be needed to host the DVMs (see the Deployment Architecture Overview <strong>Redbook</strong> for information on evaluating user workloads). Two to four infrastructure servers are also required. Shared storage in the form of a SAN or NAS is typically essential for deployments of this size. Shared storage is needed to ensure that DVM images remain available in the event of a desktop server failure – something which is much more likely with up to 40 servers. It is also typically required to provide the high level of IOPS (30,000 to 50,000) needed for up to 1,000 active DVMs. <strong>Pano</strong> <strong>System</strong> Configuration Because we’re deploying over 500 seats, we are required to use a <strong>Pano</strong> Controller group that combines at least two <strong>Pano</strong> Controller instances to provide scalability in a master/slave configuration. If we also want to provide redundancy or failover capabilities in the event of server hardware or software failure, two <strong>Pano</strong> Controller instances need to be installed on two different physical servers and configured as primary (active) and secondary (passive), and a third <strong>Pano</strong> Controller instance would be added and configured as a slave. PANO LOGIC: REDBOOK PAGE 10
DEPLOYING PANO SYSTEM ON CITRIX XENDESKTOP Table 7: Summary of Hardware Needed for a Sample 1,000-Seat Deployment Component Amount Description Desktop Servers 30-40 Each with dual, quad-core Intel Westmere CPUs (E5620 or better) and 48-72 GB of RAM. Servers host XenServer or ESX hypervisor software and Windows DVMs. Infrastructure Servers Storage 2-4 Raw Capacity: 33 TB Min. IOPS: 40,000 Deploy multiple <strong>Pano</strong> Controller instances in a <strong>Pano</strong> Controller group for scalability. Infrastructure servers host <strong>Pano</strong> Controller, XenDesktop Controller, the required supporting XenServer or ESX hypervisor and, optionally, Citrix Provisioning Services and NetScaler VPX. Allows 15 GB per DVM, an average of 1.5 DVMs per user, plus 50 GB overhead for <strong>Pano</strong> Controller and XenDesktop VMs, with a limit of 80% capacity utilization and less the 20% RAID overhead. Requires SAN/NAS with at least 221 15K RPM SAS drives or 285 10K RPM drives, based on an allocation of 40 IOPS/DVM. Networking 6-7 100 Mbps/1 Gbps switches for edge networks 4-6 1 Gbps segments for the core network Management Workstation 1 Windows workstation is required to configure and manage the <strong>Pano</strong> <strong>System</strong> and platform. Also hosts the Desktop Studio software. In this configuration, all three instances of <strong>Pano</strong> Controller belong to the same <strong>Pano</strong> Controller group and integration with XenDesktop Controller is made highly available by implementing an active/passive, two-node failover cluster using the two <strong>Pano</strong> Controller instances. <strong>Pano</strong> Controller is responsible for the initial connection to <strong>Pano</strong> Zero Clients and the display of login screens on the clients. Platform Considerations and Configuration This section discusses Citrix-specific factors that you should consider for 1,000-seat deployments. Creating DVM Templates You can optionally deploy Citrix Provisioning Services alongside Machine Creation Services to enables you to use a single DVM image template to create multiple DVM images on one or more desktop servers. This can greatly reduce the amount of storage required compared to other methods of creating DVM images and is typically most useful in deployments with 1,000 or more DVMs. PANO LOGIC: REDBOOK PAGE 11
Page 1 and 2: TABLE OF CONTENTS XenDesktop Compon
Page 3 and 4: DEPLOYING PANO SYSTEM ON CITRIX XEN
Page 9: DEPLOYING PANO SYSTEM ON CITRIX XEN
Page 13 and 14: NetScaler 10 Gbps SAN Backbone SAN

Redbook - Pano System on Citrix XenDesktop - Pano Logic

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?