Build Powerful, Flexible, Reproducible Development Environment using Vagrant and Ansible

Does the below sound familiar?

  • Works on my machine!
  • Is Developer environment setup an elaborate task and non-reproducible in your projects?
  • Do you struggle with differences between Production & Development environments during troubleshooting?

Come to the world of creating and configuring lightweight, reproducible, and portable development environments using Vagrant and Ansible.

Machines are provisioned on top of leading industry giants like VirtualBox, VMWare, AWS and few more.

Provisioning tools like Ansible, Chef, Puppet can be used to automatically install and configure software on the machine.

Integration with Vagrant helps your create reproducible environments defined by VagrantFile. To have the same setup for all team members, you need to just copy the VagrantFile in the version control. You will learn how to isolate dependencies and their configuration within a single disposable, consistent environment, without sacrificing any of the tools you're used to working with (editors, browsers, debuggers, etc.).

Once the OS, configurations and software are decided and a vagrant file with the provisioning is created, others can create the development environment using the same file.

This session will focus on integrating Vagrant with Virtual Box and provision using Ansible.

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

In the 45 minutes demo, we will show you how to create a development  environment using Vagrant and Ansible.

Learning Outcome

  • Understand how to create portable and consistent development environment which can be destroyed and created at any point.
  • Able to create multiple VMs using vagrant
  • Integrate with Ansible for provisioning
  • Configure basic software packages

Target Audience

Agile Developers, Scrum Master, Agile transformation Leaders, Devops

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Submission