- Ops Manager Overview >
- Install a Simple Test Ops Manager Installation
Install a Simple Test Ops Manager Installation¶
Overview¶
To evaluate Ops Manager, you can install the Ops Manager Application and Ops Manager Application Database on a single server. This setup provides all the functionality of Ops Manager monitoring and automation but provides no failover or high availability.
Unlike a production installation, the simple test installation uses only one mongod for the Ops Manager Application database. In production, the database requires a dedicated replica set.
This procedure includes optional instructions to activate the Backup feature, in which case you would install Snapshot Storage on the same server as the other Ops Manager components. The backup database uses only one mongod and not a dedicated replica set, as it would in production.
This procedure installs the test deployment on servers running either RHEL 6+ or Amazon Linux.
Procedure¶
Warning
This setup is not suitable for a production deployment.
To install Ops Manager for evaluation:
Set up a RHEL 6+ or Amazon Linux server that meets the following requirements:¶
- 15 GB memory and 50 GB disk space:
- The server must have 15 GB of memory and 50 GB of disk space for
the root partition. You can meet the size requirements by using an
Amazon Web Services EC2
m3.xlarge
instance and changing the size of the root partition to 50 GB. When you log into the instance, executedf -h
to verify the root partition has 50 GB of space. - Root access:
- You must have root access to the server.
Configure the yum
package management system to install the latest stable release of MongoDB.¶
Issue the following command to set up a yum
repository definition:
# Update this section with each MongoDB version.
Install MongoDB.¶
Issue the following command to install the latest stable release of MongoDB:
Create the data directory for the Ops Manager Application Database.¶
Issue the following two commands to create the data directory and change its ownership:
Create the backup directory. (Optional)¶
To configure the Backup feature as well, issue the following additional commands for the backup database:
Start MongoDB for the Application Database.¶
Start MongoDB as the mongod
user, specifying:
- Port
27017
- The
/data/appdb
path for data files (--dbpath
) - The
/data/appdb/mongodb.log
path for logs (--logpath
) - The
--fork
option to run the process in the background and maintain control of the terminal. - The
--wiredTigerCacheSizeGB
option to minimize the amount of cache the WiredTiger storage engine uses for the application database.
Start MongoDB for the backup database. (Optional)¶
Start MongoDB as the mongod
user, specifying:
- Port
27018
- The
/data/backup
path for data files (--dbpath
) - The
/data/backup/mongodb.log
path for logs (--logpath
) - The
--fork
option to run the process in the background and maintain control of the terminal. - The
--wiredTigerCacheSizeGB
option to minimize the amount of cache the WiredTiger storage engine uses for the backup database.
Download the Ops Manager package.¶
- In a browser, go to http://www.mongodb.com and click on the Download button.
- Complete the form.
- On the MongoDB Download Center page, click on the Ops Manager tab.
- Select
RedHat 5+ / CentOS 5+ / SUSE 12+ / Amazon Linux
from the Platforms drop-down menu. - Select
RPM
from the Packages drop-down menu. - Click Download.
Note
The downloaded package is named
mongodb-mms-<version>.x86_64.rpm
, where <version>
is the
version number.
Install Ops Manager.¶
Install the .rpm
package by issuing the following command, where
<version>
is the version of the .rpm
package:
The install creates the following:
The base directory for the Ops Manager software, which is:
/opt/mongodb/mms/
A new system user,
mongodb-mms
, under which the server runs.The
/opt/mongodb/mms/conf/conf-mms.properties
file, which contains the connection string to access the Application Database. The default islocahost
, port27017
, so no changes are necessary.
Only if you installed to RHEL 7.1 or 7.2, replace symlinks with scripts.¶
As a result of RHEL Bug 1285492,
the version of systemd
found in RHEL 7.1 and 7.2 Ops Manager will not start automatically
on boot up.
To work around this:
Replace the symbolic links to the scripts with the scripts themselves. Copy the scripts from
/opt/mongodb/mms/bin/mongodb-mms
to/etc/init.d
.In the copied scripts, change the line:
to:
Start Ops Manager.¶
Issue the following:
Get your server’s hostname.¶
If you are using an EC2 instance, the hostname is the Public DNS
listed on the EC2 instance’s Description
tab.
If you do not have a hostname, you can instead use the public IP address. To get the public IP address, paste this URL into your preferred browser:
Open the Ops Manager home page and register the first user.¶
In a browser, enter the following URL using the server’s hostname. If do not have a hostname, use the public IP address instead:
Click the Register link and follow the prompts to register the first user and create the first project. The first user is automatically assigned the Global Owner role.
Configure Ops Manager.¶
Ops Manager walks you through several configuration pages. Required settings are marked with an asterisk. Enter information as appropriate. When configuration is complete, Ops Manager opens the Deployment page.
If you will backup your instance, configure the backup capabilities. (Optional)¶
Create a directory to store the head databases.
Important
Do not use this directory for any other purpose:
Make the directory writable by the
mongodb-mms
user:In Ops Manager, while logged in as the user you registered during installation, click the Admin link at the top right of the page.
Click the Backup tab.
Follow the prompts to configure the Backup storage. Ops Manager walks you through the configuration.
For snapshot storage, select either the local filesystem or the backup database. If you use a File System Store, you still need a small MongoDB database for oplog storage. At the prompt to configure the connection string to the backup database, enter the following:
Set up your first deployment.¶
- Click MongoDB Ops Manager in the upper left corner of the page to return to the Deployment page.
- Click Add to deploy a MongoDB instance.