Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Ansible Playbook Essentials

You're reading from   Ansible Playbook Essentials Design automation blueprints to manage your multitier infrastructure

Arrow left icon
Product type Paperback
Published in Aug 2015
Publisher
ISBN-13 9781784398293
Length 168 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Gourav Shah Gourav Shah
Author Profile Icon Gourav Shah
Gourav Shah
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface Setting Up the Learning Environment FREE CHAPTER 1. Blueprinting Your Infrastructure 2. Going Modular with Ansible Roles 3. Separating Code and Data – Variables, Facts, and Templates 4. Bringing In Your Code – Custom Commands and Scripts 5. Controlling Execution Flow – Conditionals 6. Iterative Control Structures – Loops 7. Node Discovery and Clustering 8. Encrypting Data with Vault 9. Managing Environments 10. Orchestrating Infrastructure with Ansible A. References
Index

Automating events and actions with handlers

Let's assume that we are managing Nginx manually, and that we have to change the port that Nginx listens to from the default site to 8080. What would we do to make this happen? Sure, we would edit the default.conf file and change the port from 80 to 8080. However, would that be enough? Would that make Nginx listen to port 8080 immediately after editing this file? The answer is no. There is one more step involved. Let's take a look at the following screenshot:

Automating events and actions with handlers

When we change a configuration file, we will typically also restart/reload the service so that it reads our modifications and applies those.

So far, so good. Now let's come back to our Ansible code. We are going to run this code in an automated fashion on a large number of servers, possibly hundreds. Considering this, it's not feasible for us to log in to each system to restart services after every change. This defeats the purpose of automating the process. Now, how do we...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime