Book Image

Learning DevOps - Second Edition

By : Mikael Krief
Book Image

Learning DevOps - Second Edition

By: Mikael Krief

Overview of this book

In the implementation of DevOps processes, the choice of tools is crucial to the sustainability of projects and collaboration between developers and ops. This book presents the different patterns and tools for provisioning and configuring an infrastructure in the cloud, covering mostly open source tools with a large community contribution, such as Terraform, Ansible, and Packer, which are assets for automation. This DevOps book will show you how to containerize your applications with Docker and Kubernetes and walk you through the construction of DevOps pipelines in Jenkins as well as Azure pipelines before covering the tools and importance of testing. You'll find a complete chapter on DevOps practices and tooling for open source projects before getting to grips with security integration in DevOps using Inspec, Hashicorp Vault, and Azure Secure DevOps kit. You'll also learn about the reduction of downtime with blue-green deployment and feature flags techniques before finally covering common DevOps best practices for all your projects. By the end of this book, you'll have built a solid foundation in DevOps and developed the skills necessary to enhance a traditional software delivery process using modern software delivery tools and techniques.
Table of Contents (25 chapters)
1
Section 1: DevOps and Infrastructure as Code
7
Section 2: DevOps CI/CD Pipeline
11
Section 3: Containerized Microservices with Docker and Kubernetes
14
Section 4: Testing Your Application
18
Section 5: Taking DevOps Further/More on DevOps

Monitoring your system

One of the main elements for the success of a DevOps culture is the implementation of tools that will continuously monitor the state of a system and applications. Monitoring must be implemented at all levels of the system by involving all teams, with the aim of having applications with real added value for the end user.

Indeed, the first component that can be monitored is the application itself, by implementing, as soon as possible, a logging or tracing system that will serve to gather information on the use of the application. Then, we will measure and monitor the state of the infrastructure, such as the random-access memory (RAM) and central processing unit (CPU) level of the virtual machines (VMs) or the network bandwidth. Finally, the last element that must be monitored is the status of DevOps processes. It is, therefore, important to have metrics on the execution of CI/CD pipelines, such as information on the execution time of pipelines, or the number...