[DOCS-4979] Documentation on CNAME is of little help when deploying with automation Created: 11/Mar/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Daniel Coupal | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | docs-automation-agent |
| Description |
|
Going through the deployment wizard, we suggest to the user to use CNAME to avoid having to change connection strings, avoid downtime, ... and point to the following documentation: http://docs.mongodb.org/manual/core/sharded-cluster-config-servers/. The link is confusing as the doc is about config servers, and searching for CNAME gives about the same 2 lines of text as shown in the wizard without adding more. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |