Book Image

The Linux DevOps Handbook

By : Damian Wojsław, Grzegorz Adamowicz
3.5 (2)
Book Image

The Linux DevOps Handbook

3.5 (2)
By: Damian Wojsław, Grzegorz Adamowicz

Overview of this book

The Linux DevOps Handbook is a comprehensive resource that caters to both novice and experienced professionals, ensuring a strong foundation in Linux. This book will help you understand how Linux serves as a cornerstone of DevOps, offering the flexibility, stability, and scalability essential for modern software development and operations. You’ll begin by covering Linux distributions, intermediate Linux concepts, and shell scripting to get to grips with automating tasks and streamlining workflows. You’ll then progress to mastering essential day-to-day tools for DevOps tasks. As you learn networking in Linux, you’ll be equipped with connection establishment and troubleshooting skills. You’ll also learn how to use Git for collaboration and efficient code management. The book guides you through Docker concepts for optimizing your DevOps workflows and moves on to advanced DevOps practices, such as monitoring, tracing, and distributed logging. You’ll work with Terraform and GitHub to implement continuous integration (CI)/continuous deployment (CD) pipelines and employ Atlantis for automated software delivery. Additionally, you’ll identify common DevOps pitfalls and strategies to avoid them. By the end of this book, you’ll have built a solid foundation in Linux fundamentals, practical tools, and advanced practices, all contributing to your enhanced Linux skills and successful DevOps implementation.
Table of Contents (20 chapters)
1
Part 1: Linux Basics
6
Part 2: Your Day-to-Day DevOps Tools
12
Part 3: DevOps Cloud Toolkit

Failure to adopt a collaborative culture

DevOps is all about collaboration and breaking down silos between teams. However, many organizations struggle to adopt a culture of collaboration, leading to miscommunications, delays, and, ultimately, project failures. The importance of collaboration in DevOps with examples of how a lack of collaboration can derail projects would certainly be a good idea for a separate chapter.

Silos refer to isolated teams or departments that do not communicate or collaborate effectively with each other, leading to poor coordination and hindering overall productivity and efficiency. Several possible reasons why organizations fail to adopt a collaborative culture in DevOps include the following: lack of leadership, siloed structure from the get-go, lack of trust, and lack of communication. Let’s take a look at each of these and try to find a good way out.

Lack of leadership

A common challenge is when leadership does not prioritize or actively...