# Vagrant Overview for MariaDB Users Vagrant is a tool to create and manage development machines (Vagrant *boxes*). They are usually virtual machines on the localhost system, but they could also be Docker containers or remote machines. Vagrant is open source software maintained by HashiCorp and released under the MIT license. Vagrant benefits include simplicity, and a system to create test boxes that is mostly independent from the technology used. For information about installing Vagrant, see [Installation](https://www.vagrantup.com/docs/installation) in Vagrant documentation. In this page we discuss basic Vagrant concepts. ## Vagrant Concepts Following are the core Vagrant concepts: | Concept | Description | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Vagrant Machine | The final environment created from a box. It can be a virtual machine, a container, or a remote cloud server. | | Box | A reusable package used to create Vagrant machines. It can be a base OS image downloaded from Vagrant Cloud or a custom-built template. | | Provider | The underlying virtualization technology that runs the machine (e.g., VirtualBox, VMware, Hyper-V, Docker). | | Provisioner | A tool or script (e.g., Shell, Ansible, Puppet) that automatically installs and configures software on the machine after it is created. | ### Example The above concepts are probably easier to understand with an example. We can use an Ubuntu box as a base to build a Vagrant machine with MariaDB. So we write a Vagrantfile for this purpose. In the Vagrantfile we specify VirtualBox as a provider. And we use the Ansible provisioner to install and configure MariaDB. Once we finish this Vagrantfile, we can run a Vagrant command to start a Vagrant machine, which is actually a VirtualBox VM running MariaDB on Ubuntu. The following diagram should make the example clear: ![vagrant-virtalbox-ansible](/files/BNTBvNMxOiB2vicPIrMF) ### Vagrantfiles A Vagrantfile is a file that describes how to create one or more Vagrant machines. Vagrantfiles use the Ruby language, as well as objects provided by Vagrant itself. A Vagrantfile is often based on a box, which is usually an operating system in which we are going to install our software. For example, one can create a MariaDB Vagrantfile based on the `ubuntu/trusty64` box. A Vagrantfile can describe a box with a single server, like MariaDB, but it can also contain a whole environment, like LAMP. For most practical use cases, having the whole environment in a single box is more convenient. Boxes can be searched in [Vagrant Cloud](https://app.vagrantup.com/boxes/search). Most of their Vagrantfiles are available on GitHub. Searches can be made, among other things, by keyword to find a specific technology, and by provider. ### Providers A provider adds support for creating a specific type of machines. Vagrant comes with several providers, for example: * `VirtualBox` allows one to create virtual machines with VirtualBox. * `Microsoft-Hyper-V` allows one to create virtual machines with Microsoft Hyper-V. * [Docker](/docs/server/server-management/automated-mariadb-deployment-and-administration/docker-and-mariadb.md) allows one to create Docker containers. On non-Linux systems, Vagrant will create a VM to run Docker. Alternative providers are maintained by third parties or sold by HashiCorp. They allow one to create different types of machines, for example using VMWare. Some examples of useful providers, recognized by the community: * [Vagrant AWS Provider](https://github.com/mitchellh/vagrant-aws). * [Vagrant Google Compute Engine (GCE) Provider](https://github.com/mitchellh/vagrant-google). * [Vagrant Azure Provider](https://github.com/Azure/vagrant-azure). * [OpenVZ](https://app.vagrantup.com/OpenVZ). * [vagrant-lxc](https://github.com/fgrehm/vagrant-lxc). If you need to create machines with different technologies, or deploy them to unsupported cloud platforms, you can develop a custom provider in Ruby language. To find out how, see [Plugin Development: Providers](https://www.vagrantup.com/docs/plugins/providers) in Vagrant documentation. The [Vagrant AWS](https://github.com/mitchellh/vagrant-aws) Provider was initially written as an example provider. ### Provisioners A provisioner is a technology used to deploy software to the newly created machines. The simplest provisioner is `shell`, which runs a shell file inside the Vagrant machine. `powershell` is also available. Other providers use automation software to provision the machine. There are provisioners that allow one to use [Ansible](/docs/server/server-management/automated-mariadb-deployment-and-administration/ansible-and-mariadb.md), [Puppet](/docs/server/server-management/automated-mariadb-deployment-and-administration/automated-mariadb-deployment-and-administration-puppet-and-mariadb.md), Chef or Salt. Where relevant, there are different provisioners allowing the use of these technologies in a distributed way (for example, using Puppet apply) or in a centralized way (for example, using a Puppet server). It is interesting to note that there is both a Docker provider and a Docker provisioner. This means that a Vagrant machine can be a Docker container, thanks to the `docker` provisioner. Or it could be any virtualisation technology with Docker running in it, thanks to the `docker` provisioner. In this case, Docker pulls images and starts containers to run the software that should be running in the Vagrant machine. If you need to use an unsupported provisioning method, you can develop a custom provisioner in Ruby language. See [Plugin Development: Provisioners](https://www.vagrantup.com/docs/plugins/provisioners) in Vagrant documentation. ### Plugins It is possible to install a plugin with this command: ```bash vagrant plugin install ``` A Vagrantfile can require that a plugin is installed in this way: ```bash require 'plugin_name' ``` A plugin can be a Vagrant plugin or a Ruby gem installable from [rubygems.org](https://rubygems.org/). It is possible to install a plugin that only exists locally by specifying its path. ### Changes in Vagrant 3.0 HashiCorp published an article that describes its [plans for Vagrant 3.0](https://www.hashicorp.com/blog/toward-vagrant-3-0). Vagrant will switch to a client-server architecture. Most of the logic will be stored in the server, while the development machines will run a thin client that communicates with the server. It will be possible to store the configuration in a central database. Another notable change is that Vagrant is switching from Ruby to Go. For some time, it will still be possible to use Vagrantfiles and plugins written in Ruby. However, in the future Vagrantfiles and plugins should be written in one of the languages that support [gRPC](https://grpc.io/) (not necessarily Go). Vagrantfiles can also be written in [HCL](https://github.com/hashicorp/hcl), HashiCorp Configuration Language. ## Vagrant Commands This is a list of the most common Vagrant commands. For a complete list, see [Command-Line Interface](https://www.vagrantup.com/docs/cli) in Vagrant documentation. To list the available machines: ```bash vagrant box list ``` To start a machine from a box: ```bash cd /box/directory vagrant up ``` To connect to a machine: ```bash vagrant ssh ``` To see all machines status and their id: ```bash vagrant global-status ``` To destroy a machine: ```bash vagrant destroy ``` ## Vagrant Resources and References Here are some valuable websites and pages for Vagrant users. * [Vagrant Up](https://www.vagrantup.com/). * [app.vagrantup.com](https://app.vagrantup.com/). * [Vagrant Community](https://www.vagrantup.com/community). * [Vagrant on Wikipedia](https://en.wikipedia.org/wiki/Vagrant_\(software\)). * [Vagrant on HashiCorp Learn](https://learn.hashicorp.com/vagrant). Content initially contributed by [Vettabase Ltd](https://vettabase.com/). *This page is licensed: CC BY-SA / Gnu FDL* {% @marketo/form formId="4316" %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mariadb.com/docs/server/server-management/automated-mariadb-deployment-and-administration/vagrant-and-mariadb/vagrant-overview-for-mariadb-users.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.