Book Image

Mastering GitLab 12

By : Joost Evertse
Book Image

Mastering GitLab 12

By: Joost Evertse

Overview of this book

GitLab is an open source repository management and version control toolkit with functions for enterprises and personal software projects. It offers configurability options, extensions, and APIs that make it an ideal tool for enterprises to manage the software development life cycle. This book begins by explaining GitLab options and the components of the GitLab architecture. You will learn how to install and set up GitLab on-premises and in the cloud, along with understanding how to migrate code bases from different systems, such as GitHub, Concurrent Versions System, Team Foundation Version Control, and Subversion. Later chapters will help you implement DevOps culture by introducing the workflow management tools in GitLab and continuous integration/continuous deployment (CI/CD). In addition to this, the book will guide you through installing GitLab on a range of cloud platforms, monitoring with Prometheus, and deploying an environment with GitLab. You'll also focus on the GitLab CI component to assist you with creating development pipelines and jobs, along with helping you set up GitLab runners for your own project. Finally, you will be able to choose a high availability setup that fits your needs and helps you monitor and act on results obtained after testing. By the end of this book, you will have gained the expertise you need to use GitLab features effectively, and be able to integrate all phases in the development process.
Table of Contents (30 chapters)
Free Chapter
Section 1: Install and Set Up GitLab On-Premises or in the Cloud
Section 2: Migrating Data from Different Locations
Section 3: Implement the GitLab DevOps Workflow
Section 4: Utilize GitLab CI and CI Runners
Section 5: Scale the Server Infrastructure (High Availability Setup)

Managing a Hybrid HA Environment

In the previous chapter, we created a basic scalable GitLab architecture using Terraform and Ansible. In this chapter, we will continue with the same structure, but we will change some things and create even more resiliency. One of the weak points of the architecture we first designed was that the frontend servers had more than one GitLab component installed, which could prove to be a problem if one component breaks down. We will run the Sidekiq component on another server to mitigate this risk. Another weakness was the shared filesystem. Network File System (NFS) is known to have some performance and file-locking problems; GitLab has developed Gitaly as a replacement, and we will install it in this chapter. Another issue is that there was no monitoring available in the basic scalable architecture. We will install that in this chapter as well.