- Reference >
- Automation Agent >
- Install the Automation Agent >
- Install the Automation Agent with
debPackages
Install the Automation Agent with deb Packages¶
On this page
Overview¶
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.
Use this procedures to install the Automation Agent on Ubuntu with deb
packages. For Debian systems, use the
Install the Automation Agent from an Archive procedure.
To install the Automation Agent to a server that has an existing MongoDB
deployment that was not installed with a deb package, use the
Install the Automation Agent from an Archive procedure.
Prerequisites¶
64-Bit Architecture¶
The Automation Agent can run only on a 64-bit architecture.
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.
ReadandWritepermissions 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.
Ubuntu 12.04¶
If you install the Automation Agent to an Ubuntu 12.04 machine, and you plan to deploy MongoDB instances that use LDAP authentication, then you must either:
- manually change the primary group of the
mongodbuser tosasl, or - install the agent from the tar.gz archive.
Alternatively, you can use Ubuntu 14.04.
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.
Root Access¶
To install the Automation Agent using a deb package, you must have
root access.
Procedures¶
This section includes procedures for both installing and updating the Automation Agent.
Install the Automation Agent with a deb Package¶
Download the latest version of the Automation Agent archive.¶
On a system shell, issue a command that resembles the
following. Replace amd64 with your platform, as needed:
Install the Automation Agent Package.¶
Edit the automation-agent.config file.¶
Edit the automation-agent.config file.
For mmsGroupId, enter your GroupID as the value. For
mmsApiKey, enter the group’s agent API key.
For mmsBaseUrl, enter the URL of the Ops Manager Application. Include the port number.
Optional: Configure the Automation Agent to use a proxy server.¶
To configure the agent to connect to Ops Manager via a proxy server, you must
specify the server in the httpProxy environment variable. In the
/etc/mongodb-mms/automation-agent.config file, set the httpProxy value to the URL of to
your proxy server:
Prepare the data directory.¶
The data directory stores MongoDB data.
For an existing MongoDB deployment, ensure that the
directory is owned by the mongodb user. If no MongoDB
deployment exists, create the directory and set the owner.
Start the Automation Agent.¶
Issue the following command:
Update the Automation Agent with a deb Package¶
Important
The preferred way to update the Automation Agent is through the Ops Manager UI. If an Automation Agent is out of date, Ops Manager displays a warning on the Deployment page and provides a link to perform the update automatically.
If you use this procedure, you do not need to stop the agent. The update package automatically stops, unpacks, and then restarts the agent.
Download the latest version of the Automation Agent archive.¶
On a system shell, issue a command that resembles the
following. Replace amd64 with your platform, as needed:
Install the Automation Agent Package.¶
Prepare the data directory.¶
The data directory stores MongoDB data.
For an existing MongoDB deployment, ensure that the
directory is owned by the mongodb user. If no MongoDB
deployment exists, create the directory and set the owner.