Redbook - Pano System on Citrix XenDesktop - Pano Logic
Redbook - Pano System on Citrix XenDesktop - Pano Logic
Redbook - Pano System on Citrix XenDesktop - Pano Logic
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DEPLOYING PANO SYSTEM ON CITRIX XENDESKTOP<br />
Given that the storage needs for this size deployment are fairly modest (at 15 - 20 GB per<br />
DVM image), direct-attached storage using enterprise-class drives c<strong>on</strong>figured as a RAID 5<br />
or RAID 6 volume internal to the desktop server may be the most cost-effective approach.<br />
However using this sort of internal server storage, rather than shared storage like a<br />
storage area network (SAN), means that if a user needs to access a specific DVM image<br />
(like a permanently assigned user-based DVM) and the server c<strong>on</strong>taining it is down, the<br />
DVM is effectively inaccessible.<br />
In additi<strong>on</strong> to the risks from internal or direct-attached storage, the processing performed<br />
by a single desktop server also represents a single point of failure – if the server should go<br />
offline, access to all of the DVMs would be interrupted.<br />
Likewise, the infrastructure server represents another single point of failure – if it were to<br />
be offline, user logins would be blocked, although users already c<strong>on</strong>nected to their DVMs<br />
would be able to c<strong>on</strong>tinue working until they needed to log in again or c<strong>on</strong>nect to another<br />
DVM. Both of these availability risks can be mitigated by adding redundant infrastructure<br />
and desktop servers, but the hardware and software costs involved might not be workable<br />
for a deployment of this small size.<br />
Table 3: Summary of Hardware Needed for a Sample 25-Seat Deployment<br />
Comp<strong>on</strong>ent Amount Descripti<strong>on</strong><br />
Desktop Servers 1<br />
Dual, quad-core Intel Westmere CPUs (E5620 or<br />
better), and 32-48 GB of RAM. Server hosts<br />
XenServer or ESX hypervisor software and<br />
Windows DVMs.<br />
Infrastructure<br />
Server<br />
Storage<br />
1<br />
Raw<br />
Capacity:<br />
0.9 TB<br />
Min. IOPS:<br />
1,040<br />
Server hosts <str<strong>on</strong>g>Pano</str<strong>on</strong>g> C<strong>on</strong>troller, <strong>XenDesktop</strong><br />
C<strong>on</strong>troller and supporting XenServer or ESX<br />
hypervisors. Can be hosted <strong>on</strong> the same desktop<br />
server as the DVMs, rather than a separate<br />
server, if user workloads are light. (See the<br />
Deployment Architecture Overview <str<strong>on</strong>g>Redbook</str<strong>on</strong>g> for<br />
informati<strong>on</strong> <strong>on</strong> evaluating user workloads.)<br />
Allows 15 GB per DVM, an average of 1.5 DVMs<br />
per user, plus 50 GB overhead for <str<strong>on</strong>g>Pano</str<strong>on</strong>g><br />
C<strong>on</strong>troller and <strong>XenDesktop</strong> VMs, plus limit of<br />
80% capacity utilizati<strong>on</strong> and less 20% RAID<br />
overhead.<br />
Requires at least six 15K RPM SAS drives or<br />
eight 10K RPM drives, based <strong>on</strong> allocati<strong>on</strong> of 40<br />
IOPS/DVM. Use direct-attached storage internal<br />
to servers rather than a shared SAN/NAS unless<br />
deploying multiple servers for redundancy.<br />
Networking<br />
1 100 Mbps/1 Gbps switch for edge network<br />
1 1 Gbps segment in the core network<br />
Management<br />
Workstati<strong>on</strong><br />
1<br />
Windows workstati<strong>on</strong> needed to c<strong>on</strong>figure and<br />
manage the <str<strong>on</strong>g>Pano</str<strong>on</strong>g> <str<strong>on</strong>g>System</str<strong>on</strong>g> and platform. Also<br />
hosts the Desktop Studio software.<br />
<str<strong>on</strong>g>Pano</str<strong>on</strong>g> <str<strong>on</strong>g>System</str<strong>on</strong>g> C<strong>on</strong>figurati<strong>on</strong><br />
One instance of <str<strong>on</strong>g>Pano</str<strong>on</strong>g> C<strong>on</strong>troller is sufficient for this deployment size, unless you want to<br />
c<strong>on</strong>figure the system for future scalability or current redundancy.<br />
PANO LOGIC: REDBOOK PAGE 8