Document Deployment Practices
(DOCS-80)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 11 years, 18 weeks, 2 days ago | ||||||||
| Description |
|
We need to describe the best ways to
Feel free to add others. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 15/Oct/12 ] |
|
Closing because not actionable. Feel free to open new tickets for specific operational patterns. Of the initial list: the new docs have updated instructions for building a large index gracefully. I'm unanware of a case where we recommend manual failover (other than jiggering priorities and issuing a stepdown,) and EBS striping is ecosystem (and somewhat out of scope.) |
| Comment by Sam Kleinman (Inactive) [ 06/Jan/12 ] |
|
Kyle, I think this issue can be closed, as it is addressed in docs 2.0's tutorial section and to a lesser extent in the cookbook. I think it will be more actionable if we create specific tickets for individual tutorials or patterns that we want to see documented. I'm assigning to you in case you have specific thoughts before closing. If you want to leave it open for me to track the larger "tutorial" and "patterns" issue as a while, feel free to assign to me. Cheers, |