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

Vagrant 1.0 - Virtualized development for the masses.

vagrantup.com

Post reply on HN
Print view View original

11–20 of 21 posts

Re: Vagrant 1.0 - Virtualized development for the masses.

#11

Post by patcon »

People often talk big in open source communities about all the progressive and best-practicey things their organizations do. But oftentimes, people don't share. A good chunk of the time, it's competitive advantage, but sometimes this is because it's tough to share a complex setup easily.

Vagrant makes it simple to share a workflow or tool configuration as a little package that can be exploded into its full awesomeness with a simple "vagrant up". Combined with Chef's Spiceweasel tool, others can theoretically launch an infrastructure right then and there, should they like what they see locally.

This blows my mind. Surrriously. So excited for the potential. Thanks Mitchell, for being the right wizard at the right time.

Re: Vagrant 1.0 - Virtualized development for the masses.

#14

Post by johnbender »

tomku wrote: post #13

Did you guys (or the MRI guys, not sure where the bug was) ever fix whatever forced the use of JRuby on Windows in previous versions, or is it just bundled with the installer now? Either way, grats on the release, Vagrant is a really useful (and cool!) tool. :)

Tomku,

I think you're referring to the win32ole issues which were addressed in the 0.9.0 release as the driver and communication with Virtualbox no longer require ffi.

[edit] the change was made in the 0.9 release.

Re: Vagrant 1.0 - Virtualized development for the masses.

#15

Post by mbreese »

I have a question...

So, Vagrant lets you setup quick VMs to make development easier. I get that... (and like it). But what happens when you need to migrate the dev image to actual hardware? I assume that you use the same Puppet / Chef provisioning that you use in the VM, but it isn't clear from the "Getting Started" part of the site. Does Vagrant help with that, or are you on your own?

Perhaps there should be a "Production/deployment" section of the Getting Started Guide.

Re: Vagrant 1.0 - Virtualized development for the masses.

#16

Post by mitchellh »

mbreese wrote: post #15

I have a question... So, Vagrant lets you setup quick VMs to make development easier. I get that... (and like it). But what happens when you need to migrate the dev image to actual hardware? I assume that you use the same Puppet / Chef provisioning that you use in the VM, but it isn't clear from the "Getting Started" part of the site. Does Vagrant help with that, or are you on your own? Perhaps there should be a "Pro…

Thanks for the feedback. I agree there should probably be a section on this in the documentation since it is a common question.

But you're on the right track: The puppet/chef provisioning you use in the VM should be used for production as well. Usually the scripts aren't IDENTICAL in dev/production but there are only slightly different.

Re: Vagrant 1.0 - Virtualized development for the masses.

#17

Post by josephholsten »

mitchellh wrote: post #4

Hi! Just so you know I'll be responding to any comments here on HN. I've worked on Vagrant for over 2 years and even originally announced it on HN ( http://news.ycombinator.com/item?id=1175901 ). Over the 2 years of the existence of the project, popularity has steadily rose, features were flushed out, and stability soon followed. With the 1.0 release I'm happy to announce a handful of the many companies who use Vagra…

Glad to be one of the users who uses vagrant every day!

Re: Vagrant 1.0 - Virtualized development for the masses.

#18

Post by josephholsten »

mbreese wrote: post #15

I have a question... So, Vagrant lets you setup quick VMs to make development easier. I get that... (and like it). But what happens when you need to migrate the dev image to actual hardware? I assume that you use the same Puppet / Chef provisioning that you use in the VM, but it isn't clear from the "Getting Started" part of the site. Does Vagrant help with that, or are you on your own? Perhaps there should be a "Pro…

I've set up scripts to convert an existing virtualbox/vagrant .box file to a vmware compatible OVF. I would use those to deliver to clients at my last employer. I know github is doing a similar process. Additionally there's mccloud, which lets you deploy to aws. If you need help getting any of these set up, let me know.

Re: Vagrant 1.0 - Virtualized development for the masses.

#20

Post by senthilnayagam »

josephholsten wrote: post #18
mbreese wrote: post #15

I have a question... So, Vagrant lets you setup quick VMs to make development easier. I get that... (and like it). But what happens when you need to migrate the dev image to actual hardware? I assume that you use the same Puppet / Chef provisioning that you use in the VM, but it isn't clear from the "Getting Started" part of the site. Does Vagrant help with that, or are you on your own? Perhaps there should be a "Pro…

I've set up scripts to convert an existing virtualbox/vagrant .box file to a vmware compatible OVF. I would use those to deliver to clients at my last employer. I know github is doing a similar process. Additionally there's mccloud, which lets you deploy to aws. If you need help getting any of these set up, let me know.

those scripts would be nice to haves, if they are not part of some commercial product or a potential startup can you open source them
Post reply on HN