Horizon 7 Sizing and Consumption Model : 7.4 Sizing Conclusion
   
7.4 Sizing Conclusion
This tenant sizing scenario is based on a small deployment of 100 desktop sessions with an expected user session concurrency of 60%. This is a single use-case which is common for a Proof-of-Concept (PoC) with a tenant. Using the sizing and blueprint information in the previous sections, we can now calculate a single tenant deployment based on a shared management block.
To aid with sizing of any Horizon, it is recommended that the VMware Horizon Sizing Estimator is used. The Horizon Sizing Estimator will guide the user through each step of an enterprise deployment with Horizon 7, along with architectural guidelines and recommendations. This is currently available to VMware partners and employees (see the link in Section 10, References).
Table 14. Tenant Use-Case 1 - Engineering PoC
Question
Answer
Design Outcome
Non-core applications
Yes
Applications that are not part of the base-image. App Volumes required.
User-installed applications?
Yes
App Volumes Writable Volumes required or Full Clone Desktops.
Non-core application disk space required (GB)
2GB
Capacity required for App Volumes AppStack.
User-installed application disk space required (GB)
4GB
Capacity required for App Volumes writable volume.
Access to local client drive?
No
Client Drive Redirection not required.
Access to locally attached USB drive?
No
No USB redirection required.
Access to locally attached printer?
Yes
Virtual printing requirement.
User Concurrency
60%
Expected concurrent average user connections.
60 users.
 
Table 15. Use-Case 1 - Recovery Specifications
Specification
Value
Description
Secondary Pod (Cloud Pod Architecture)
No
Secondary Pod can be used for disaster recovery. Not required for PoC.
 
Note Security and Management specifications not specified for this PoC use-case.
In this example (Tenant use-case 1), 4 hosts will be used in the resource block as illustrated in the following figure. This will allow for sufficient capacity during a host failure in addition to a host being taken offline for maintenance.
Figure 19. Tenant Resource Block Example
C:\Users\ray\AppData\Local\Microsoft\Windows\INetCacheContent.Word\Resource Blueprint 1.png
 
A shared management block has been selected, with the following tenant management components:
Table 16: Tenant Management Components
Component
Qty.
Description
vCenter Server Appliance
2
A pair of vCenter Server appliances (vCenter HA) will be used for the tenant resource block. Tenant administrators will have access for the management of desktop images and vSphere operations.
Access Point
2
A pair of Access Point virtual appliances will be deployed behind an NSX load-balancer. This will be used for resilience and facilitate external (internet) access.
Connection Server
2
Two Horizon View Connection Servers will be deployed for resilience.
NSX Manager
2
Two NSX Manager virtual appliances are deployed for management of the resource cluster networking.
vRealize Operations for Horizon
2
A single vRealize Operations Manager server will be deployed with the Horizon adapter. This will be used for tenant monitoring of the environment.
Identity Manager
3
Three VMware Identity Manager appliances will be deployed for access to Workspace ONE.
Enrollment Servers
2
Two Enrollment Servers will be deployed for True SSO.
User Environment Manager
1*
A single file server will be deployed for User Environment Manager.
* Where a single User Environment Manager file server is deployed, in this example it is not considered critical to operations. For high availability of the User Environment Manager file shares, Microsoft DFS-R (replication) can be used in a hub and spoke replication topology (active-active replication is not supported).