Raghavendra Talur's blog

This post is about one of the most useful plugins for vagrant, vagrant-cachier. Vagrant makes it very easy to bring up and destroy VMs. It gives independence from trying to maintain VMs in a sane state. The downside of bringing up VMs so often is the amount of data usage that happens. Thankfully we have a great vagrant plugin which solves this problem by keeping the the downloaded data on the host and serves as cache for VMs. The plugin is vagrant-cachier and you can find code and documentation at https://github.com/fgrehm/vagrant-cachier. Here is how you enable vagrant-cachier plugin in your Vagrantfile. However, on a rhel/fedora derivative guest VM I had to make a few changes with the box before I could achieve a truly off-network Vagrant setup. Basically, my requirement was that I should be able to perform a "vagrant up" when the host machine(Laptop in my case) does not have a working Internet connection. Here are the things that I had to do to achiev

This post is a quick guide for installing and using Vagrant on Fedora 22. Update: Part 2 :  http://blog.raghavendratalur.in/2015/09/vagrant-on-fedora-22-part-2.html Introduction       $VAGRANT_HOME Global config of vagrant exists in $VAGRANT_HOME. Default points to ~/.vagrant.d. This is where all boxes are stored This is where all plugins are installed. If you don't like huge amount of data being stored under dot folders, you can point it to a different location by exporting it in .bashrc. For example, add the following line to ~/.bashrc. export VAGRANT_HOME="$HOME/vagrant/data"       $VAGRANT_DEFAULT_PROVIDER We will be mainly using libvirt as the provider, so let's make it the default provider. Add the following line to ~/.bashrc. export VAGRANT_DEFAULT_PROVIDER=libvirt in your ~/.bashrc. If you added any of the above lines, execute this command before proceeding. $ source ~/.bashrc For more