jasmerchant.blogg.se

F5’s Global Traffic Management (GTM) is used to automatically balance the load between the two geographically separated POD’s. The toplevel Virtual IP (VIP) is used (with an FQDN) for every external device to connect to an available desktop.

Redundant hardware in each POD (hosts, networking, storage, etc)Īnd all of this is based on the fact you use Horizon 6+ in combination with security servers for external connections which are paired to connection servers.

To get CPA to work in a normal/common practice way, you need some prerequisites to be in place:

Well, first watch these three short instruction videos so you know how what it is and how it should work.

But what about NSX, the network virtualization software that has a load balancer included in the solution? Can you use that in conjunction with Cloud Pod Architecture (CPA) as well? In this post I will explain the functionality of CPA and why/where you would like to add a load balancer with specific functions. F5 has such a module next to their Local Traffic Manager (LTM) as well. And in case of geographically separated data centers, a load balancer with support for a Global Traffic Manager as well. To use this feature, it is a best practice to set up load balancing as well. This feature can make sure that you can run Horizon based VDI/Remote Apps from multiple data centers and that the maximum number of desktops can exceed 10,000 per Horizon implementation (by setting up multiple POD’s with 10,000 desktops each). In 2014, VMware announced a new feature in Horizon 6 called Cloud Pod Architecture.