Gitlab hero border pattern left svg Gitlab hero border pattern right svg

System Requirements for GitLab Professional Services Training Sessions

Attendee pre-training system requirements

A few tasks are needed to ensure a smooth learning experience. Most of the training modules include a presentation and demo. The curriculum is heavily practice-based. Whether a local machine is used or an instance provided by Gitlab, it's important to review the following requirements ahead of the training session.

Attendee local setup

  • Operating System: Attendees must bring their own laptop or desktop that runs either macOS, Linux, or Windows operating systems.
  • Internet Access: Attendees need Internet access with the ability to reach websites via http/https.

GitLab Demo Cloud Access

Unique invitation codes are handed out on the first day of class by the instructors. Access to an instance with all paid features and capabilities turned on is provided during the training session, features not always available with the free version (GitLab CE) of GitLab. Ensure both the invitation site and the GitLab Demo Cloud URLs are reachable, resolving firewall issues ahead of training.

Course-Specific Requirements

GitLab with Git Basics

  • GitLab Access: Attendees require access to the GitLab Demo Cloud environment to participate in the hands-on activities.
  • Verify Git Installation: The following steps verify whether on the local machine Git is installed:
    • macOS: Type git in the Terminal application. If it’s not installed, it will prompt you to install it.
    • Linux: sudo yum install git-all or sudo apt-get install git-all
    • Windows 10: Windows Subsystem for Linux
    • Other versions of Windows: See Git for Windows
  • Generate SSH keys: Follow the instructions here
  • Browser: No Internet Explorer

GitLab CI/CD Training

  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Browser: No Internet Explorer
  • Required Runner Executor: Shell executor required to complete Hands On activities for this course. With a different executor on the local machine, the instructor will demo lab exercises for the entire class.

GitLab for System Administrators

  • Managed Lab: An option for orgainzations is to have GitLab provide virtual machines (VMs). Alternatively, VMs can be installed on local machines with a GitLab sandbox instance installed there. Two VMs are the requirement for this class, one for a GitLab instance and the second for a Runner, both with a FQFN (Fully Qualified Domain Name). The GitLab and the Runner VMs will need access to each other through ports 80 and 443. Access using the FQDNs in a browser from a workstation is required. Either RedHat, CentOS or Ubuntu is supported for the course. Minimum workstation requirements are 4x CPU and 4GB RAM. It is suggested to use 8x CPU and 16GB RAM for the GitLab Instances per student. Students should be able to have ssh access to each VM and have rights for incidental root access.
  • Docker: The installation of Docker when virtual machines (VMs) from GitLab are provided, an option your organization can choose for the training session, is not required. Alternatively Docker installation on a local system affords installation of a GitLab sandbox instance. What's important is installing Docker prior to the start of the training session for full participation with hands-on activities. Should any of these options be unavailable, the trainer demonstrates all steps of every hands-on exercise during the session. To install Docker on a local machine, start here. SSH Access: SSH access to the Lab VMs is required. For *nix workstations (Mac or Linux), this is usually defaulted into the terminal. For Windows workstations we recomend git bash. Git for Windows here Windows 10 or above can be used, but is not the preferred method. If your OS does not have a pre-installed SSH client, you will need to install it prior to class.
  • Browser: Internet Explorer is not supported

Project Management with GitLab

  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Browser: No Internet Explorer

GitLab Security Essentials

  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Browser: No Internet Explorer
  • Runner Executor Needed: Shell needed to complete Hands On activities for this course. If a different executor is ready on your local machine, notify the instructor and we can plan on demoing the lab exercises.

GitLab InnerSourcing Training

Licenses: The following features covered in this session are only available for Silver/Gold & Premier/Ultimate GitLab Licenses:
  • Multi-Level Epics
  • Roadmaps
  • Incremental Rollout
  • Package Registry
  • Container Registry
  • Dependency Proxy
  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Browser: No Internet Explorer
Open in Web IDE View source