Book Image

Hands-On DevOps with Vagrant

By : Alex Braunton
Book Image

Hands-On DevOps with Vagrant

By: Alex Braunton

Overview of this book

Hands-On DevOps with Vagrant teaches you how to use Vagrant as a powerful DevOps tool and gives an overview of how it fits into the DevOps landscape. You will learn how to install VirtualBox and Vagrant in Windows, macOS, and Linux. You will then move on to understanding Vagrant commands, discovering its boxes and Vagrant Cloud. After getting to grips with the basics, the next set of chapters helps you to understand how to configure Vagrant, along with networking. You will explore multimachine, followed by studying how to create multiple environments and the communication between them. In addition to this, you will cover concepts such as Vagrant plugins and file syncing. The last set of chapters provides insights into provisioning shell scripts, also guiding you in how to use Vagrant with configuration management tools such as Chef, Ansible, Docker, Puppet, and Salt. By the end of this book, you will have grasped Vagrant’s features and how to use them for your benefit with the help of tips and tricks.
Table of Contents (21 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Salt options available within Vagrant


As Salt is essentially built into Vagrant, there are many options available. There are currently six different types of options available to manage in the Vagrantfile. These option types are:

  • Install
  • Minion
  • Master
  • Execute states
  • Execute runners
  • Output control

Let's break these option groups down to see what specific options are available to configure.

 

Install options

These are fairly generic options and are used to manage the installation of Salt. Here are the options available:

  • install_master: If this option is set to true, it will install the salt-master daemon
  • no_minion: If set to true, this options will not install the minion
  • install_syndic: Dictates whether to install salt-syndic
  • install_type: Dictates the installation channel when installing via package manager, such as stable, daily, or testing
  • install_args: When using Git, you can specify additional args, such as branch or tag
  • always_install: Dictates whether to install binaries, even if they are already detected...