[DOCS-8131] Explain how to successfully stop using Automation features on the Free Tier Created: 19/Jun/16  Updated: 22/Jul/16  Resolved: 21/Jul/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: v20160621

Type: Bug Priority: Major - P3
Reporter: Cailin Nelson Assignee: Anthony Sansone (Inactive)
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: 7 years, 30 weeks ago
Epic Link: C/OM Automation
Story Points: 1

 Description   

When the Cloud Manager Free Trial expires, Groups lose access to Automation. Typically, Groups may be using Automation at this time for

  • Managing their Monitoring and/or Backup Agents
  • Managing their MongoDB Deployments

In order to stop using Automation, Groups should:

  1. Ensure that the package version for their Automation Agent is at least 2.7.1. Please note that this is not the version shown in the UI. They must check the package version on disk.
  2. Use the "Make init scripts tool" to create init scripts for their MongoDB processes. This is already nicely described here and we can link to that.
  3. "Unmanage All" from the deployment page
  4. Login to each server and stop all Automation Agents. Also verify that all Monitoring and Backup Agents have been stopped.
  5. Manually install a Monitoring Agent and (optionally) manually install a Backup Agent using the package instructions found at Deployment : Agents.


 Comments   
Comment by Cailin Nelson [ 20/Jul/16 ]

http://www.rpm.org/max-rpm/s1-rpm-query-handy-queries.html
https://www.debian.org/doc/manuals/apt-howto/ch-search.en.html

Comment by Bob Grabar [ 23/Jun/16 ]

tony.sansone Let Cailin know when this is complete. If affects the UI. See this comment.

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