#Vagrant vs terraform install
![vagrant vs terraform vagrant vs terraform](https://www.thevfanatic.com/wp-content/uploads/2019/01/image_7c79c414-f8a7-4220-a15a-0aba107db2ef20190114_204646-300x212.jpg)
Packer is a tool to create machine images for providers like Virtualbox, VMWare, AWS, Google cloud.
![vagrant vs terraform vagrant vs terraform](https://image.slidesharecdn.com/gluecon2015-150520222355-lva1-app6892/95/tear-it-down-build-it-back-up-empowering-developers-with-amazon-cloudformation-15-1024.jpg)
The typical problems like “ it does not work for me even though its working in your machine” goes away. Simply by doing “vagrant up”, the complete VM environment is exactly reproduced. Vagrant also integrates well with other provisioning tools like Chef, Ruby and Ansible to describe the provisioning. “Vagrantfile” describes the VM settings as well as initial bootstrap provisioning that needs to be done on the VM. Vagrant integrates well with major hypervisors like Virtualbox, VMWare, HyperV. Vagrant provides a repeatable VM development environment. Overview of Vagrant, Packer, Terraform and Atlas Vagrant In this blog, I will cover a development to production workflow for a LAMP application stack using Atlas, Vagrant, Packer and Terraform. Atlas is Hashicorp’s product that combines its open source tools into a platform and it has a commercial version as well.
Recently, I saw some of the videos of Hashiconf and I learnt that Hashicorp has an ecosystem of tools addressing Devops needs and that these tools can be chained together to create complete application delivery platform from development to production. I have used and loved Vagrant for a long time and I recently used Consul and I was very impressed by both these Devops tools.