Learning DevOps

Mikael Krief

• Editore: Packt Publishing
• Anno: 2022
• ISBN:
  9781801813464
• Edizione: 2
• Argomento: Informatica
• Categoria: Sviluppo software

Implement modern DevOps techniques to increase business productivity, agility, reliability, security, and scalabilityKey Features• Learn how to use business resources effectively for improved productivity and collaboration• Use infrastructure as code practices to build large-scale cloud infrastructure• Leverage the ultimate open source DevOps tools to achieve continuous integration and continuous delivery (CI/CD)Book DescriptionIn 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.What you will learn• Understand the basics of infrastructure as code patterns and practices• Get an overview of Git command and Git flow• Install and write Packer, Terraform, and Ansible code for provisioning and configuring cloud infrastructure based on Azure examples• Use Vagrant to create a local development environment• Containerize applications with Docker and Kubernetes• Apply DevSecOps for testing compliance and securing DevOps infrastructure• Build DevOps CI/CD pipelines with Jenkins, Azure Pipelines, and GitLab CI• Explore blue-green deployment and DevOps practices for open sources projectsWho this book is forIf you are an application developer or a system administrator interested in understanding continuous integration, continuous delivery, and containerization with DevOps tools and techniques, this book is for you. Knowledge of DevOps fundamentals and Git principles is required.

Section 1: DevOps and Infrastructure as Code

The objectives of part one are to present the DevOps culture and to provide all the keys for the best infrastructure as code practices. This part explains the application of DevOps to cloud infrastructure, showing provisioning using Terraform and configuration with Ansible. Then, we improve on this by templating this infrastructure with Packer.

This section comprises the following chapters:

• Chapter 1, The DevOps Culture and Infrastructure as Code Practices
• Chapter 2, Provisioning Cloud Infrastructure with Terraform
• Chapter 3, Using Ansible to Configure IaaS Infrastructure
• Chapter 4, Optimizing Infrastructure Deployment with Packer
• Chapter 5, Authoring the Development Environment with Vagrant

Chapter 1: The DevOps Culture and Infrastructure as Code Practices

DevOps, a term that we hear more and more in enterprises with phrases such as We do DevOps or We use DevOps tools, is the contraction of the words "Development" and "Operations."

DevOps is a culture that's different from traditional corporate cultures and requires a change in mindset, processes, and tools. It is often associated with continuous integration (CI) and continuous delivery (CD) practices, which are software engineering practices, but also with Infrastructure as Code (IaC), which consists of codifying the structure and configuration of infrastructure.

In this chapter, we will see what DevOps culture is, what DevOps principles are, and the benefits they bring to a company. Then, we will explain CI/CD practices and, finally, we will detail IaC with its patterns and practices.

In this chapter, we will cover the following topics:

• Getting started with DevOps
• Implementing CI/CD and continuous deployment
• Understanding IaC practices

Check out the following video to view the Code in Action: https://bit.ly/3JJAMAb

Getting started with DevOps

The term DevOps was introduced in 2007-2009 by Patrick Debois, Gene Kim, and John Willis, and it represents the combination of Development (Dev) and Operations (Ops). It has given rise to a movement that advocates bringing developers and operations together within teams. This delivers added business value to users more quickly, which makes it more competitive in the market.

DevOps culture is a set of practices that reduce the barriers between developers, who want to innovate and deliver faster, and operations, who want to guarantee the stability of production systems and the quality of the system changes they make.

DevOps culture is also the extension of agile processes (Scrum, XP, and so on), which makes it possible to reduce delivery times and already involves developers and business teams. However, they are often hindered because of the non-inclusion of Ops in the same teams.

The communication and this link between Dev and Ops allows a better follow-up of end-to-end production deployments and more frequent deployments that are of higher quality, saving money for the company.

To facilitate this collaboration and to improve communication between Dev and Ops, there are several key elements in the processes that must be put in place, as shown here:

• More frequent application deployments with integration and continuous delivery (called CI/CD).
• The implementation and automation of unitary and integration tests, with a process focused on behavior-driven design (BDD) or test-driven design (TDD).
• The implementation of a means of collecting feedback from users.
• Monitoring applications and infrastructure.

The DevOps movement is based on three axes:

• The culture of collaboration: This is the very essence of DevOps – the fact that teams are no longer separated by silos specialization (one team of developers, one team of Ops, one team of testers, and so on). However, these people are brought together by making multidisciplinary teams that have the same objective: to deliver added value to the product as quickly as possible.
• Processes: To expect rapid deployment, these teams must follow development processes from agile methodologies with iterative phases that allow for better functionality, quality, and rapid feedback. These processes should not only be integrated into the development workflow with continuous integration, but also into the deployment workflow with continuous delivery and deployment. The DevOps process is divided into several phases:

A. Planning and prioritizing functionalities

B. Development

C. Continuous integration and delivery

D. Continuous deployment

E. Continuous monitoring

These phases are carried out cyclically and iteratively throughout the life of the project.

• Tools: The choice of tools and products used by teams is very important in DevOps. Indeed, when teams were separated into Dev and Ops, each team used their specific tools – deployment tools for developers and infrastructure tools for Ops – which further widened communication gaps.

With teams that bring development and operations together, and with this culture of unity, the tools that are used must be usable and exploitable by all members.

Developers need to integrate with the monitoring tools that are used by Ops teams to detect performance problems as early as possible, and with security tools provided by Ops to protect access to various resources.

Ops, on the other hand, must automate the process of creating and updating the infrastructure and integrate the code into a code manager. This is called IaC, but this can only be done in collaboration with developers who know the infrastructure that's needed for applications. Ops must also be integrated into application release processes and tools.

The following diagram illustrates the three axes of DevOps culture – the collaboration between Dev and Ops, the processes, and the use of tools:

Figure 1.1 – The DevOps culture union

So, we can go back to DevOps culture with Donovan Brown's definition (http://donovanbrown.com/post/what-is-devops):

"DevOps is the union of people, processes, and products to enable continuous delivery of value to our end users."

The ...