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

Creating the www playbook

We created a site-wide playbook and used an include statement to call another playbook by the name www.yml. We will now create this file with one play, which maps our web server hosts to the Nginx role:

---
#www.yml : playbook for web servers
- hosts: www
  remote_user: vagrant
  sudo: yes
  roles:
     - nginx

The above code works as follows:

  • Run this code on any host that maps to the [www] group specified in the hosts file.
  • For each directory inside the roles/nginx/* file, include roles/nginx/*/main.yml to the play. This includes tasks, handlers, vars, meta, default, and so on. This is where the auto include rules apply.

The default and custom role paths

By default, Ansible looks inside the roles/ subdirectory of the project that we create playbooks for. Being top-class devops engineers, we will follow the best practice to have a centralized, version-controlled repository to store all your roles. We may also end up reusing the roles created by community. Once we do...

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