[DOCS-6498] Steps to move processes from one Ops Manager group to another. Created: 30/Oct/15  Updated: 13/Dec/19  Resolved: 04/Jan/18

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

Type: Task Priority: Major - P3
Reporter: Barry O'Neill Assignee: Robert Justice (Inactive)
Resolution: Won't Fix Votes: 0
Labels: docs-cloudmgr-opsmgr-security
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 8 weeks ago
Story Points: 1

 Description   

Hi,

I have seen a large number of customers opening tickets requesting steps to move processes from one group to another. Would it be possible for us to document the steps to do this?

Firstly, you need to retrieve the password for this user by issuing the following command at OS level:

curl -u $mmsGroupId$:$mmsApiKey$ $mmsBaseUrl$/agents/api/automation/conf/v1/$groupId$? | python -m json.tool | grep autoPwd

Then create the user on your deployment by logging into the instance using the mongo shell with a user that has the ability to create users on the admin database. Then run the following:

db.createUser({user: "mms-automation", pwd: $autoPwd$, roles: ["clusterAdmin", "dbAdminAnyDatabase","readWriteAnyDatabase","userAdminAnyDatabase" ] });

("$autoPwd$" is the password we retrieved in Step 1)

Then attempt to add the cluster to automation again.

Thanks,

Barry



 Comments   
Comment by Andrew Davidson [ 20/Dec/17 ]

It does seem hard to rationalize publishing this endpoint.
To play devil's advocate through, don't we currently make the group's agent password available via the API (specifically the first time the group is created)

Comment by Andrew Davidson [ 18/Dec/17 ]

Sorry I filed this ticket a few yrs ago, so it's hard to remember / get on to speed on context.
Which is the undocumented API that would be required here?

Comment by Barry O'Neill [ 15/Dec/17 ]

Hi Rob,

fwiw here is the procedure I have been giving to customers moving between OM groups up until very recently:

I will outline the steps you will need to follow to execute out the migration all at once and include documentation for more detailed description of each step:

  1. Un-manage all of the processes in your current Ops Manager as (described here)https://docs.opsmanager.mongodb.com/current/tutorial/unmanage-deployment/]
  2. Stop any Automation, Monitoring and Backup Agent processes that are running on the hosts that you want to migrate
    • To determine the process ids of the agent processes you can run the following command:

      ps aux | grep mongo
      

    • You can then stop the relevant processes

      sudo kill <pid>
      

  1. You will need to edit the Automation Agent Config file to point to the Ops Manager mmGroupId and mmsAPIKey
  1. If you are using authentication you will need to follow the next steps:
    • First you will need to drop the mms-automation user from the process you are trying to ad to the Ops Manager deployment.
      1. log into the DB with a user that is able to add / remove users.
      2. drop the user

         db.dropUser("mms-automation")

    • Retrieve the password from your NEW Ops Manager group using the command below.

      curl -u MMSGROUPID:MMSAPIKEY $mmsBaseUrl$/agents/api/automation/conf/v1/$groupId$'?' | python -m json.tool | grep autoPwd

    • Next create the mms-automation agent user on the process you are trying to add:

      db.createUser({user: "mms-automation", pwd: $autoPwd$, roles: ["clusterAdmin", "dbAdminAnyDatabase","readWriteAnyDatabase","userAdminAnyDatabase" ] });
      

      ("$autoPwd$" is the password we retrieved above)

  2. Import the processes for monitoring
  3. Add the monitored processes to Automation

Cheers,
Barry

Comment by Andrew Davidson [ 06/Mar/17 ]

Sure sounds good ("Move process(es) into another group's deployment"

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:52:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.