[DOCS-11082] Document how to convert an existing Community deployment to Enterprise Advanced Created: 05/Dec/17 Updated: 05/Sep/18 Resolved: 07/Aug/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Nicholas Larew |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 10 weeks, 1 day ago | ||||||||
| Description |
|
It's not clear if the documentation explains how to convert from Community to Enterprise. (It's sort of implicit if you understand MongoDB well enough to use one of the various Enterprise Installation instructions and maybe one of the 3 sets of Upgrade instructions in the Release Notes, but that's a tall order that presupposes that the user is aware of those 4 separate pages in the documentation. I propose that the Installation docs for Enterprise have subsections identifying how to convert from Community, that each Installation document links to each of the 3 Upgrading documents in the Release Notes, and that each of the Upgrading documents in the Release Notes call out the fact that the upgrade steps also (roughly) define the order of doing rolling cutovers from Community to Enterprise. (I see no need to document how to switch from Enterprise to Community, in case that matters.) |
| Comments |
| Comment by Richard Kreuter (Inactive) [ 05/Dec/17 ] |
|
By the by, the first paragraph is a problem description, and my proposal is just one way to do it. If you want to write a separate tutorial on the conversion, that'd be fine (preferable even, so that users don't have to pick the correct cross-document links, which my proposal requires). |