Large-Scale Deployment: Primary Instances with Aggregate Instance

Document created by cward Expert on Oct 16, 2015Last modified by Anson McCook on Dec 16, 2016
Version 6Show Document
  • View in full screen mode

When managing a large-scale environment it may be useful to have multiple Turbonomic instances managed by an aggregate instance. Details on aggregating multiple Turbonomic instances together can be found in the User Guide by navigating to the links below. This post provides supplemental information on how aggregation works and how to setup in your environment.


Aggregated Operations Manager Installations


Adding Operations Manager Targets for Aggregation


Aggregation Details



Quick Summary:

Operations Manager Primary instances (OpsMan Primary) are deployments of Operations Manager that manage under 10,000 workloads and report back to an Operations Manager Aggregate instance (OpsMan Aggregrate). This allows for a scalable architecture that ensures performance and control from a single view.


Example Diagram:

This is an example of how the architecture works for using an Aggregate instance. For a user with around 30,000 workloads, a deployment of 3 OpsMan Primary instances would be needed. Each OpsMan Primary instance is connected to any number of hypervisor targets that manage up to 10,000 workloads. A separate OpsMan instances is then deployed to be the Aggregate Instance to manage the Primary instances.



Quick Setup Instructions:

See User Guide links at the top for more detailed information.


1) Download the Operations Manager deployment template here, Download Operations Manager (Select the appropriate Hypervisor deployment.)

Note: The same deployment template that you download for a Primary Instance will be the same deployment template for the Aggregate instance.


2) For each Primary instance, add your Hypervisor targets in the Target Configuration wizard. (Admin Tab > Workflows > Target Configuration > Add)


3) For the Aggregate instance, select "Operations Manager Appliance" to add Primary instances for management.

Host name or IP address

Provide the address of the Operations Manager server you want to set as a target. For secure communications, provide the target server’s HTTPS address.


Specify the account the aggregating server will use to access the Primary instance. This can be any Administrator account that is on the target server.

Appliance ID

The Server ID appears in the aggregating user interface when the user needs to access an underlying server. For example, assume you’re logged into an aggregating server and want to run a plan. When you display the Plan view, you will see the underlying target servers, listed by their Server IDs.

3 people found this helpful