5 ms·

Vagrant 1.6 has been released

51 points by knite 12y ago

jareds 12y ago
While Windows guests look interesting how are people going to get the initial box? Is every individual or organization going to have to create their own box or will there be some way to get a box if you are part of MSDN?
- bingaling 12y ago
  perhaps the modern.ie dev vms could be boxed up http://modern.ie/en-us/virtualization-tools#downloads http://modern.ie/en-us/virtualization-tools#downloads
- tomswartz07 12y ago
  For what it's worth, the same guy makes Packer, a tool to create your own boxes. https://github.com/mitchellh/packer https://github.com/mitchellh/packer It even allows you to replace the functionality of Vagrant - in place- to create, spin up, and provision the box all in one command. It's super awesome.
- mitchellh 12y ago
  You have to acquire an ISO in some legal way yourself. Then, you can use something like packer-windows which has pre-built templates for various versions of Windows to build Vagrant-compatible boxes in about 10 minutes: https://github.com/joefitzgerald/packer-windows https://github.com/joefitzgerald/packer-windows It isn't as easy as "download pre-built Linux box" but for environments that are using Windows, this workflow has been amazing for them above what they used to do, and is quite fast.
  - jareds 12y ago
    Thanks, I'm going to give this a look since you can use the trial ISO's.
chrisbolt 12y ago
What's new: http://www.vagrantup.com/blog/vagrant-1-6.html http://www.vagrantup.com/blog/vagrant-1-6.html
- tomswartz07 12y ago
  Full changelog is here: https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.m...
sergiotapia 12y ago
Edit: Bit the bullet and bought myself this bundle pack from Leanpub: https://leanpub.com/b/vagrant-ansible/ https://leanpub.com/b/vagrant-ansible/ - Vagrant looks like a great tool to have under my belt. Ansible also looks extremely simple compared to Chef and looks like Vagrant and Ansible compliment each other beautifully. --- I guess this a good a place as any to ask, pardon my ignorance. What part of the workflow does Vagrant solve exactly? For example, I'm building a business-class Rails application - normally I have RVM create a gemset specifically for that application. I also have PostgreSQL and MySQL installed locally for any app that needs it. How does Vagrant fit into this workflow, what am I missing? Also, since the 'dev box' is now a virtual machine does that mean I can only ssh into it and edit code with something like Vim? Thanks for the information.
- joevandyk 12y ago
  http://docs.vagrantup.com/v2/why-vagrant/index.html http://docs.vagrantup.com/v2/why-vagrant/index.html has your information.
  - sergiotapia 12y ago
    Yep, I saw that but it doesn't really answer my question. :( If you're a developer, Vagrant will 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 you or someone else creates a single Vagrantfile, you just need to vagrant up and everything is installed and configured for you to work. Other members of your team create their development environments from the same configuration, so whether you're working on Linux, Mac OS X, or Windows, all your team members are running code in the same environment, against the same dependencies, all configured the same way. Say goodbye to "works on my machine" bugs. --- It doesn't answer if I can only ssh into the box and write code there. I need more actual workflow data.
    - Denzel 12y ago
      As jeffasinger described, you can sync folders between your local environment and the Vagrant VM. You can edit files locally, save them, and have the changes propagated without SSH'ing into the box. [1] [1]: http://docs.vagrantup.com/v2/synced-folders/ http://docs.vagrantup.com/v2/synced-folders/ Edit: Adding source.
molecule 12y ago
http://www.vagrantup.com/blog/vagrant-1-6.html http://www.vagrantup.com/blog/vagrant-1-6.html > Boxes can now be compressed with LZMA - LZMA compression can result in much smaller boxes in a lot of cases, and Vagrant can now decompress LZMA-compressed boxes. any word on how this is enabled, or does it just work? I didn't see anything in the package or box docs. thanks.
- mitchellh 12y ago
  Just works. Actually, LZMA compression has always works on Linux/Mac. Vagrant 1.6 is just the first release to also support LZMA compression on Windows as well. Since it is supported on all platforms, we're able to advertise it a bit.
akurilin 12y ago
Love Vagrant, so useful.
tdicola 12y ago
I'm really impressed with Vagrant's documentation: http://docs.vagrantup.com/v2/ http://docs.vagrantup.com/v2/ Super clean, easy to read, and well organized. Nice job!
speg 12y ago
I've just started using Vagrant, but am not quite sure how it relates to production. Can I use Vagrant to build out my production server too? Or would I just use Chef/Puppet/Ansible with the same playbook/recipe on both my Vagrant powered VM and non-vagrant powered production machine?
- thedevelopment 12y ago
  I believe Vagrant is for quickly and repeatably building development environments - I don't think it's meant for production. Look into packer for building out Production images, and Chef/Puppet/Ansible for additional configuration ontop those images.
- elithrar 12y ago
  I use Salt (used to use Puppet) to build out my Vagrant box(es) in development. When I'm good to go, I use Packer with the same Salt configuration to build an image and push it to AWS/DO/RackSpace as needed. Makes it super easy to develop and deploy on exactly the same machine, and the Vagrant/Packer configurations are typically fairly minimal so there's very little set-up time once you've written out your Salt/Puppet/etc configurations.
Sgoettschkes 12y ago
I could not live without vagrant anymore. Developing inside vm, having a linux env on my windows machine, testing stuff, testing ansible/chef setups with a testing vm... It's so easy :)

