Vagrant is a tool for building virtualized development environments.
vagrantup.com
vagrantup.com
I didn't expect to see this on HN today but I guess I'll just give a giant information dump here for those interested :)
Good links for those interested in what Vagrant is:
* "Why Vagrant?" - http://vagrantup.com/docs/getting-started/why.html
* "Frequently Asked Questions" - http://vagrantup.com/faq.html
* The code - https://github.com/mitchellh/vagrant
* The original HN submission when Vagrant was launched (286 days ago) - http://news.ycombinator.com/item?id=1175901
And then a quick update for those who want to know whats going on with the project now:
The project has been nonstop since January this year, and the codebase is nearing one year old. Vagrant is now on version 0.6.8. Vagrant is used by many companies worldwide and the 0.6.x series is considered stable. In September 2010 I gained sponsorship for my work on Vagrant by Engine Yard[1]. I've been working very hard for the past 2 months to get the project working with other hypervisors (KVM, VMWare), spurring other open source projects of my own in the process (libvirt-rb, virtuoso, you can find these at my github[2]).
[1]: http://www.engineyard.com/blog/2010/mitchell-hashimoto-joins...
I've been migrating our developer environments over at 99designs to use Vagrant and it's been fantastic. What was previously an unmaintainable shell script is now a re-usable collection of chef recipes and a brief Vagrantfile.
Thanks for your hard work!
Ideally I'd like to be able to build a vm in vagrant under virtualbox, and then push it out to a esx/esxi acceptance box, then push it out to a esx/esxi production box.
It would mean that the devs could build the images, then get ops to have a look over the config/add their own fixes, then deploy the fixes into production. Not many enterprises I know really want to run virtualbox in production.
In a probably unrelated question to vagrant, would you happen to know if VirtualBox virtual hdd can be shrinked and expanded? And if VB can, does vagrant support that?
Use-case: one 8GB (only use 2GB total) vm instance to be moved from Windows Server to Ubuntu Linux. Or for cloning purposes. Copying 8GB probably would take a lot of time, compacting it to 2GB first then copying it to multiple machines probably would be a lot faster.
Thanks again for creating vagrant!
Also, it's well worth the effort to learn Chef (or another automated provisioning tool) if you haven't already. It makes working with Vagrant way easier and saves you time whenever you create a new environment. Plus you can use the same recipes on a production box, so the effort isn't wasted.
Is there any future chance of libvirt compatibility as an option?
Regards
Joe
If you're not on 64-bit windows, I'd love to work with you to hear what your experience was and what went wrong.
Negative experiences like the one you had are unfortunate, but through them we can fix it and make it better for everyone else.
You don't have any contact info in your profile, please contact me at mitchell.hashimoto@gmail.com or through github, irc, etc.
The problems have been mentioned several times on the internet when I did google, but no solution were mentioned.