Foglight for Virtualization Enterprise Edition 8.9.3 - Federation Field Guide

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.

NOTE: This procedure is valid for all cartridge components.

Upgrading cartridges on a federated system

Selectively disabling federation services

NOTE: This is an advanced configuration procedure; it is not part of your basic federation setup process. Use it only if necessary.

Certain areas of the federation functionality can be disabled independently of each other with the help of Java system properties, as presented in the following table.

These properties must be set only on the Federation Master. To take effect, any changes to these properties require a server restart using the -D option. For example, to disable remote calls during dynamic properties evaluation, restart the server using the option:

Deploying cartridge components

NOTE: This is an advanced configuration procedure; it is not part of your basic federation setup process. Use it only if necessary.

Cartridges consist of components of various types. Each component is deployed and enabled individually. Whether a particular component is enabled in a Management Server depends on the server type (Federation Master or Federated Child) and on the federation deployment type.

You can control whether components are actually deployed by overriding the default federation deployment type during the cartridge build process. If no explicit value is provided for the federation deployment type, the server uses the default values.

The federation deployment type of a component is set in the federateDeployType cartridge manifest entry for that component. The cartridge-building ant task (<car>) allows you to set that attribute by using the federateDeployType (optional) parameter on cartridge sub-elements.

The following table lists possible values of the federateDeployType parameter.

If a cartridge component has the DEFAULT_DEPLOY federation deployment type, the Management Server uses a pre-defined set of rules (based of the type of the component) to decide whether to deploy the component or not. The following table presents the cartridge components that are not deployed by default on Federation Masters.