Install a Simple Test Ops Manager Installation
Warning
This setup is not suitable for a production deployment.
To evaluate Ops Manager, you can install the Ops Manager Application and Ops Manager Application Database on a single host. This setup provides all the functionality of Ops Manager monitoring and automation but provides no failover or high availability.
Considerations
This test installation includes the following caveats:
It uses one
mongod
for the Ops Manager Application database. In production, the database requires a dedicated replica set.It uses MongoDB Community Edition. MongoDB Community doesn't need additional libraries.
It doesn't include backup functionality.
Procedure
To install and configure an evaluation version of Ops Manager on hosts running Red Hat Enterprise Linux 8.0:
Provision an Ops Manager host.
Provision a host for Ops Manager. This host must meet the following requirements:
System Memory | 15 GB |
Disk Capacity | 50 GB in / (The root directory of this host) |
Host OS Permissions | root |
Host OS | Red Hat Enterprise Linux 8.0 |
Cloud-based instances must meet the memory and storage requirements.
To verify the needed capacity, log in to the instance and execute the following commands:
vmstat -S M -s | grep "total memory"
The output for the command shows that this instance has 16 GB of RAM.
16384 M total memory
df -h | grep "/$"
The output for the command shows that this instance has 73 GB of storage capacity.
/dev/sda1 73G 58G 12G 84% /
Important
Verify that the ulimit
settings meet the
minimum requirements.
Configure yum
to install MongoDB.
Create a /etc/yum.repos.d/mongodb-org-6.0.repo
file so
that you can install MongoDB directly using yum
:
[mongodb-org-6.0] name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/6.0/x86_64/ gpgcheck=1 enabled=1 gpgkey=https://pgp.mongodb.com/server-6.0.asc
Optional: Disable the mongod
service.
Ops Manager connects to its application database on port 27017. If
the host on which you want to install the application database has a
running mongod
, disable that existing database.
To disable the mongod
service, invoke the following command:
sudo systemctl disable mongod
Update the MongoDB configuration file.
The installer creates a configuration file saved at
/etc/mongod.conf
.
Open the MongoDB file with your preferred text editor.
Edit the file to make the following changes:
1 systemLog: 2 destination: file 3 path: "/data/appdb/mongodb.log" 4 logAppend: true 5 storage: 6 dbPath: "/data/appdb" 7 journal: 8 enabled: true 9 wiredTiger: 10 engineConfig: 11 cacheSizeGB: 1 12 processManagement: 13 fork: true 14 timeZoneInfo: /usr/share/zoneinfo 15 pidFilePath: /var/run/mongodb/mongod.pid 16 net: 17 bindIp: 127.0.0.1 18 port: 27017 19 setParameter: 20 enableLocalhostAuthBypass: false Save the file when you have made the edits.
Download the Ops Manager package.
Navigate to the Ops Manager Download Center.
From the Platforms drop-down menu, click Red Hat + CentOS 6, 7, 8 / SUSE 12 + 15 / Amazon Linux.
From the Packages drop-down menu, click RPM.
Click Download.
Note
MongoDB names the downloaded package
mongodb-mms-<version>.x86_64.rpm
. <version>
represents the
version number for Ops Manager.
Optional: Verify Ops Manager package integrity.
To verify the integrity of the Ops Manager download, see Verify Integrity of Ops Manager Packages.
Install Ops Manager.
To install the .rpm
package, invoke the following command.
<version>
represents the Ops Manager version in the .rpm
package:
sudo rpm -ivh mongodb-mms-<version>.x86_64.rpm
This command creates the following artifacts:
Artifact | Value |
---|---|
Ops Manager software base directory | /opt/mongodb/mms/ |
New system user that owns the Ops Manager processes | mongodb-mms . |
Ops Manager configuration file with the
connection string to access the Application Database . Don't change this value defaults from
locahost:27017 . | /opt/mongodb/mms/conf/conf-mms.properties |
Get your instance hostname.
If you use an cloud service provider instance, find the hostname following the directions of the relevant provider:
If you don't have a hostname, use the public IP address. To find your host's public IP address, paste this URL into your preferred browser:
https://www.google.com/search?q=myip
Open the Ops Manager home page and register the first user.
In a browser, enter the following URL using the hostname. If do not have a hostname, use the public IP address instead:
http://<OpsManagerHost>:<Port> Click the Sign Up link.
Follow the console prompts to register the first user and create the first organization and project. Ops Manager assigns the Global Owner role to the first user.
Configure Ops Manager.
Ops Manager opens the configuration console. Ops Manager marks required settings with an asterisk.
Enter the information as appropriate. When you finish the configuration, Ops Manager opens the Deployment page.