Showing posts from August, 2016

Automated Gluster cluster creation for testing

Setting up an identical cluster as that of users' when trying to reproduce any issue is not a simple task when you are working in distributed systems. This usually consists of installing the operating system by hand and then remembering to do every tiny configuration change that is required to complete the setup on every machine in the setup. Realizing that I forgot to set a selinux boolean or enable a port in firewall after an hour of debugging is not a happy place to be in. Now, I have arrived at a setup which does not get on my nerves. I use combination of two tools to get the work done. The first is a tool that I wrote when I found myself editing Vagrantfile a lot when trying to scale the setup by altering the parameters. It is called vagrant-cluster-creator  . The second tool that I use is gdeploy  , which is what you should use to configure and deploy Gluster if you want consistent setups. What you need to have the same setup as I do: a. install vagrant, please refer

Checklist for Vagrant box creation

Here is my check list for creating a vagrant box of a linux machine. Some of the steps might be applicable only for RHEL family of distributions. Shutdown the VM and copy over the VM's disk file as box.img.

Getting started with Vagrant on Fedora 24

If you want to use Vagrant on Fedora 24, here is all you need to do: $ sudo dnf install libvirt vagrant vagrant-libvirt vagrant-libvirt-doc $ sudo cp /usr/share/vagrant/gems/doc/vagrant-libvirt-0.0.32/polkit/10-vagrant-libvirt.rules /usr/share/polkit-1/rules.d/ $ sudo systemctl enable libvirtd.service $ sudo usermod -a -G vagrant <username> # Now, logout from the system and login again for usermod to take effect. $ mkdir vagrant-test $ cd vagrant-test $ vagrant init fedora/24-cloud-base $ vagrant up