**Goal of this checklist:** Set a clear path for High Availability Expert training ### Stage 1: Commit and Become familiar with what High Availability is - [x] **Done with Stage 1** 1. [x] Ping your manager on the issue to notify him you have started 1. [x] In your Slack Notification Settings, set **HA** as a **Highlight Word** 1. [x] Commit to this by notifying the current experts that they can start routing non-technical HA questions to you 1. [x] Understand the [basic concept of high availability](https://www.digitalocean.com/community/tutorials/what-is-high-availability) 1. [x] Understand the use of [GitLab High Availability roles](https://docs.gitlab.com/omnibus/roles/) 1. [x] Understand the different [HA architectures possible with GitLab](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3647/diffs) ### Stage 2: Technical Setup - [x] **Done with Stage 2** 1. [x] Set up a minimal HA setup using the GitLab omnibus package following the documentation at https://docs.gitlab.com/ee/administration/high_availability/ 1. [x] [Configure database](https://docs.gitlab.com/ee/administration/high_availability/database.html) 1. [x] [Configure Redis](https://docs.gitlab.com/ee/administration/high_availability/redis.html) 1. [x] [Configure NFS](https://docs.gitlab.com/ee/administration/high_availability/nfs.html) 1. [x] [Configure GitLab Application servers](https://docs.gitlab.com/ee/administration/high_availability/gitlab.html) 1. [x] [Configure load balancers](https://docs.gitlab.com/ee/administration/high_availability/load_balancer.html) ** A minimal setup has 2 application servers, 7 nodes for database components and 1 load balancer. ### Stage 3: GitLab HA Administration - [x] **Done with Stage 3** Remember to contribute to any documentation that needs updating 1. [x] https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2980 1. [x] https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3532 1. [x] https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3546 1. [x] https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4577 1. [x] https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4824 1. [x] https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4831 ### Stage 4: Tickets - [ ] **Done with Stage 4** - [ ] Contribute valuable responses on at least 10 HA tickets. Even if a ticket seems too advanced for you to answer. Find the answers from an expert and relay it to the customer. 1. [x] https://gitlab.zendesk.com/agent/tickets/85548 1. [x] https://gitlab.zendesk.com/agent/tickets/85661 1. [x] https://gitlab.zendesk.com/agent/tickets/90054 1. [x] https://gitlab.zendesk.com/agent/tickets/90164 1. [x] https://gitlab.zendesk.com/agent/tickets/91039 1. [x] https://gitlab.zendesk.com/agent/tickets/95893 1. [x] https://gitlab.zendesk.com/agent/tickets/95819 1. [x] https://gitlab.zendesk.com/agent/tickets/95877 1. [x] https://gitlab.zendesk.com/agent/tickets/97372 1. [ ] ### Stage 5: Customer Calls 1. [x] https://gitlab.zendesk.com/agent/tickets/85661 1. [x] https://gitlab.zendesk.com/agent/tickets/85548 ### [ ] Stage 6: Quiz? ### Final Stage - [ ] Your Manager needs to check this box to acknowledge that you finished - [ ] Send a MR to declare yourself an **HA Expert** on the team page