Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-7485

Server Content Intake/Input from SE and Tug

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: None
    • Security Level: Public
    • Labels:
      None

      Description

      Meeting set up with Tug, Alex, Perry, Tim

      Hi,

      Frank asked that I start working on the Server Guide some more and any input/changes from customers or yourself. This includes:

      -Areas that need to be reorganized for clarity
      -Areas that need more content, or have missing content
      -Areas that need to be edited for more clarity.

      Note to Tug: For logistics/time I am happy to schedule a separate session with you next week around 9AM PST.

      Thanks

      Karen

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        kzeller kzeller added a comment -

        Time, James, AlexM:

        -Hard to find info. Suggestion: reorganize around activities: failover, rebalance, backup and restore, sizing, performance, managing buckets

        -Would help if we organize this way:
        -managing buckets
        -concepts/background (can be skimmed or skipped by user if they want to just know 'how' to do stuff)
        -considerations, any issues they should be aware of before they do any actions related to this component
        -how-to (create, delete, etc.)
        -tips, tricks, best practices, what to avoid

        -Alternate way to organize is 1) all concepts together 2) then all how to's. Problem is divorcing background/key-concept from 'how-to-manage/change'

        Other topics: Changing cluster size, rebalance, monitoring a cluster

        For introductory material, would be more helpful if we treat installation as different than provsioning nodes:

        -install = already plenty of content, dont' need anymore. Already easy
        -getting started = actually creating a cluster with two nodes. Make it cluster-oriented

        Naming/Organization
        -too many sections getting buried under chapter headings that are too vague, e.g. Administration Basics, Administration Tasks, Best practice
        -too many topic get buried in chapter such as command line tools, or rest, instead of organize around activity
        -Need simplified naming, naming that indicates what you accomplish.

        Gaps:

        -things that are node-to-node
        -monitoring a cluster, how to monitor, what is truly meaningful from all our stats, not just what they all are.

        Show
        kzeller kzeller added a comment - Time, James, AlexM: -Hard to find info. Suggestion: reorganize around activities: failover, rebalance, backup and restore, sizing, performance, managing buckets -Would help if we organize this way: -managing buckets -concepts/background (can be skimmed or skipped by user if they want to just know 'how' to do stuff) -considerations, any issues they should be aware of before they do any actions related to this component -how-to (create, delete, etc.) -tips, tricks, best practices, what to avoid -Alternate way to organize is 1) all concepts together 2) then all how to's. Problem is divorcing background/key-concept from 'how-to-manage/change' Other topics: Changing cluster size, rebalance, monitoring a cluster For introductory material, would be more helpful if we treat installation as different than provsioning nodes: -install = already plenty of content, dont' need anymore. Already easy -getting started = actually creating a cluster with two nodes. Make it cluster-oriented Naming/Organization -too many sections getting buried under chapter headings that are too vague, e.g. Administration Basics, Administration Tasks, Best practice -too many topic get buried in chapter such as command line tools, or rest, instead of organize around activity -Need simplified naming, naming that indicates what you accomplish. Gaps: -things that are node-to-node -monitoring a cluster, how to monitor, what is truly meaningful from all our stats, not just what they all are.

          People

          • Assignee:
            kzeller kzeller
            Reporter:
            kzeller kzeller
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes