[DOCS-5732] Incorrect information in Ops Manager Documentation Created: 26/Jun/15  Updated: 11/Jan/17  Resolved: 26/Jun/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Task Priority: Major - P3
Reporter: Joshua Maag Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 8 years, 33 weeks, 5 days ago

 Description   

On the troubleshooting page for Ops Manager, https://docs.opsmanager.mongodb.com/v1.6/troubleshooting/, there is a line that says the following:

There are two ways to install the Automation Agent on your servers. First, you can simply install the Automation Agent on all existing hardware. Second, you can use Ops Manager Provisioning to automatically create Amazon Web Services (AWS) EC2 instances that have the Automation Agent pre-installed.

This statement has lead a customer to believe that Ops Manager is able to provision instances directly from the interface, much like Cloud Manager does. It should be clarified to state that you can attach EC2 servers by installing the automation agent on them first, but that they can't spin up a bunch of EC2 servers from Ops Manager.

Thanks,

Joshua



 Comments   
Comment by Allison Reinheimer Moore [ 26/Jun/15 ]

Thanks for the catch! I've updated the paragraph in question and am publishing the changes now. They should be live in the next 15 minutes.

Generated at Thu Feb 08 07:50:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.