51 points by knite 12y ago

While Windows guests look interesting how are people going to get the initial box? Is every individual or organization going to have to create their own box or will there be some way to get a box if you are part of MSDN?

bingaling 12y ago
perhaps the modern.ie dev vms could be boxed up http://modern.ie/en-us/virtualization-tools#downloads http://modern.ie/en-us/virtualization-tools#downloads
tomswartz07 12y ago
For what it's worth, the same guy makes Packer, a tool to create your own boxes. https://github.com/mitchellh/packer https://github.com/mitchellh/packer It even allows you to replace the functionality of Vagrant - in place- to create, spin up, and provision the box all in one command. It's super awesome.
mitchellh 12y ago
You have to acquire an ISO in some legal way yourself. Then, you can use something like packer-windows which has pre-built templates for various versions of Windows to build Vagrant-compatible boxes in about 10 minutes: https://github.com/joefitzgerald/packer-windows https://github.com/joefitzgerald/packer-windows It isn't as easy as "download pre-built Linux box" but for environments that are using Windows, this workflow has been amazing for them above what they used to do, and is quite fast.
- jareds 12y ago
  Thanks, I'm going to give this a look since you can use the trial ISO's.

chrisbolt 12y ago

What's new: http://www.vagrantup.com/blog/vagrant-1-6.html http://www.vagrantup.com/blog/vagrant-1-6.html

tomswartz07 12y ago
Full changelog is here: https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.m...

sergiotapia 12y ago

Edit: Bit the bullet and bought myself this bundle pack from Leanpub: https://leanpub.com/b/vagrant-ansible/ https://leanpub.com/b/vagrant-ansible/ - Vagrant looks like a great tool to have under my belt. Ansible also looks extremely simple compared to Chef and looks like Vagrant and Ansible compliment each other beautifully. --- I guess this a good a place as any to ask, pardon my ignorance. What part of the workflow does Vagrant solve exactly? For example, I'm building a business-class Rails application - normally I have RVM create a gemset specifically for that application. I also have PostgreSQL and MySQL installed locally for any app that needs it. How does Vagrant fit into this workflow, what am I missing? Also, since the 'dev box' is now a virtual machine does that mean I can only ssh into it and edit code with something like Vim? Thanks for the information.

joevandyk 12y ago
http://docs.vagrantup.com/v2/why-vagrant/index.html http://docs.vagrantup.com/v2/why-vagrant/index.html has your information.
- sergiotapia 12y ago
  Yep, I saw that but it doesn't really answer my question. :( If you're a developer, Vagrant will 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 you or someone else creates a single Vagrantfile, you just need to vagrant up and everything is installed and configured for you to work. Other members of your team create their development environments from the same configuration, so whether you're working on Linux, Mac OS X, or Windows, all your team members are running code in the same environment, against the same dependencies, all configured the same way. Say goodbye to "works on my machine" bugs. --- It doesn't answer if I can only ssh into the box and write code there. I need more actual workflow data.
  - Denzel 12y ago
    As jeffasinger described, you can sync folders between your local environment and the Vagrant VM. You can edit files locally, save them, and have the changes propagated without SSH'ing into the box. [1] [1]: http://docs.vagrantup.com/v2/synced-folders/ http://docs.vagrantup.com/v2/synced-folders/ Edit: Adding source.

molecule 12y ago

http://www.vagrantup.com/blog/vagrant-1-6.html http://www.vagrantup.com/blog/vagrant-1-6.html > Boxes can now be compressed with LZMA - LZMA compression can result in much smaller boxes in a lot of cases, and Vagrant can now decompress LZMA-compressed boxes. any word on how this is enabled, or does it just work? I didn't see anything in the package or box docs. thanks.

mitchellh 12y ago
Just works. Actually, LZMA compression has always works on Linux/Mac. Vagrant 1.6 is just the first release to also support LZMA compression on Windows as well. Since it is supported on all platforms, we're able to advertise it a bit.

akurilin 12y ago

Love Vagrant, so useful.

tdicola 12y ago

I'm really impressed with Vagrant's documentation: http://docs.vagrantup.com/v2/ http://docs.vagrantup.com/v2/ Super clean, easy to read, and well organized. Nice job!

speg 12y ago

I've just started using Vagrant, but am not quite sure how it relates to production. Can I use Vagrant to build out my production server too? Or would I just use Chef/Puppet/Ansible with the same playbook/recipe on both my Vagrant powered VM and non-vagrant powered production machine?

thedevelopment 12y ago
I believe Vagrant is for quickly and repeatably building development environments - I don't think it's meant for production. Look into packer for building out Production images, and Chef/Puppet/Ansible for additional configuration ontop those images.
elithrar 12y ago
I use Salt (used to use Puppet) to build out my Vagrant box(es) in development. When I'm good to go, I use Packer with the same Salt configuration to build an image and push it to AWS/DO/RackSpace as needed. Makes it super easy to develop and deploy on exactly the same machine, and the Vagrant/Packer configurations are typically fairly minimal so there's very little set-up time once you've written out your Salt/Puppet/etc configurations.

Sgoettschkes 12y ago

I could not live without vagrant anymore. Developing inside vm, having a linux env on my windows machine, testing stuff, testing ansible/chef setups with a testing vm... It's so easy :)