Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vagrant 2.0

hashicorp.com

Post reply on HN
Print view View original

1–10 of 120 posts

Re: Vagrant 2.0

#3

Post by randlet »

sciurus wrote: post #2

Does the major version bump signify any major changes? The blog post and changelog don't seem to describe any.

"Vagrant 1.0 was released in 2013 as a stable release. Vagrant 1.0 only supported VirtualBox as a provider, only supported a handful of Linux operating systems as guests, and supported a simple up/destroy workflow. Since Vagrant 1.0, we've added support for multi-providers such as VMware and Docker, guests such as Windows, macOS, and complex workflows including snapshots. These major changes are followed by hundreds of improvements and bug fixes."

Re: Vagrant 2.0

#4

Post by jimmar »

Just from the version number I thought there'd be a few major changes, but really it just seems like another point release that happens to increment the major version number. (Which is totally fine by me. I rely on Vagrant a lot and I'm glad the new version doesn't introduce breaking changes). Change log is here: https://github.com/mitchellh/vagrant/blob/v2.0.0/CHANGELOG.m...

Re: Vagrant 2.0

#6

Post by jitl »

In the change log, I’m happy to see “improved the resilience of some Virtualbox commands.” At Airbnb, we used to use Vagrant with Virtualbox and the Chef provisioner to create our dev environments, but we migrated totally away from Vagrant after struggling with Virtualbox bugs, and strangeness with Vagrant’s internal state and locking.

Seems like this issue is finally addressed: https://github.com/mitchellh/vagrant/issues/8468

Vagrant is a fantastic tool because of its flexibility, but that flexibility comes at cost: there are sometimes bugs and performance issues where the different Vagrant components don’t quite mesh perfectly.

Re: Vagrant 2.0

#8

Post by growtofill »

jitl wrote: post #6

In the change log, I’m happy to see “improved the resilience of some Virtualbox commands.” At Airbnb, we used to use Vagrant with Virtualbox and the Chef provisioner to create our dev environments, but we migrated totally away from Vagrant after struggling with Virtualbox bugs, and strangeness with Vagrant’s internal state and locking. Seems like this issue is finally addressed: https://github.com/mitchellh/vagrant/i…

What did you end up using instead of Vagrant?

Re: Vagrant 2.0

#9

Post by hosh »

jimmar wrote: post #4

Just from the version number I thought there'd be a few major changes, but really it just seems like another point release that happens to increment the major version number. (Which is totally fine by me. I rely on Vagrant a lot and I'm glad the new version doesn't introduce breaking changes). Change log is here: https://github.com/mitchellh/vagrant/blob/v2.0.0/CHANGELOG.m...

Yup, seems more like a marketing thing to me. I couldn't find any compelling features. On the other hand, the stability improvements are great to have -- my team doesn't really want to be thinking about vagrant when trying to work on our projects.
Post reply on HN