Vagrant (software)

Vagrant
Vagrant starting a virtual machine using vagrant up
Original author(s) Mitchell Hashimoto[1]
Developer(s) HashiCorp (Mitchell Hashimoto and John Bender)
Initial release March 8, 2010 (2010-03-08)[2]
Stable release
2.1.1 / May 7, 2018
Repository
Edit this at Wikidata
Written in Ruby
Operating system Linux, FreeBSD, macOS, and Microsoft Windows
Available in English
Type Configuration management
License MIT License[3]
Website www.vagrantup.com

Vagrant is an open-source software product for building and maintaining portable virtual software development environments,[4] e.g. for VirtualBox, Hyper-V, Docker containers, VMware, and AWS which try to simplify software configuration management of virtualizations in order to increase development productivity. Vagrant is written in the Ruby language, but its ecosystem supports development in a few languages.

History

Vagrant was first started as a personal side-project by Mitchell Hashimoto in January 2010. The first version of Vagrant was released in March 2010. In October 2010, Engine Yard declared that they were going to sponsor the Vagrant project. The first stable version, Vagrant 1.0, was released in March 2012, exactly two years after the original version was released. In November 2012, Mitchell formed an organization called “HashiCorp” to support the full-time development of Vagrant; Vagrant remained liberally licensed free software. HashiCorp now works on creating commercial additions and provides professional support and training for Vagrant.

Vagrant was originally tied to VirtualBox, but version 1.1 added support for other virtualization software such as VMware and KVM, and for server environments like Amazon EC2.[5] Vagrant is written in Ruby, but it can be used in projects written in other programming languages such as PHP, Python, Java, C#, and JavaScript.[6][7] Since version 1.6, Vagrant natively supports Docker containers, which in some cases can serve as a substitute for a fully virtualized operating system.[8]

Architecture

Vagrant uses "Provisioners" and "Providers" as building blocks to manage the development environments. Provisioners are tools that allow users to customize the configuration of virtual environments. Puppet and Chef are the two most widely used provisioners in the Vagrant ecosystem (Ansible has been available since at least 2014 [9]). Providers are the services that Vagrant uses to set up and create virtual environments. Support for VirtualBox, Hyper-V, and Docker virtualization ships with Vagrant, while VMware and AWS are supported via plugins.

Vagrant sits on top of virtualization software as a wrapper and helps the developer interact easily with the providers. It automates the configuration of virtual environments using Chef or Puppet, and the user does not have to directly use any other virtualization software. Machine and software requirements are written in a file called "Vagrantfile" to execute necessary steps in order to create a development-ready box. "Box" is a format and an extension ( .box) for Vagrant environments that is copied to another machine in order to replicate the same environment.

References

  1. ↑ Marvin, Rob. "Mitchell Hashimoto is automating the world". Software Development Times. Software Development Times. Retrieved 27 June 2016.
  2. ↑ "mitchellh/vagrant: Release v0.1.0". GitHub. Retrieved 6 September 2015.
  3. ↑ Vagrant's LICENSE
  4. ↑ "Introducing Vagrant | Linux Journal". www.linuxjournal.com. Retrieved 2016-09-14.
  5. ↑ Mitchell Hashimoto (2013). Vagrant: Up and Running (PDF). O'Reilly Media. p. 13. ISBN 978-1449335830.
  6. ↑ "Vagrant: EC2-Like Virtual Machine Building and Provisioning from Ruby". Retrieved May 14, 2012.
  7. ↑ "Vagrant - Getting Started - Project Setup". Retrieved Jan 19, 2016.
  8. ↑ Mitchell Hashimoto (2014-05-06). "Vagrant 1.6". Retrieved 2014-06-14.
  9. ↑ Brett, Adam (2014-09-23). "Vagrant & Ansible Quickstart Tutorial". adamcod.es. Retrieved 2017-08-06.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.