Connection Server instances communicate in a Cloud Pod Architecture environment by using an interpod communication protocol called the View InterPod API (VIPA).
Connection Server instances use the VIPA communication channel to launch new desktops, find existing desktops, and share health status data and other information. Horizon 8 configures the VIPA communication channel when you initialize the Cloud Pod Architecture feature.
If running Horizon 8 2309 and later, make sure that at least (N/2)+1 nodes are up and running in the pod, where N is the total number of nodes registered in a pod. If the number of up and running nodes is less than (N/2)+1, then none of the provisioning or imaging operations will go through.
VIPA communication uses HTTPS over TCP port 8472 and is protected by certificates that Horizon 8 rotates automatically every seven days.
Where the Global Data Layer answers "what is configured" (entitlements, topology, policy), VIPA answers "what is happening right now" — for example, whether a specific pool in a remote pod currently has an available desktop, or whether a user already has a session running somewhere else in the federation. The two mechanisms work together during every brokering decision: Global Data Layer data tells a Connection Server instance which pools it is allowed to search, and VIPA lets it actually ask the pods that own those pools whether a resource is available.
Was this page helpful?