--- title: "SAI PRANEETH BHATTU (@saipraneethbhattu) | Hashnode" description: "DevOps & Cloud Enthusiast. Read the latest articles by SAI PRANEETH BHATTU on Hashnode." url: "https://hashnode.com/@saipraneethbhattu" --- @saipraneethbhattu # SAI PRANEETH BHATTU @saipraneethbhattu · Detroit, Michigan · Joined February 2026 DevOps & Cloud Enthusiast [Website](https://saipraneethbhattu.me/) ### [Package Managers in Linux: RPM, Yum, DPKG and APT Explained](https://saipraneethbhattu.hashnode.dev/package-managers-in-linux-rpm-yum-dpkg-and-apt-explained?utm_source=hashnode&utm_medium=feed) Sooner or later, every Linux user needs to install software. On Windows you download an installer and click through it. On Linux the story is different, and it is built around something called a package manager. In this lecture we will work out why package managers exist, what a package really is, and how the two big families of tools work. We will cover RPM and Yum on the Red Hat side, then DPKG and APT on the Debian side. We will finish by comparing apt and apt-get. 13 min read · [saipraneethbhattu.hashnode.dev](https://saipraneethbhattu.hashnode.dev/package-managers-in-linux-rpm-yum-dpkg-and-apt-explained?utm_source=hashnode&utm_medium=feed) [Oct 23](https://hashnode.com/posts/package-managers-in-linux-rpm-yum-dpkg-and-apt-explained/6adbb62f49d34d8b5f22e539) ### [Understanding the Linux Kernel, Boot Process and File System Hierarchy](https://saipraneethbhattu.hashnode.dev/understanding-the-linux-kernel-boot-process-and-file-system-hierarchy?utm_source=hashnode&utm_medium=feed) Let us settle in for a session that goes right to the heart of how Linux actually works. We are going to start at the very bottom, with the kernel, and slowly build our way up through hardware management, the boot process, run levels, file types, and finally the file system hierarchy. By the end of this, when you type a command in a Linux shell, you should have a mental picture of what is happening behind the scenes. 30 min read · [saipraneethbhattu.hashnode.dev](https://saipraneethbhattu.hashnode.dev/understanding-the-linux-kernel-boot-process-and-file-system-hierarchy?utm_source=hashnode&utm_medium=feed) [Oct 21](https://hashnode.com/posts/understanding-the-linux-kernel-boot-process-and-file-system-hierarchy/6ad83c67393853b7be93ccec) ### [Stop Writing Repetitive Playbooks: Ansible Tags, Variables, Loops, Handlers and Conditions Decoded](https://saipraneethbhattu.hashnode.dev/stop-writing-repetitive-playbooks-ansible-tags-variables-loops-handlers-and-conditions-decoded?utm_source=hashnode&utm_medium=feed) Once you have written your first few Ansible playbooks, installed some packages, and started a couple of services, a natural question comes up: what else can Ansible do? The answer is quite a lot. This article walks through six features that turn a basic Ansible setup into something genuinely powerful: the Setup module, Tags, Variables, Loops, Handlers, and Conditional tasks. Each one builds on what you already know, and together they give you the tools to manage complex, real-world server environments cleanly and efficiently. Before going further, the environment being used here has one Ansible master and multiple worker nodes. Two are grouped as prod and two as dev inside /etc/ansible/hosts. SSH key-based authentication is already configured between the master and all worker nodes. If any of that is not set up yet, revisit passwordless SSH setup and inventory configuration before continuing. 15 min read · [saipraneethbhattu.hashnode.dev](https://saipraneethbhattu.hashnode.dev/stop-writing-repetitive-playbooks-ansible-tags-variables-loops-handlers-and-conditions-decoded?utm_source=hashnode&utm_medium=feed) [Jun 21](https://hashnode.com/posts/stop-writing-repetitive-playbooks-ansible-tags-variables-loops-handlers-and-conditions-decoded/6a37b8322f65399e00adf40c) ### [Ansible Playbooks Explained: From First YAML File to Managing Real Servers](https://saipraneethbhattu.hashnode.dev/ansible-playbooks-explained-from-first-yaml-file-to-managing-real-servers?utm_source=hashnode&utm_medium=feed) If you have already run a few Ansible ad hoc commands and seen how they work, you already understand the core idea: one command, many servers. But ad hoc commands only take you so far. When you need to install software, start services, create users, copy files, and print confirmation messages, all in one automated run across multiple servers, that is when you move to playbooks. Playbooks are where Ansible truly earns its place in a DevOps workflow. Everything you do in Ansible at scale, you do through playbooks. 13 min read · [saipraneethbhattu.hashnode.dev](https://saipraneethbhattu.hashnode.dev/ansible-playbooks-explained-from-first-yaml-file-to-managing-real-servers?utm_source=hashnode&utm_medium=feed) [Jun 19](https://hashnode.com/posts/ansible-playbooks-explained-from-first-yaml-file-to-managing-real-servers/6a3503818a730ef24935d0f5) ### [You Have 400 Servers to Configure. Now What? Let Ansible Do the Work.](https://saipraneethbhattu.hashnode.dev/you-have-400-servers-to-configure-now-what-let-ansible-do-the-work?utm_source=hashnode&utm_medium=feed) Picture this. You have four EC2 instances running in your AWS account, and someone asks you to install Apache on all four of them. What do you do? The obvious answer most people go with is SSH into each machine, run the install command, repeat. Simple enough when it is four servers. But what happens when it is forty? Or four hundred? In a real enterprise environment, that number is not exaggerated at all. That is exactly the problem that Ansible was built to solve. And once you understand what it does and how it thinks, you will wonder how anyone managed large infrastructure without it. 12 min read · [saipraneethbhattu.hashnode.dev](https://saipraneethbhattu.hashnode.dev/you-have-400-servers-to-configure-now-what-let-ansible-do-the-work?utm_source=hashnode&utm_medium=feed) [Jun 18](https://hashnode.com/posts/you-have-400-servers-to-configure-now-what-let-ansible-do-the-work/6a33bd7e02152832f454d765)