Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Provision Servers for Automation

On this page

Overview

Ops Manager can automate operations for the MongoDB processes running on your servers. Ops Manager can both discover existing processes and deploy new ones.

Ops Manager Automation relies on an Automation Agent, which must be installed on every server that runs a monitored MongoDB deployment. The Automation Agents periodically poll Ops Manager to determine the goal configuration, deploy changes as needed, and report deployment status back to Ops Manager.

When you provision servers for Automation they are also provisioned for Monitoring. To provision servers for Automation, install the Automation Agent on each server.

Prerequisites

Before you can provision servers for automation you must meet the following prerequisites.

Server Hardware

Each server must meet the following requirements.

  • At least 10 GB of free disk space plus whatever space is necessary to hold your MongoDB data.
  • At least 4 GB of RAM.
  • If you use Amazon Web Services (AWS) EC2 instances, we recommend at least an m3.medium instance.

Server Networking Access

The servers that host the MongoDB processes must have full networking access to each other through their fully qualified domain names (FQDNs). You can view a server’s FQDN by issuing hostname -f in a shell connected to the server. Each server must be able to reach every other server through the FQDN.

Ensure that your network configuration allows each Automation Agent to connect to every MongoDB process listed on the Deployment tab. Ensure that the network and security systems, including all interfaces and firewalls, allow these connections.

Installing to a Server that Already Runs MongoDB

If you install the Automation Agent to a server that is already running a MongoDB process, the agent must have:

  • Permission to stop the MongoDB process. The Automation Agent will restart the process using the agent’s own set of MongoDB binaries. If you had installed MongoDB with a package manager, use the same package manager to install the Automation Agent. This gives the agent the same owner as MongoDB.
  • Read and Write permissions on the MongoDB data directory and log directory.
  • Permission to stop, start, and update any existing Monitoring and Backup Agents.

Installing to a Server Before Installing MongoDB

If you deploy the Automation Agent to a server that does not have MongoDB installed, ensure the user that owns the Automation Agent has Read and Write permissions on the MongoDB data and log directories you plan to use.

MongoDB Enterprise Dependencies

If you will run MongoDB Enterprise, you must manually install a set of dependencies to each server before installing MongoDB. The MongoDB manual provides the appropriate command to install the dependencies. See the link for the server’s operating system:

Procedure

Install the Automation Agent on each each server that you want Ops Manager to manage. The following procedure applies to all operating systems. For instructions for a specific operating system, see Install the Automation Agent.

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.

1

In Ops Manager, select the Settings tab and then select Agents.

2

Under Automation, click your operating system and follow the instructions to install and run the agent.

For more information, see also Install the Automation Agent.

Next Steps

Once you have installed the agent to all your servers, you can deploy your first replica set, cluster, or standalone.

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.