Book Image

Learning DevOps

By : Mikael Krief
Book Image

Learning DevOps

By: Mikael Krief

Overview of this book

The implementation of DevOps processes requires the efficient use of various tools, and the choice of these tools is crucial for the sustainability of projects and collaboration between development (Dev) and operations (Ops). This book presents the different patterns and tools that you can use to provision and configure an infrastructure in the cloud. You'll begin by understanding DevOps culture, the application of DevOps in cloud infrastructure, provisioning with Terraform, configuration with Ansible, and image building with Packer. You'll then be taken through source code versioning with Git and the construction of a DevOps CI/CD pipeline using Jenkins, GitLab CI, and Azure Pipelines. This DevOps handbook will also guide you in containerizing and deploying your applications with Docker and Kubernetes. You'll learn how to reduce deployment downtime with blue-green deployment and the feature flags technique, and study DevOps practices for open source projects. Finally, you'll grasp some best practices for reducing the overall application lead time to ensure faster time to market. 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 (23 chapters)
Free Chapter
1
Section 1: DevOps and Infrastructure as Code
6
Section 2: DevOps CI/CD Pipeline
9
Section 3: Containerized Applications with Docker and Kubernetes
12
Section 4: Testing Your Application
16
Section 5: Taking DevOps Further

Chapter 2: Provisioning Cloud Infrastructure with Terraform

  1. The language used by Terraform is HashiCorp Configuration Language (HCL).
  2. Terraform's role is an Infrastructure as Code tool.
  3. No. Terraform is not a scripting tool.
  4. The command that allows you to display the installed version is versionterraform version.
  5. The name of the Azure object that connects Terraform to Azure is the Azure service principal.
  6. The three main orders of Terraform are terraform init, terraform plan, and terraform apply.
  7. The Terraform command that allows us to destroy resources is terraform destroy.
  8. We add the --auto-approve option to the terraform apply command.
  9. The purpose of the tfstate file is to keep the resources and their properties throughout the execution of Terraform.
  10. No, it is not a good practice to leave tfstate locally; it must be stored in a protected remote backend.
...