GitLab HA Module - John Long
Title: "GitLab HA Module - your-name"
Tackle stage 1 first and the last stage last, but the others can be completed in any order you prefer.
Goal of this checklist: Set a clear path for High Availability Expert training
In addition to the suggested actions here you might like to refer to Wei-Meng's HA book (currently WIP 2020-03)
Stage 1: Commit and Become familiar with what High Availability is
-
Done with Stage 1 -
Ping your manager on the issue to notify that you have started -
In your Slack Notification Settings, set HA as one of My Keywords -
Commit to this by adding yourself to the knowledge areas page. -
Commit to this by notifying the current experts that they can start routing non-technical HA questions to you -
Understand the basic concept of high availability -
Understand the use of GitLab High Availability roles -
Understand the different HA architectures possible with GitLab
-
Stage 2: Technical Setup
-
Done with Stage 2 -
Set up a minimal HA setup using the GitLab omnibus package
Note: A minimal setup should have 2 application servers, 7 nodes for database components and 1 load balancer.
-
Stage 3 (WIP): GitLab HA Administration
-
Done with Stage 3
Remember to contribute to any documentation that needs updating
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 them to the customers. -
__ -
__ -
__ -
__ -
__ -
__ -
__ -
__ -
__ -
__
-
Stage 5 (WIP): Customer Calls
-
Done with Stage 5
Stage 6 (WIP): Quiz?
-
Done with Stage 6
Final Stage
-
Your manager needs to check this box to acknowledge that you have finished. -
Send a MR to declare yourself an High Availability Expert on the team page.
Edited by John Long