Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Vagrant to the rescue

February 05, 2015

Vagrant to the rescue

Many developers know the pain of setting up a development machine and share the setup with the team - Putting the same folders in the same place, keeping configurations in sync and managing external dependencies. Vagrant solves this problem by creating a development environment inside a virtual machine and making it easy to share with other developers. Within this talk, I'll take the audience on a trip from a time where everybody would install stuff on localhost until the software starts working to a land where the environment one develops in mirrors the production environment as closely as possible without changing the laptop/pc of the developer. I'll talk about devops and configuration management briefly and show how one can get started with vagrant. After this talk, the audience knows what problems vagrant solves and how to get started.


February 05, 2015

More Decks by Sebastian

Other Decks in Programming


  1. Building blocks Configuration + Provider + Base Boxes + Provisioner

    + Plugins = Vagrant http://pixabay.com/static/uploads/photo/2010/12/10/08/salad-1105_640.jpg
  2. Configuration Vagrant.configure(2) do |config| config.vm.box = "Sgoettschkes/debian7-ansible" config.vm.network "private_network", ip:

    "" config.vm.synced_folder "../", "/srv/workspace" config.vm.provision "chef_solo" do |chef| chef.add_recipe "main" end end
  3. Base Boxes Base Boxes • Image from VM • Provider-specific

    • Distribution through ◦ HTTP ◦ “Atlas” http://upload.wikimedia.org/wikipedia/commons/9/91/Shipping_containers_at_Clyde.jpg
  4. Plugins # AWS provider $ vagrant plugin install vagrant-aws #

    Boxen provisioner $ vagrant plugin install ventriloquist # Manage host files $ vagrant plugin install vagrant-hostmanager # Make screenshots of your VM $ vagrant plugin install vagrant-camera # … many more!
  5. Basic workflow $ vagrant init Sgoettschkes/debian7-ansible $ vagrant up #

    box is booting $ vagrant ssh # It’s actually a normal, headless VM! $ exit
  6. Basic workflow $ vim Vagrantfile # change config # add

    provisioners and so on $ git init $ git commit -Am ‘I am using Vagrant now!’ # Keep the Vagrantfile and files needed for provisioning # in git (or any other scm) to share with others
  7. Basic workflow $ git clone [email protected]:awesomecompany/awesomeVm.git $ cd awesomeVm &&

    vagrant up # VM is setup the same as on your co-workers machine # You can now work on your project
  8. Basic workflow # Co-worker updated Vagrantfile/provisioning files $ git pull

    --rebase $ vagrant provision # VM is up to date again
  9. Basic workflow # You wanna change some Vagrant related stuff

    $ vim Vagrantfile # Change it! $ vim playbook.yml # Change something here as well, maybe? $ vagrant provision # Your box is up to date again $ git commit -am ‘Incredible changes’ && git push
  10. Use cases Development environment Testing environment Local test box for

    PMs & Designer Playing around with clusters Open Source projects
  11. Multi-VM setup Vagrant.configure(2) do |config| config.vm.box = "Sgoettschkes/debian7" config.vm.define "web1"

    do |web1| web1.vm.network "private_network", ip: "" end config.vm.define "db1" do |db1| db.vm.network "private_network", ip: "" end end
  12. Multi-VM setup Vagrant.configure(2) do |config| config.vm.box = "Sgoettschkes/debian7" config.vm.define "web1"

    do |web1| web1.vm.network "private_network", ip: "" end config.vm.define "db1" do |db1| db.vm.network "private_network", ip: "" end end
  13. Vagrant share $ vagrant share # Your VM is now

    accessible through a public url # You can go back doing awesome work!