diff options
| author | Drew Blessing <drew@gitlab.com> | 2017-05-17 10:04:07 -0500 |
|---|---|---|
| committer | Drew Blessing <drew@gitlab.com> | 2017-05-17 14:37:47 -0500 |
| commit | 65382a9763c604799f34ef7e0b3839fc707ffdc4 (patch) | |
| tree | e56b976430b03f699dd09c69b7d324e2ed09473e | |
| parent | daf9ec6cd1f88e7462cae9dc68eda2dcf793cecf (diff) | |
| download | gitlab-ce-65382a9763c604799f34ef7e0b3839fc707ffdc4.tar.gz | |
Consolidate opening text from about.gitlab.com and add active/passive note
Add opening text that was previously on https://about.gitlab.com/high-availability
and add a note that active/passive is compatible but not supported.
| -rw-r--r-- | doc/administration/high_availability/README.md | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/administration/high_availability/README.md b/doc/administration/high_availability/README.md index d5a5aef7ec0..4d3be0ab8f6 100644 --- a/doc/administration/high_availability/README.md +++ b/doc/administration/high_availability/README.md @@ -5,6 +5,20 @@ The solution you choose will be based on the level of scalability and availability you require. The easiest solutions are scalable, but not necessarily highly available. +GitLab provides a service that is usually essential to most organizations: it +enables people to collaborate on code in a timely fashion. Any downtime should +therefore be short and planned. Luckily, GitLab provides a solid setup even on +a single server without special measures. Due to the distributed nature +of Git, developers can still commit code locally even when GitLab is not +available. However, some GitLab features such as the issue tracker and +Continuous Integration are not available when GitLab is down. + +**Keep in mind that all Highly Available solutions come with a trade-off between +cost/complexity and uptime**. The more uptime you want, the more complex the +solution. And the more complex the solution, the more work is involved in +setting up and maintaining it. High availability is not free and every HA +solution should balance the costs against the benefits. + ## Architecture There are two kinds of setups: @@ -37,6 +51,10 @@ Block Device) to keep all data in sync. DRBD requires a low latency link to remain in sync. It is not advisable to attempt to run DRBD between data centers or in different cloud availability zones. +> **Note:** GitLab recommends against choosing this HA method because of the + complexity of managing DRBD and crafting automatic failover. This is + *compatible* with GitLab, but not officially *supported*. + Components/Servers Required: 2 servers/virtual machines (one active/one passive)  |