You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Damodar Reddy T (JIRA)" <ji...@apache.org> on 2014/02/05 10:28:11 UTC

[jira] [Created] (CLOUDSTACK-6029) [Doc] Comments to be put in the Techinical documentation as well as in the FS

Damodar Reddy T created CLOUDSTACK-6029:
-------------------------------------------

             Summary: [Doc] Comments to be put in the Techinical documentation as well as in the FS
                 Key: CLOUDSTACK-6029
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6029
             Project: CloudStack
          Issue Type: Task
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Doc
    Affects Versions: 4.3.0
            Reporter: Damodar Reddy T
            Assignee: Damodar Reddy T
            Priority: Critical
             Fix For: 4.3.0


The following comments need to be put in the FS as well as int he technical documentation

1. Explain the additional configuration required to handle split-brain in ticket and FS
2.  Find the standard terminology(For Active/Active Master/Master) used and document to Make sure the correct terminology is being used in all documentation.
3. Find the ping timout and document
4. Find out about the DB version certified with CS, also what version of RHEL/CentOS are supported and what DBs they run
5. Can you put some pointers to documentation on best practices in FS (For Async and Semi-Sync
6. Network topology(Same Zone, Multiple Zones) and latency requirements for setting up DB-HA needs to be documented.
7. Backup and restore mechanism best practices.
8. Latency in updating slave in case of Async.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)