Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On DevOps with Vagrant

You're reading from   Hands-On DevOps with Vagrant Implement end-to-end DevOps and infrastructure management using Vagrant

Arrow left icon
Product type Paperback
Published in Oct 2018
Publisher Packt
ISBN-13 9781789138054
Length 232 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Alex Braunton Alex Braunton
Author Profile Icon Alex Braunton
Alex Braunton
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Introduction FREE CHAPTER 2. Installing VirtualBox and Vagrant 3. Command Line-Interface - Vagrant Commands 4. Discovering Vagrant Boxes - Vagrant Cloud 5. Configuring Vagrant Using a Vagrantfile 6. Networking in Vagrant 7. Multi-Machine 8. Exploring Vagrant Plugins and Syncing Files 9. Shell Scripts - Provisioning 10. Ansible - Using Ansible to Provision a Vagrant Box 11. Chef - Using Chef to Provision a Vagrant Box 12. Docker - Using Docker with Vagrant 13. Puppet - Using Puppet to Provision a Vagrant Box 14. Salt - Using Salt to Provision a Vagrant Box 15. Other Book You May Enjoy

Ansible Playbooks


An Ansible Playbook is a configuration file used by Ansible. You can think of it as a Vagrantfile for Vagrant. It uses the YAML (Yet Another Markup Language) markup language as the syntax and is easily readable:

---
 - hosts: all
     sudo: yes
     tasks:
         - name: ensure nginx is at the latest version
             apt: name=nginx state=latest
         - name: start nginx
             service:
                 name: nginx
                 state: started

Let's look at the example playbook we created in the previous section, shown here in the above code block, and dissect it to get a better understanding of what it all means:

  • The first line is always three dashes to signify the beginning of the file.
  • We must then define which hosts this applies to. These can often be defined in the Ansible inventory file by setting a value such as [db] and supplying an IP address for that node.
  • We then set the sudo value to yes as we require sudo/root privileges to install Nginx on the...
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
Banner background image