[DOCS-5278] Add more information about importing existing clusters Created: 24/Apr/15  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: James O'Leary Assignee: Anthony Sansone (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 7 years, 29 weeks ago
Epic Link: docs-replication
Story Points: 4

 Description   

The documentation for MMS automation could do with sections covering:

  1. the ethos of automation. Explain early that automation will manage and control your instances, unlike the using package or tar ball installs. UNIX services no longer control the mongo processes, they must be controlled from the MMS UI or indirectly through the MMS automation API.
  2. add warnings to the import existing cluster pages and new FAQ entries that cover:
    • the PATH environment variable for the mongo shell may need to be updated
    • Remove or disable the mongod service
    • (optionally) Remove the old binaries
    • ensure that rebooting the node should start the automation agent which should in turn restart the mongo processes.
    • explicitly mention that other automated tasks (such as cron jobs will also need to be updated)


 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

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