Vagrant 1.4

#1

Post by bpierre » Mon, Dec 09, 2013, 7:20 PM UTC

Re: Vagrant 1.4

#2

Post by pezh0re » Mon, Dec 09, 2013, 9:24 PM UTC

As someone who uses Vagrant for a ton of puppet testing, the part about the Windows guests in 1.5 made me incredibly happy.

Re: Vagrant 1.4

#3

Post by yeukhon » Mon, Dec 09, 2013, 9:24 PM UTC

The machine-readable output is interesting.

Re: Vagrant 1.4

#4

Post by WestCoastJustin » Mon, Dec 09, 2013, 9:27 PM UTC

For anyone who doesn't know. Vagrant acts like a wrapper around VMware, VirtualBox, or even AWS, so that you can easily automate testing. You can also share your Vagrant boxes (images) with others in an easy manner. Vagrant is one of those things, that once you start to use it, you wonder how you managed without it. I have created several screencasts about Vagrant:

Learning Vagrant @ http://sysadmincasts.com/episodes/4-vagrant

Create a Vagrant box with Veewee @ http://sysadmincasts.com/episodes/5-create-a-vagrant-box-wit...

Learning Puppet with Vagrant @ http://sysadmincasts.com/episodes/8-learning-puppet-with-vag...

Managing Iptables with Puppet @ http://sysadmincasts.com/episodes/18-managing-iptables-with-...

Re: Vagrant 1.4

#5

Post by andyl » Mon, Dec 09, 2013, 9:48 PM UTC

Docker provisioner - that's great. I could use Ansible to provision Docker containers, but its nice to have a built-in option as well.

Re: Vagrant 1.4

#6

Post by tedivm » Mon, Dec 09, 2013, 9:53 PM UTC

This is fantastic! I just used Vagrant to help automate testing on an email library I wrote (https://github.com/tedivm/Fetch, if anyone is interested- new tests are in the "testing" branch).

Vagrant made setting that up really easy. In fact, the hardest part was scripting different responses for whether the machine was already up or not, and the new Machine-Readable Output will make that far, far easier.

Thanks for making a great tool better!

Re: Vagrant 1.4

#7

Post by peter_l_downs » Mon, Dec 09, 2013, 9:56 PM UTC

> Work will begin on pulling the Vagrant AWS integration into the core distribution -- to start -- so that you can use Vagrant with AWS (and other providers) right after installing it and without having to juggle plugin versions.

This is awesome, I can't wait. I've been waiting for this!

Re: Vagrant 1.4

#8

Post by NDizzle » Mon, Dec 09, 2013, 10:11 PM UTC

I'm afraid of upgrading vagrant now like I am afraid of upgrading bootstrap.

Too many things break - it's simply not worth the trouble of upgrading and finding all the gotchas scattered all over the place in my config files and code.

Re: Vagrant 1.4

#9

Post by FooBarWidget » Mon, Dec 09, 2013, 10:19 PM UTC

I had hoped that their Docker support would be some magical mechanism that would treat Docker as a kind of VirtualBox. That is, instead of using VirtualBox to create VMs, they would use Docker to create containers. 'vagrant ssh' would then SSH directly into a container instead of the host VM.

Sadly, their Docker support is just a provisioner. :( I can do that myself too in a shell script.

Re: Vagrant 1.4

#10

Post by johnbellone » Mon, Dec 09, 2013, 10:23 PM UTC

FooBarWidget wrote: post #9

I had hoped that their Docker support would be some magical mechanism that would treat Docker as a kind of VirtualBox. That is, instead of using VirtualBox to create VMs, they would use Docker to create containers. 'vagrant ssh' would then SSH directly into a container instead of the host VM. Sadly, their Docker support is just a provisioner. :( I can do that myself too in a shell script.

There's not really a way to do that uniformly right now on any system that isn't Linux. I agree that it would be ideal, but the core philosophy behind Vagrant is a single configuration recipe to create portable environments (development). You can do a lot of things in shell scripts, but its still easier to have it all in one place in an easily grokable format.