Navigation

Provision Servers for the Server Pool

Ops Manager Server Pool allows Ops Manager users with administrative privileges, i.e. Ops Manager Administrators, to maintain a pool of globally provisioned servers that already have Automation Agents installed.

When users in a group want to create a new MongoDB deployment, they can request servers from this pool to host the MongoDB deployment.

Administrators can associate properties with the servers in the pool. The administrator can then expose these server properties as options when a user creates a server request; i.e. the user can select certain properties to request servers that match the these properties.

Administrators control which server properties are exposed to the user. That is, the Administrator can provide the user access to all the available server properties or restrict the user to a specific properties. For details, see Servers Request Options.

Enable and Configure the Server Pool

To enable and configure the server pool, click the Admin link in the top right corner of Ops Manager to access the settings panels. From the General tab, go to Ops Manager Config and select the the Server Pool tab.

If the server pool is disabled, enable server pool and configure the server pool, such as setting server termination policy. The configuration applies to all servers in the pool.

Provision Servers for the Pool

Requirements

The servers in the pool must meet the same prerequisites as any other provisioned servers.

Install Automation Agents

Install the Automation Agent on each server for the pool. Follow the instructions for your operating system found at Install or Update the Automation Agent.

Important

In the agent’s configuration file, specify the server pool configuration for the agent. Do not specify the group configuration. For details, see the installation instructions.

Tip

On Linux servers, if you installed MongoDB with a package manager, use the same package manager to install the Automation Agent. If you installed MongoDB without a package manager, use an archive to install the Automation Agent

Manage the Server Pool

To manage servers in the pool, click the the Admin link in the top right corner and go to the Server Pool tab.

View Servers

From the Server Pool page, the Server List displays the servers in the pool as well as their availability (i.e. whether they are bound to a group or unbound).

Terminate Servers

From the Server List view, Administrators can terminate unbound servers. For servers bound to a group, owners of the group can terminate the servers from their Deployment view.

The termination policy, set in Enable and Configure the Server Pool, determines what happens to terminated servers and their data files.

Recycle Terminated Servers

If the policy determines that the servers are not automatically returned to the pool upon termination, the servers go to the Recycle Bin. From the Recycle Bin view, Administrator can recycle terminated servers to return them to the pool.

If the list of terminated servers exceed the list displayed on the current page, Recycle All recycles all terminated servers in the recycle bin, not just the servers displayed on the current page.

View Pending Request

From the Server Pool page, the Pending Requests view lists the pending requests. Administrator can cancel pending requests from this view. When users submit server request and no servers exist that can fulfill the request, users can cancel their request at that time.

If neither the user or the Administrator cancels the pending request, the request expires once the timeout period has passed. The Ops Manager Administrator sets the request timeout period for the server pool through the Enable and Configure the Server Pool.

Manage Server Request Options

From the Servers Request Options page, Administrators can control which server properties are exposed to the user when the user creates the server request.

Server properties are specified in the serverPoolPropertiesFile file that the Administrator specifies when installing the Automation Agent.

By controlling which properties to expose to the users, the Administrator can control the degree of customization that a user can have when creating the server request.

For example, the Administrator can provide access to all the available server properties to allow for maximum customization of the server request, or limit users to certain properties, or even limit all properties from the user.