Commit 16ac8fdf authored by Mek Stittri's avatar Mek Stittri
Browse files

Updated references to the old high-availability page

parent 693130f4
Pipeline #144226754 skipped with stage
......@@ -35,8 +35,7 @@ you can restart GitLab with `sudo gitlab-ctl restart` (for Omnibus packages) or
 
Rebooting one of our [gitlab.com production
servers](/blog/2015/01/03/the-hardware-that-powers-100k-git-repos/) can easily take
5 minutes. To reduce the downtime for our users we used our [DRBD-based High
Availability setup](/solutions/high-availability/). First we
5 minutes. To reduce the downtime for our users we used our [DRBD-based clustered setup](https://docs.gitlab.com/ee/administration/high_availability/database.html#architecture). First we
installed updated packages on our stand-by server, followed by a reboot. Then
we did a failover from the active server to the stand-by in under a minute.
This gives us the same end result as a server reboot, namely gitlab.com running
......
......@@ -58,7 +58,7 @@ Once point of contact for your questions, one contract to bother legal with, one
Sure, there might be caveats.
 
You now have a single solution.
However, that solution is [scalable](/solutions/high-availability/) and you can set up disaster recovery if you want.
However, that solution is scalable with [Reference Architectures](solutions/reference-architectures) and you can set up disaster recovery if you want.
 
You might think that one tool restricts you to just one workflow.
However, Git allows for a number of different workflows for your teams to choose from.
......
......@@ -39,7 +39,7 @@ We offer **self-hosted** options for both
and a **hosted** option for GitLab Enterprise Edition Premium on [GitLab.com](/).
 
We have a **free and open source** offering, GitLab Community Edition, and two **enterprise** offerings,
Enterprise Edition Starter and Enterprise Edition Premium, with advanced features such as [GitLab Geo](/solutions/geo/), [High Availability and Disaster Recovery](/solutions/high-availability/), [File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html) and [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html).
Enterprise Edition Starter and Enterprise Edition Premium, with advanced features such as [GitLab Geo](/solutions/geo/), [High Availability (via our Reference Architectures)](solutions/reference-architectures), [Disaster Recovery](https://docs.gitlab.com/ee/administration/geo/disaster_recovery/), [File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html) and [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html).
 
You can **visualize your release process** in all versions of GitLab with GitLab [CI/CD Pipelines](https://docs.gitlab.com/ee/ci/pipelines.html), [Review Apps](/product/review-apps/) and [Prometheus monitoring](https://docs.gitlab.com/ee/administration/monitoring/prometheus/).
GitLab Enterprise Premium comes with [Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html) and
......
......@@ -152,7 +152,7 @@ Organizations in regulated industries, the [public sector](https://en.wikipedia.
 
In the public sector, there are standards like [NIST 800-53](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf) and [FedRAMP](https://www.fedramp.gov/). For companies handling credit card transactions, there is [PCI DSS](https://www.pcisecuritystandards.org/). These are just two examples. While some of these standards are not directly aimed at services like GitLab, they have a broad reach, and the requirements generally cannot be waived, as the penalties for non-compliance can be severe. Many enterprises have also developed their own internally driven processes and policies that can be important to support, rather than requiring changes prior to the adoption of GitLab.
 
For published standards, it is important that GitLab offers the required features and configuration to enable our customers to be in compliance. This includes changes to our code base; for example, fully encrypting all traffic between GitLab nodes, selection of specific cryptographic modules, [high availability](https://about.gitlab.com/solutions/high-availability/), and [disaster recovery](https://docs.gitlab.com/ee/administration/geo/disaster_recovery/), among others. Additionally, some standards like [FedRAMP](https://www.fedramp.gov/documents/) can also impact the operational and governance processes of GitLab.com. The more that we can do to be compliant out of the box or provide documentation on recommended settings, the less work our customers will be required to do during evaluation and implementation.
For published standards, it is important that GitLab offers the required features and configuration to enable our customers to be in compliance. This includes changes to our code base; for example, fully encrypting all traffic between GitLab nodes, selection of specific cryptographic modules, availability via our [Reference Architectures](https://about.gitlab.com/solutions/reference-architectures/), and [disaster recovery](https://docs.gitlab.com/ee/administration/geo/disaster_recovery/), among others. Additionally, some standards like [FedRAMP](https://www.fedramp.gov/documents/) can also impact the operational and governance processes of GitLab.com. The more that we can do to be compliant out of the box or provide documentation on recommended settings, the less work our customers will be required to do during evaluation and implementation.
 
By enabling our customers to meet their compliance requirements and reducing the required effort, we will see the following benefits:
 
......
......@@ -22,9 +22,7 @@ title: "Category Strategy - Disaster Recovery"
GitLab installations hold business critical information and data. The Disaster
Recovery (DR) category helps our customers fulfill their business continuity
plans by creating processes that allow the recovery of a GitLab instance following a
natural or human-created disaster. Disaster Recovery complements GitLab's [High
Availability
solution](https://about.gitlab.com/solutions/high-availability/) and
natural or human-created disaster. Disaster Recovery complements GitLab's [Reference Architectures](https://about.gitlab.com/solutions/reference-architectures/) and
utilizes [Geo nodes](https://docs.gitlab.com/ee/administration/geo/replication/)
to enable a failover in a disaster situation. We want disaster recovery to be
robust and easy to use for [systems
......
......@@ -57,7 +57,7 @@ Non-public information relating to this security control as well as links to the
### Policy Reference
* [GitLab Business Continuity Plan in Handbook](https://about.gitlab.com/handbook/business-ops/gitlab-business-continuity-plan.html)
* [GitLab Disaster Recovery](https://about.gitlab.com/handbook/engineering/infrastructure/library/disaster-recovery/)
* [GitLab High Availability](https://about.gitlab.com/solutions/high-availability/)
* [GitLab Reference Architectures](https://about.gitlab.com/solutions/reference-architectures/)
* [GitLab Infra Epic for Geo](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1)
* [GitLab Handbook listing of DR for Databases](https://about.gitlab.com/handbook/engineering/infrastructure/database/disaster_recovery.html)
* [NIST Guidance on Business Continuity](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf)
......
......@@ -71,7 +71,7 @@ Key resources by stage.
### Manage
 
* [Geo and DR](/solutions/geo/)
* [High Availability](/solutions/high-availability/)
* [High Availability (via our Reference Architectures)](/solutions/reference-architectures/)
* [Value Stream Management](/solutions/value-stream-management/)
 
### Plan
......
......@@ -192,7 +192,7 @@ If you're considering using GitLab it might not be obvious how its features corr
It is used in conjunction with GitLab CI, the open-source continuous integration service included with GitLab that coordinates the jobs.
Below are slides, the video presentation, and additional information about GitLab Runners.
* **GitLab High Availability (HA) and GitLab GEO**
- [Review the GitLab HA and Geo Replication Overview](https://about.gitlab.com/solutions/high-availability/), then hear Brian Wald, Solution Architect Manager, break it all down [on YouTube](https://youtu.be/fji7nvmOHNQ).
- [Review the GitLab Reference Architectures Overview](https://docs.gitlab.com/ee/administration/reference_architectures/), then hear Brian Wald, Solution Architect Manager, break it all down [on YouTube](https://youtu.be/fji7nvmOHNQ).
 
### Integrations
 
......
......@@ -264,9 +264,9 @@ title: "Sales & Customer Success Quick Start Learning Path"
-[GitLab Runner Doc](https://docs.gitlab.com/runner/)
-[GitLab Runner Deep Dive Slides](https://docs.google.com/presentation/d/1OhQllwfVNSbWymjf5MCxgWG86FnxjvqLUjL-8sQgZTg/edit#slide=id.g2823c3f9ca_0_9)
-[GitLab Runner Deep Dive Reording](https://drive.google.com/file/d/1QdgNLxepxiNwUwykhOX6DBmUMp067ooQ/view)
* **GitLab High Availability (HA) and GitLab GEO (Material - 20 minutes)**
-Review the GitLab HA and Geo Replication Overview, then hear Brian Wald, Solution Architect Manager, break it all down.
-[GitLab High Availability Doc](https://about.gitlab.com/solutions/high-availability/)
* **GitLab Reference Architectures and GitLab GEO (Material - 20 minutes)**
-Review the GitLab Reference Architectures and Geo Replication Overview, then hear Brian Wald, Solution Architect Manager, break it all down.
-[GitLab Reference Architectures](https://docs.gitlab.com/ee/administration/reference_architectures/)
-[GitLab High Availability and Geo Options Video](https://youtu.be/fji7nvmOHNQ)
* **ACTIVITY: Let's Install GitLab! (Material - Handbook - 60 minutes)**
-Choose one of the installation options mentioned in the link below. Once installed populate with some test data. Be sure to include: Populate with some test data: User account, Project, Issue.
......
......@@ -149,7 +149,7 @@ The key to identifying more GitLab Premium/Silver and GitLab Ultimate/Gold oppor
 
#### Achieve High Availability and Disaster Recovery
* What is your organization’s HA (High Availability) strategy? Do you have one? Why / why not?
* If HA support is needed, position Premium’s [HA support](https://about.gitlab.com/solutions/high-availability/); note: Core offers HA capabilities with self-support vs. expert GitLab support
* If HA support is needed, position Premium’s HA support via our [Reference Architectures](https://about.gitlab.com/solutions/reference-architectures/); note: Core offers HA capabilities with self-support vs. expert GitLab support
* How does your organization handle [Disaster Recovery](https://docs.gitlab.com/ee/administration/geo/disaster_recovery/index.html)?
* GitLab’s Disaster Recovery feature, only available in Premium/Silver and Ultimate/Gold SKUs, handles fail-over to another data center within minutes
* Are your development teams centrally located in generally the same vicinity or are they distributed across the world? If distributed, how do you ensure that latency between geographically dispersed developers is minimized?
......
......@@ -37,7 +37,7 @@ The below list of features are after factoring in the announcement regarding [18
 
| **Features** | **Value** |
| --------- | ------------ |
| [High Availability](https://about.gitlab.com/solutions/high-availability/) | Avoid downtime and outages, ensuring developers are able to work at all times. |
| High Availability via our [Reference Architectures](https://about.gitlab.com/solutions/reference-architectures/) | Avoid downtime and outages, ensuring developers are able to work at all times. |
| [Disaster Recovery](https://docs.gitlab.com/ee/administration/geo/disaster_recovery/index.html) | Fail-over to another data center within minutes |
| [Geographic Replication](https://about.gitlab.com/solutions/geo/) | Reduce latency between distributed teams and increase developer productivity with globally distributed cloning and container registry geographic replication. |
 
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment