3 ms·
Definitely looked at a few virtualization options (we use Citrix XenServer at work), but my rationale for LXC was making the most use of limited hardware (rathe
by FireBeyond 14y ago
Definitely looked at a few virtualization options (we use Citrix XenServer at work), but my rationale for LXC was making the most use of limited hardware (rather than being forced to commit, say, 2GB for VM A, 2 for VM B, and so on, instead having up to the full server resources available - this isn't strictly the "best practice" for a mock production environment but will suffice).
"vim elite" may not have been the best phrasing - my intent wasn't to imply superiority and condescension, merely "text editor power user".
Divvy is a nice tool, which I do use, and does make life a little easier, and if my preference deep down is that of a largely maximized world and Windows, so be it.
I do really want to investigate Vagrant, and will check out your links, cheers!
- e12e 14y agoAh, I didn't think you'd be interested in LXC as I thought you'd be running your VMs under OS X? If you're considering running VirtualBox (Vagrant) under Linux/Solaris, VirtualBox does support a limited form of overcommitting RAM (not under OS X, however): https://www.virtualbox.org/manual/ch04.html#idp18673360 I believe you can use this with Vagrant via: http://vagrantup.com/v1/docs/config/vm/customize.html You still have to dedicate RAM to VirtualBox -- but you no longer have to dedicate it to each VM. If you are already using Citrix, the Xen Server product has supported a limited form of overcommit since version 5.6: http://support.citrix.com/article/CTX124972 I would think spending time automating deployment to the same environment as you use for production would be better than having a separate technology for development? I don't know what your internal politics are like, but setting up a dedicated server with a few tens of gigs of RAM for development and testing should be a worthwhile investment -- and running the same software there as in production should be good both for knowledge transfer and avoiding surprises going from testing to production (and vice versa). Finally, I've been a impressed with vmware's new open source project, CloudFoundry.com/.org -- if not so impressed with their documentation for the free/open version. Apparently you can use that with VirtualBox as well: http://matschaffer.com/2011/04/cloudfoundry-virtualbox/ Note that Vagrant is in the process of being refactored with the goal of adding support for other hosts than just VirtualBox in the (relatively) near future.