Ansible for DevOps


Ansible for DevOps

Ansible for DevOps

 Since the beginning of networked computing, deploying and managing servers reliably and efficiently has been a challenge. Historically, system administrators have typically been walled off from the developers and users who interact with the systems they administer, and so they have had to manage servers by hand, installing software, changing configurations, and administering services on individual servers.

    As data centers grew, and hosted applications became more complex, administrators realized they couldn’t scale their manual systems management as fast as the applications they were enabling. That’s why server provisioning and configuration management tools came to flourish. Server virtualization brought large-scale infrastructure management to the fore, and the number of servers managed by one admin (or by a small team of admins), has grown by an order of magnitude. Instead of deploying, patching, and destroying every server by hand, admins now are expected to bring up new servers, either automatically or with minimal intervention. Large-scale IT deployments now may involve hundreds or thousands of servers; in many of the largest environments, server provisioning, configuration, and decommissioning are all entirely automated.


Modern infrastructure management

    As the systems that run applications become an ever more complex and integral part of the software they run, application developers themselves have begun to integrate their work more fully with operations personnel. In many companies, development and operations work is almost fully integrated. Indeed, this integration is a requirement for modern test-driven application design. As a software developer by trade, and a sysadmin by necessity, I have seen the power in uniting development and operations more commonly referred to now as DevOps. When developers begin to think of infrastructure as part of their application, stability and performance become normative. When sysadmins (most of whom have intermediate to advanced knowledge of the applications and languages being used on servers they manage) work tightly with developers, development velocity is improved, and more time is spent doing ‘fun’ activities like performance tuning, experimentation, and getting things done, and less time putting out fires.

The Full Stack Developer Essential Guide


Table Of Contents


Chapter 1 - Getting Started with Ansible

Chapter 2 - Local Infrastructure Development: Ansible and Vagrant

Chapter 3 - Ad-Hoc Commands

Chapter 4 - Ansible Playbooks

Chapter 5 - Ansible Playbooks - Beyond the Basics

Chapter 6 - Playbook Organization - Roles and Includes

Chapter 7 - Inventories

Chapter 9 - Deployments with Ansible

Chapter 10 - Server Security and Ansible

Chapter 11 - Automating Your Automation - Ansible Tower and CI/CD

Appendix A - Using Ansible on Windows workstations

Appendix B - Ansible Best Practices and Conventions

Download full PDF in Comment section



Previous Post Next Post