[SERVER-18399] Remind user that their Mongo process is controlled by Cloud/Ops Manager Automation via the mongo shell Created: 09/May/15  Updated: 19/Jul/23  Resolved: 15/Jul/16

Status: Closed
Project: Core Server
Component/s: Admin, Shell
Affects Version/s: None
Fix Version/s: 3.3.10

Type: New Feature Priority: Major - P3
Reporter: Cailin Nelson Assignee: Andrew Morrow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-25066 Surface automation state in the shell... Closed
Documented
is documented by DOCS-8388 3.4 -- automationNotices Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Build 9 (09/18/15), Build A (10/09/15), Platforms 15 (06/03/16), Platforms 16 (06/24/16), Platforms 17 (07/15/16)
Participants:
Case:

 Description   

When a MongoDB process is controlled by Cloud Manager or Ops Manager Automation, some actions that can be performed by the user in the shell will be reverted by Automation if they are in conflict with the configuration entered into Cloud/Ops Manager.

Examples:

  • Changing the replica set configuration
  • Adding, editing or removing a custom role
  • Adding/removing a shard
  • Using setParameter to change the sslMode or clusterAuthMode

To enhance the user experience and prevent confusion, it would be helpful if the mongo shell could contain a message along the lines of: "Note - this process is controlled by Cloud Manager, GroupID XYZ. Please login to cloud.mongodb.com to make configuration changes."

Presumably:

  • This message would be stored inside an internal MongoDB structure somewhere
  • The Automation Agents would call a command to record this message
  • The mongo shell would look for messages of this type and display it

Please note that startupWarnings would not be an ideal solution. There are many systems (including Cloud Manager itself) which assume that startupWarnings have a negative connotation. This is informational, not a warning.

To be consistent, this message would need to appear for both mongod and mongos processes.

Additionally, it would be nice to also include this sort of message in the header of the log files.



 Comments   
Comment by Kay Kim (Inactive) [ 20/Jul/16 ]

Thank you. Will make a ticket and link.

Comment by Githook User [ 16/Jul/16 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: SERVER-18399 Fix clang builds broken by automation aware shell
Branch: master
https://github.com/mongodb/mongo/commit/88f4b9ac327248befff7f83fb1cdd9f4bb9f8916

Comment by Githook User [ 15/Jul/16 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: SERVER-18399 Issue a notification in the shell when automation is active

Also provides a new setParameter to configure the automation name
to be returned in an isMaster reply.
Branch: master
https://github.com/mongodb/mongo/commit/08ef5eefb59b96c6696416144d43cfe2c45d3619

Generated at Thu Feb 08 03:47:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.