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

Too much or not enough automation

Automation is a core tenet of DevOps. Let’s face it—automation is the greatest way of making our work easier, more efficient, and fun.

But organizations can sometimes become too reliant on it, leading to a lack of human oversight and accountability. If you automate too many things, you will fail to catch any errors that could have been spotted by a human if you’d embedded them into the process. That’s why we have peer review processes in place to ensure we don’t miss something that tests or any integration testing tool didn’t catch. That’s also why many organizations prefer to manually sign off the terraform apply process before it actually gets deployed.

On the other hand, if you don’t automate anything, you expose yourself to accidental errors, as we humans are not very good with boring repeatable tasks. And that’s the point here: identify repeatable tasks for automation.

To...