This section lays out the network architecture at a high level with some common deployment examples to help you scale Horizon on Azure VMware Solution. Network connectivity to scale Horizon on Azure VMware Solution The following diagram shows a basic Horizon pod deployment. The connection from Azure Virtual Network to the Azure private clouds / SDDCs should be configured with ExpressRoute FastPath. In turn, maximizing the scalability of Horizon running on Azure VMware Solution. It effectively turns each Azure private cloud and SDDC into a block. Given the Azure private cloud and SDDC max limit, we recommend a deployment architecture where the Horizon Connection Servers and VMware Unified Access Gateways (UAGs) are running inside the Azure Virtual Network. For more information, see the sizing guidelines in the Size Azure VMware Solution hosts for Horizon deployments section. Size and plan your deployment accordingly. User Data volumes may lower scale limits in the context of your workload. Your workload profile and needs may be different, and therefore results may vary based on your use case. Only protocol traffic is considered, no user data. The workload traffic aligns with the LoginVSI task worker profile. Combined with VMware SDDC networking / NSX-T Data Center, the Azure VMware Solution network connectivity presents unique requirements for deploying Horizon that is different from on-premises.Įach Azure private cloud and SDDC can handle 4,000 desktop or application sessions, assuming: Each Horizon pod has a separate management portal, and so a standard design practice is to minimize the number of pods.Įvery cloud has its own network connectivity scheme. A Horizon pod is a unit of organization determined by Horizon scalability limits.
A block is a single vCenter Server, while multiple blocks combined make a pod. Horizon on Azure VMware Solution deployment architectureĪ typical Horizon architecture design uses a pod and block strategy. For more information, see Expanding Existing Horizon 7 Environments.Īzure VMware Solution automatically configures specific Horizon settings as long as you deploy Horizon 2006 (aka Horizon 8) and above on the Horizon 8 branch and select the Azure option in the Horizon Connection Server installer. CPA scales up your deployment, builds a hybrid cloud, and provides redundancy for Business Continuity and Disaster Recovery. You can deploy Horizon in a hybrid cloud environment by using Horizon Cloud Pod Architecture (CPA) to interconnect on-premises and Azure data centers. For more information, see feature parity and interoperability. Other products in the Horizon ecosystem are also supported. There are a few Horizon features that are supported on-premises but not on Azure VMware Solution. Horizon 2006 and later versions on the Horizon 8 release line supports both on-premises and Azure VMware Solution deployment. The following diagram summarizes the key differences at a high level. With Horizon's introduction on Azure VMware Solution, there are now two Virtual Desktop Infrastructure (VDI) solutions on the Azure platform. For general information on VMware Horizon, refer to the Horizon production documentation: Here, we focus specifically on deploying Horizon on Azure VMware Solution.
#IBM VMWARE VDI SOLUTION WINDOWS#
Horizon lets you create, and broker connections to Windows and Linux virtual desktops, Remote Desktop Server (RDS) hosted applications, desktops, and physical machines. It delivers virtual desktops and applications on any device, anywhere.
VMware Horizon®, a virtual desktop and applications platform, runs in the data center and provides simple and centralized management. Key advantages of the Azure VMware Solution include both a more straightforward sizing method and the integration of VMware Cloud Foundation management into the Azure portal. Horizon is a different solution than Horizon Cloud on Azure, although there are some shared components.
This document focuses on the VMware Horizon product, formerly known as Horizon 7.
0 kommentar(er)
