Chat now with support
Chat with Support

Foglight for Virtualization Enterprise Edition 8.6 - Federation Field Guide

Setting up a federated environment

Enable the federation mode by setting the server.federation variable to TRUE, in the Federation Master’s server.config file.
In the server.config file of each Federated Child, identify the port number allocated for communicating with the Federation Master (that is, identify the server.jndi.jnp.port property).
Federated Child 1: server.jndi.jnp.port = "1099";
Federated Child 2: server.jndi.jnp.port = "1099";
Federated Child 3: server.jndi.jnp.port = "1099";
Add the port number of each Federated Child in the federation to the federation.config file of the Federation Master.
The following is an example of how to add to the federation.config file the port numbers for the three Federated Children specified in Step 7.
In the federation.config file, edit the topology auto refresh period, if required. The default provided is 1800 seconds (30 minutes):

Security settings

The security settings of Federated Children are not shared with the Federation Master, each is its own security domain with user authentication settings, users, groups and role assignments.

Operations that require authentication (such as clearing alarms), when performed on the Federation Master, are authenticated on the Federation Master and executed on a respective Federation Child based on a trusted relationship. This trust is established by a security token that must match and be configured on both the Federation Master and the Federated Child. It is recommended that you use a complex token and ensure that the configuration files are read-protected from any non-root accounts (including the default foglight account). Failing to configure a security token on the Federation Master and the Federated Child prevents the authentication of Federation Master actions on the Federated Child, such as acknowledging or clearing alarms.

Open the federation.config file on the Federation Master and locate the following line:
Uncomment the line (remove the #) and define a security token.
Save the federation.config file.
Repeat Step 1 through Step 3 for each Federated Child you want to have token exchange security with the Federation Master, defining the same security token for each Federated Child.

Query limitations

The following is an example of a topology object query that limits the objects pulled by the server:

In general, when limiting the scope of topology queries, some interface views may not work properly or have missing data. If the federation topology must be limited, then the queries must be manually modified with respect to the desired topology scope and the cartridges involved. Customizing queries after the initial topology pull is less likely to cause errors. The benefit would be shorter topology refresh cycles, which can be configured to run more frequently (to refresh only the “interesting” part of the model).

Custom script queries

When deploying cartridges on a federated environment, by default, the following components are not deployed on the Federation Master:

Custom (Groovy) script queries running on a standalone Foglight Management Server do not show on the Federation Master after the .car file has been successfully deployed. This is because the federateDeployType attribute of query components in cartridges is set to DEFAULT_DEPLOY by default.

Set the federateDeployType component to ALWAYS_DEPLOY.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating