Live data from Hacker News

Vagrant 1.4

vagrantup.com

41–50 of 64 posts

Re: Vagrant 1.4

#41

Earlier quoted context omitted.

I last time I used vagrant was 1.2 on whatever the latest virtualbox at the time was. The performance was about half as good as the host machine. The host machine was running the desktop version of Ubuntu at the time. I was not able to easily identify if VirtualBox's performance problems were CPU or IO bound. If I hear that the performance is close to native, I'll give it another try. Otherwise, I can't see the point…

If you are on Linux, why not use vagrant with lxc containers?

When I was using vagrant 1.2, lxc containers were not fully functional so I didn't bother trying with lxc. I'll gladly give it another try to see if performance is significantly better than virtalbox. Thanks for the tip by the way.

Re: Vagrant 1.4

#42

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…

Thanks for the screencasts, now I may finally get around to giving it a try.

Re: Vagrant 1.4

#43

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…

Can you explain what Vagrant adds on top of VirtualBox? When I tried it it didn't seem that different than just using VirtualBox directly.

What? Automatically installing VirtualBox images, and setting them up with a development environment in 2-3 commands does seem "that different than just using VirtualBox directly"?

Re: Vagrant 1.4

#44

I've just spent 5 minutes trying to learn what Vagrant is and how it works. The home page didn't help me with that AT ALL. It's full of vague terms like "development environment" and "work environment" and buzzwords claiming to "maximize productivity". In your About page, please describe the typical USAGE SCENARIOS of your software and how does it help in those cases exactly.

This is linked in the 2nd sentence in the getting started section that is linked from one of the two biggest call-to-actions on the homepage: http://docs.vagrantup.com/v2/why-vagrant/ I'm sorry you couldn't find that!

Thanks for pointing that out. I still think it would need a concrete example or two. The text is very abstract, long sentences with multiple consecutive adjectives describing how easy it is to use and how powerful it all is. A lot of fluff really. You're trying to sell the idea, not describe how it works.

I'm SURE it's a fine tool and I'm just trying to help you communicating it better. :)

Re: Vagrant 1.4

#45
post #35

Earlier quoted context omitted.

VirtualBox is getting better, but it's still no match for vmware's performance(especially file share).

I last time I used vagrant was 1.2 on whatever the latest virtualbox at the time was. The performance was about half as good as the host machine. The host machine was running the desktop version of Ubuntu at the time. I was not able to easily identify if VirtualBox's performance problems were CPU or IO bound. If I hear that the performance is close to native, I'll give it another try. Otherwise, I can't see the point…

>Otherwise, I can't see the point.

Really? Half as good as the host machine sounds about just fine.

Re: Vagrant 1.4

#46

I've just spent 5 minutes trying to learn what Vagrant is and how it works. The home page didn't help me with that AT ALL. It's full of vague terms like "development environment" and "work environment" and buzzwords claiming to "maximize productivity". In your About page, please describe the typical USAGE SCENARIOS of your software and how does it help in those cases exactly.

>I've just spent 5 minutes trying to learn what Vagrant is and how it works.

Well, it's 2013 and you're on HN. If you don't already know what Vagrant is, then perhaps you're not the most qualified information seeker.

Re: Vagrant 1.4

#47
post #46

I've just spent 5 minutes trying to learn what Vagrant is and how it works. The home page didn't help me with that AT ALL. It's full of vague terms like "development environment" and "work environment" and buzzwords claiming to "maximize productivity". In your About page, please describe the typical USAGE SCENARIOS of your software and how does it help in those cases exactly.

> I've just spent 5 minutes trying to learn what Vagrant is and how it works. Well, it's 2013 and you're on HN. If you don't already know what Vagrant is, then perhaps you're not the most qualified information seeker.

a little harsh ... but actually and unfortunately true :/

Re: Vagrant 1.4

#48
post #46

I've just spent 5 minutes trying to learn what Vagrant is and how it works. The home page didn't help me with that AT ALL. It's full of vague terms like "development environment" and "work environment" and buzzwords claiming to "maximize productivity". In your About page, please describe the typical USAGE SCENARIOS of your software and how does it help in those cases exactly.

> I've just spent 5 minutes trying to learn what Vagrant is and how it works. Well, it's 2013 and you're on HN. If you don't already know what Vagrant is, then perhaps you're not the most qualified information seeker.

Well to be fair the "Why Vagrant?" page [1] isn't exactly clear about whether this is a tool for building throwaway environments or if it's something I should use to build out production systems:

"If you're a developer, Vagrant will isolate dependencies and their configuration within a single ==>disposable

"If you're an operations engineer, Vagrant gives you a ==>disposable

All I can infer from the page is that this is a tool for building throwaway/local environments running on VM's on my desktop. But there isn't any context given on how this relates to my production environments, i.e. getting from Vagrant instance to production, there's a disconnect there for me.

[1]: http://docs.vagrantup.com/v2/why-vagrant/

Re: Vagrant 1.4

#50

Earlier quoted context omitted.

The biggest thing it adds on top of VirtualBox is a consistent workflow. If it helps, think of what Vagrant does technically as useless, and think of Vagrant only as a process discipline: to get a dev environment for any project you "vagrant up", to close it out "vagrant destroy", to access it "vagrant ssh", etc. As soon as you get this consistent workflow, then you can teach it to your entire organization and the wh…

Is this mostly appropriate for web development? Could it work for embedded or desktop development? Seems like it might be a lot of overhead if you only need to install an IDE and a compiler. Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant?

I am using Vagrant to develop a buildroot based embedded project. I had to use NFS for sharing because of hardlinks generated for buildroot. Other than that everything went smoothly.

With vagrant primary mode of interaction is through ssh (although it supports showing GUI on vagrant up). So I don't think it is a good fit for developing Windows or desktop applications.

Post reply on HN