Horizon Cloud Pod Federation Test

With the Cloud Pod Architecture feature, multiple Horizon Pods are linked together to provide a single large desktop and application brokering and management environment.

A pod consists of a set of Connection Server instances, shared storage, a database server, VMware vSphere server and network infrastructures required to host desktop and application pools. In a traditional Horizon implementation, each pod is managed independently. With the Cloud Pod Architecture feature, multiple Pods are joined together to form a single Horizon implementation called Omnissa Horizon Cloud Pod Federation.

An Omnissa Horizon Cloud Pod Federation spans multiple sites and data centers and simultaneously simplifies the administration effort required to manage a large-scale Horizon deployment.

This test monitors the Omnissa Horizon Cloud Pod Federation, provided, the target Omnissa Horizon Cluster/pod is within the federation and reports the number of sites and Horizon Cluster/Pods in the federation.

Target of the test : An Omnissa Horizon Cluster/Pod

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the Omnissa Horizon Cluster/Pod being monitored

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	Refers to the port used by the target Omnissa Horizon Cluster/Pod. By default, this is set to NULL.
Connection Server Name	By default, this test connects to every Horizon Connection Server configured in the Omnissa Horizon Cluster/Pod remotely and collects the required metrics. For this, it is necessary to specify valid credentials of the Horizon Connection Servers. To help administrators provide these credentials quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the encircled '+' icon that appears alongside this parameter in the test configuration page. To know how to use this special page, refer to Configuring the Omnissa Horizon Connection Servers for Monitoring.
User Name, Password and Confirm Password	By default, this test uses Omnissa Restful APIs to collect the required metrics from the target Omnissa Horizon Cluster/Pod. For this, the eG agent should be configured with read-only user privileges that will allow the agent to communicate with the Horizon Connection Server in a particular domain and extract statistics. Therefore, specify the credentials of the user who is authorized to access the Horizon Connection Server against the User Name, Password and Confirm Password text boxes.
Domain Name	Specify the name of the domain to which the Horizon Connection Server belongs to.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total sites	Indicates the total number of sites.	Number
Total Horizon pods	Indicates the total number of Horizon Cluster/Pods.	Number	The detailed diagnosis of this measure lists the name of the Horizon Pods within the Horizon Cloud Pod Federation and also indicates whether/not each Horizon Pod is a local pod.