- Create or Import a MongoDB Deployment >
- Deployment Prerequisites
Deployment Prerequisites¶
On this page
System Requirements¶
Hardware and Software¶
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. - The Automation Agent must be installed only on 64-bit architectures.
Server Networking Access¶
The hosts that serve the MongoDB deployments must:
Have full networking access to each other through their fully qualified domain names (FQDNs). Each host must be able to reach every other host through the FQDN.
To find the FQDN for each host:
On Linux / macOS hosts, run the following command in the shell:
On Windows hosts, run the following command in Powershell:
Resolve each FQDN to a unique IP address.
Run the following domain internet groper (
dig
) shell command to find the host’s IP address.Note
dig
is available for Microsoft Windows. Download and install the BIND tools from http://www.isc.org/downloads/Set the Common Name or Subject Alternative Name value of any SSL certificates to the MongoDB host’s FQDN.
The network configuration must allow each Automation Agent to make a direct connection to every MongoDB deployment listed on the Deployment page. Ops Manager does not support port forwarding.
Automation Agent Permissions¶
The Automation Agent must have permission:
To stop the MongoDB processes. The Automation Agent restarts the processes 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.
To
Read
andWrite
the MongoDB data directories and log directories.Set to the same user ID (UID) and group ID (GID) of the MongoDB process to be automated. If the MongoDB processes to be automated are not running as the same user and group, the Agent cannot manage those processes.
Example
If your Automation Agent runs as the
mongod
user in themongod
group, the MongoDB process must also run as themongod
user in themongod
group.Note
On Microsoft Windows systems, the Automation Agent, and therefore the
mongod
ormongos
services it manages, run as Windows services as theSYSTEM
user. The existing MongoDB process should run as eitherSYSTEM
orAdministrator
before adding it to automation.
Installation Options¶
Installing MongoDB Enterprise Dependencies¶
Important
If you run MongoDB Enterprise, you must manually install a set of dependencies to each server before installing MongoDB. Automation may fail if these dependencies are not installed.
Ubuntu & Debian¶
SUSE¶
Amazon Linux¶
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.
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
andWrite
permissions on the MongoDB data directory and log directory.- Permission to stop, start, and update any existing Monitoring and Backup Agents.