[DOCS-4632] Network diagram of MMS components needs to be more explicit Created: 09/Jan/15 Updated: 03/Feb/15 Resolved: 03/Feb/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.18, mms-1.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Ingo (Inactive) | Assignee: | Allison Reinheimer Moore |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 2 weeks, 1 day ago | ||||||||
| Description |
|
The MMS manual contains some pictures describing the various components included in MMS on-prem: http://mms.mongodb.com/help-hosted/current/core/deployments/ However, these are too vague and high level to be useful to an engineer who actually wants to install MMS on-prem. What is needed is a more explicit, actionable diagram, clearly describing which component is talking to which. In this style: http://www.lovemytool.com/.a/6a00e008d957708834013486864b9e970c-pi At least the following information needs to be clear:
|
| Comments |
| Comment by Githook User [ 03/Feb/15 ] |
|
Author: {u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}Message: |
| Comment by Githook User [ 03/Feb/15 ] |
|
Author: {u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}Message: |