Skip to content

Geo - Mike Lockhart

module-name: "Geo"
area: "Product Knowledge"
gitlab-group: "Enablement:Geo"
maintainers:
  - abuerer

Goal of this checklist: Set a clear path for Geo Expert training

Tackle stage 1 first and the last stage last, but the others can be completed in any order you prefer.

Stage 0: Create and commit to the module

  1. Create an issue using this template by making the Issue Title: Geo - "your name"

  2. Add yourself and your trainer as the assignees.

  3. Notify your manager to let them know you've started.

  4. In your Slack Notification Settings, set Geo as a Highlight Word

  5. Commit to this by notifying the current experts that they can start routing non-technical Geo questions to you.

  6. Optional: Set a milestone, if applicable, and a due date to help motivate yourself!

  7. Update your Support Team yaml file to indicate that you've started learning this knowledge area:

    knowledge_areas:
- name: Geo
  level: 1

Stage 1: Become familiar with what Geo is

  • Done with Stage 1
  1. Read about the initial decisions, implementation and background
    1. GitLab University (Be aware that we have added a lot of features since those materials and they might not be up to date but are great in providing context)
      1. GLU Deck on Geo
      2. GLU Recording on Geo (46m)
    2. Read the detailed "How we built GitLab Geo" blog post for details about implementation and phases we went through
    3. Be aware that we have (Geo Scheduling Call, Geo Monthly Testing Update) and Geo Group on YouTube. Take note the playlist is sorted by latest video first.
  2. Read through all the Geo Documentation

Stage 2: Technical Setup

  • Done with Stage 2

Remember to contribute to any documentation that needs updating

  1. Standard installations following the Setup Instructions to install Geo on two VMs. If you have a test license, Geo will replicate the license applied on the primary, but you will need to recreate the test license changes to gitlab.rb on your secondary node.
  2. Set up a local repo to push to the primary and pull from the secondary
  3. Set up a local repo to push to the secondary and pull from the secondary
  4. Destroy the primary and promote the secondary node to primary by following the GitLab Geo Disaster Recovery Instructions
    1. Connect a local repo to this new primary and make sure you can push and pull
  5. Test HTTP/HTTPS to make sure Geo is working after each step If you are using self-signed certificate checkout mkcert to make this an easy process.
    1. Set up custom / self signed certificates
    2. Start with HTTP on both servers and change to the following:
    3. Primary use HTTP, secondary HTTPS
    4. Primary use HTTPS, secondary HTTP
    5. HTTPS on both
    6. Back to HTTP
  6. Update your Geo setup 3 times and make sure at least they are new minor versions. Do this throughout the module
    1. from version __ to version __
    2. from version __ to version __
    3. from version __ to version __
  7. Set up a Docker Registry on a secondary Geo node to mirror the primary one
  8. Set up custom ports for SSH and HTTP (If you haven't done this before)
  9. With and without license
    1. Remove your license on the primary
    2. Check what happens (configs,log files, etc.)
    3. Add your license back to the primary
    4. Check what happens (configs,log files, etc.)

Stage 3: Tickets

  • Done with Stage 3

  1. Find 5 Solved tickets to get a sense of what gets asked and how others have done troubleshooting in this area.

    1. https://gitlab.zendesk.com/agent/tickets/588572
    2. https://gitlab.zendesk.com/agent/tickets/642957
    3. __
    4. __
    5. __

  2. Answer 10 tickets on this module's topic and paste the links here. Do this even if a ticket seems too advanced for you to answer. Find the answers from an expert and relay them to the customers.

    1. __
    2. __
    3. __
    4. __
    5. __ https://gitlab.zendesk.com/agent/tickets/623219
    6. __ https://gitlab.zendesk.com/agent/tickets/633049
    7. __ https://gitlab.zendesk.com/agent/tickets/641164
    8. __ https://gitlab.zendesk.com/agent/tickets/634040
    9. __ https://gitlab.zendesk.com/agent/tickets/621162
    10. __ https://gitlab.zendesk.com/agent/tickets/582811

Stage 4: Pair on Customer Calls

  • Done with Stage 4
  1. Calls where we help a Customer troubleshoot Geo
    1. call with @ anton
    2. call with @ jfarmiloe
    3. call with ___

Penultimate stage: Review

Any updates or improvements needed? If there are any dead links, out of date or inaccurate content, missing content whether in this module or in other documentation, list it below as tasks for yourself! Once ready, have a maintainer or manager review.

  • Update ...

Final Stage

  1. Have your trainer review your tickets. If you do not have a trainer, ask an expert to review.

  2. Manager: schedule a call (or integrate into 1:1) to review how the module went.

  3. Bookmark How to ask for support from Geo to know how to ask Geo team for help when working Geo tickets and emergencies.

  4. Update your Support Team yaml file to indicate that you're ready to work on tickets in this knowledge area:

    knowledge_areas:
- name: Geo
  level: 2
Edited by Mike Lockhart | GitLab