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.

Related Content you might be interested in

Current Title:

Small book image
Learning DevOps - Second Edition
Mikael Krief
Mar, 2022 | 560 pages
Small book image
Terraform Cookbook
Mikael Krief
Oct, 2020 | 366 pages
Small book image
Terraform Cookbook
Mikael Krief
Aug, 2023 | 634 pages
Small book image
HashiCorp Infrastructure Automation Certification Guide
Ravi Mishra
Jul, 2021 | 350 pages
Table of Contents (25 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Download the example code files
Code in Action
Download the color images
Conventions used
Get in touch
Share Your Thoughts
1
Section 1: DevOps and Infrastructure as Code
Section 1: DevOps and Infrastructure as Code
Free Chapter
2
Chapter 1: The DevOps Culture and Infrastructure as Code Practices
Chapter 1: The DevOps Culture and Infrastructure as Code Practices
Getting started with DevOps
Implementing CI/CD and continuous deployment
Understanding IaC practices
Summary
Questions
Further reading
3
Chapter 2: Provisioning Cloud Infrastructure with Terraform
Chapter 2: Provisioning Cloud Infrastructure with Terraform
Technical requirements
Installing Terraform
Configuring Terraform for Azure
Writing a Terraform script to deploy an Azure infrastructure
Running Terraform for deployment
Understanding the Terraform life cycle with different command-line options
Protecting the state file with a remote backend
Summary
Questions
Further reading
4
Chapter 3: Using Ansible for Configuring IaaS Infrastructure
Chapter 3: Using Ansible for Configuring IaaS Infrastructure
Technical requirements
Installing Ansible
Creating an Ansible inventory
Executing the first playbook
Executing Ansible
Protecting data with Ansible Vault
Using a dynamic inventory for an Azure infrastructure
Summary
Questions
Further reading
5
Chapter 4: Optimizing Infrastructure Deployment with Packer
Chapter 4: Optimizing Infrastructure Deployment with Packer
Technical requirements
An overview of Packer
Creating Packer templates for Azure VMs with scripts
Using Ansible in a Packer template
Executing Packer
Writing Packer templates with HCL format
Using a Packer image with Terraform
Summary
Questions
Further reading
6
Chapter 5: Authoring the Development Environment with Vagrant
Chapter 5: Authoring the Development Environment with Vagrant
Technical requirements
Installing Vagrant
Writing a Vagrant configuration file
Creating a local VM using the Vagrant CLI
Summary
Questions
Further reading
7
Section 2: DevOps CI/CD Pipeline
Section 2: DevOps CI/CD Pipeline
8
Chapter 6: Managing Your Source Code with Git
Chapter 6: Managing Your Source Code with Git
Technical requirements
Overviewing Git and its principal command lines
Understanding the Git process and Gitflow pattern
Summary
Questions
Further reading
9
Chapter 7: Continuous Integration and Continuous Delivery
Chapter 7: Continuous Integration and Continuous Delivery
Technical requirements
CI/CD principles
Using a package manager in the CI/CD process
Using Jenkins for CI/CD implementation
Using Azure Pipelines for CI/CD
Using GitLab CI
Summary
Questions
Further reading
10
Chapter 8: Deploying Infrastructure as Code with CI/CD Pipelines
Chapter 8: Deploying Infrastructure as Code with CI/CD Pipelines
Technical requirements
Running Packer in Azure Pipelines
Running Terraform and Ansible in Azure Pipelines
Summary
Questions
Further reading
11
Section 3: Containerized Microservices with Docker and Kubernetes
Section 3: Containerized Microservices with Docker and Kubernetes
12
Chapter 9: Containerizing Your Application with Docker
Chapter 9: Containerizing Your Application with Docker
Technical requirements
Installing Docker
Creating a Dockerfile
Building and running a container on a local machine
Pushing an image to Docker Hub
Pushing a Docker image to a private registry (ACR)
Deploying a container to ACI with a CI/CD pipeline
Using Docker for running command-line tools
Getting started with Docker Compose
Deploying Docker Compose containers in ACI
Summary
Questions
Further reading
13
Chapter 10: Managing Containers Effectively with Kubernetes
Chapter 10: Managing Containers Effectively with Kubernetes
Technical requirements
Installing Kubernetes
A first example of Kubernetes application deployment
Using Helm as a package manager
Publishing a Helm chart in a private registry (ACR)
Using AKS
Creating a CI/CD pipeline for Kubernetes with Azure Pipelines
Monitoring applications and metrics in Kubernetes
Summary
Questions
Further reading
14
Section 4: Testing Your Application
Section 4: Testing Your Application
15
Chapter 11: Testing APIs with Postman
Chapter 11: Testing APIs with Postman
Technical requirements
Creating a Postman collection with requests
Using environments and variables to dynamize requests
Writing Postman tests
Executing Postman request tests locally
Understanding the Newman concept
Preparing Postman collections for Newman
Running the Newman command line
Integration of Newman in the CI/CD pipeline process
Summary
Questions
Further reading
16
Chapter 12: Static Code Analysis with SonarQube
Chapter 12: Static Code Analysis with SonarQube
Technical requirements
Exploring SonarQube
Installing SonarQube
Real-time analysis with SonarLint
Executing SonarQube in a CI process
Summary
Questions
Further reading
17
Chapter 13: Security and Performance Tests
Chapter 13: Security and Performance Tests
Technical requirements
Applying web security and penetration testing with ZAP
Running performance tests with Postman
Summary
Questions
Further reading
18
Section 5: Taking DevOps Further/More on DevOps
Section 5: Taking DevOps Further/More on DevOps
19
Chapter 14: Security in the DevOps Process with DevSecOps
Chapter 14: Security in the DevOps Process with DevSecOps
Technical requirements
Testing Azure infrastructure compliance with Chef InSpec
Keeping sensitive data safe with HashiCorp Vault
Summary
Questions
Further reading
20
Chapter 15: Reducing Deployment Downtime
Chapter 15: Reducing Deployment Downtime
Technical requirements
Reducing deployment downtime with Terraform
Understanding blue-green deployment concepts and patterns
Applying blue-green deployments on Azure
Introducing feature flags
Using an open source framework for feature flags
Using the LaunchDarkly solution
Summary
Questions
Further reading
21
Chapter 16: DevOps for Open Source Projects
Chapter 16: DevOps for Open Source Projects
Technical requirements
Storing source code in GitHub
Contributing to open source projects using pull requests
Managing the changelog file and release notes
Sharing binaries in GitHub releases
Getting started with GitHub Actions
Analyzing code with SonarCloud
Detecting security vulnerabilities with WhiteSource Bolt
Summary
Questions
Further reading
22
Chapter 17: DevOps Best Practices
Chapter 17: DevOps Best Practices
Automating everything
Choosing the right tool
Writing all your configuration in code
Designing the system architecture
Building a good CI/CD pipeline
Integrating tests
Shifting security left with DevSecOps
Monitoring your system
Evolving project management
Summary
Questions
Further reading
23
Assessments
Chapter 1: The DevOps Culture and Infrastructure as Code Practices
Chapter 2: Provisioning Cloud Infrastructure with Terraform
Chapter 3: Using Ansible for Configuring IaaS Infrastructure
Chapter 4: Optimizing Infrastructure Deployment with Packer
Chapter 5: Authoring the Development Environment with Vagrant
Chapter 6: Managing Your Source Code with Git
Chapter 7: Continuous Integration and Continuous Delivery
Chapter 8: Deploying Infrastructure as Code with CI/CD Pipelines
Chapter 9: Containerizing Your Application with Docker
Chapter 10: Managing Containers Effectively with Kubernetes
Chapter 11: Testing APIs with Postman
Chapter 12: Static Code Analysis with SonarQube
Chapter 13: Security and Performance Tests
Chapter 14: Security in the DevOps Process with DevSecOps
Chapter 15: Reducing Deployment Downtime
Chapter 16: DevOps for Open Source Projects
Chapter 17: DevOps Best Practices
Why subscribe?
24
Other Books You May Enjoy
Other Books You May Enjoy
Packt is searching for authors like you
Share Your Thoughts

Managing the changelog file and release notes

When we host a project as open source, it is good practice to provide information to users about the changes that are being applied to it as they occur. This change logging system (also called release notes) is all the more important if, in addition to the source code, our repository also publicly provides a binary of the application since the use of this binary is dependent on its different versions and code changes.

Logically, we could find the history of code changes by navigating through the history of Git commits. However, this would be too tedious and time-consuming for Git novices. For these reasons, we will indicate the change in history with the code versions in a text file that can be read by everyone. This file has no fixed nomenclature or formalism, but for simplicity, we have decided to call it CHANGELOG.md.

So, this changelog file is a text file in markdown format, which is easy to edit with simple formatting and is...

Previous Section
End of Section 5
Next Section