Raghavendra Talur 78305ce960 tests: Introduce a Vagrant VM based test environment
This introduces a mechanism using which a developer
could easily test the Gluster code in a VM environment.

Also, it will help bring uniformity in the environments
used by various developers.

How to use:
1. git checkout -b custom-branch-name
2. Make changes
3. Execute ./run-tests-in-vagrant.sh

What happens in the background:
1. A new directory is created:
    tests/vagrant/vagrant-custom-branch-name

   It will serve as the Vagrant dir which has the
   Vagrantfile and related ansible playbooks.

   The VM is started using Vagrant and provisioned
   using ansible.

2. The source dir is recursively copied over to the
   VM under /home/vagrant/glusterfs.

3. Gluster is source installed in VM.

What happens in the foreground:
1. run-tests.sh is executed in VM using ssh and output is displayed
   in the same terminal with option to use ctrl-c to interrupt the test
   midway. The VM would still persist and you could ssh into it.

Also, you can checkout a different branch elsewhere and execute
run-tests-in-vagrant.sh there to get another VM which would
execute tests on that code.

If you wish to make some changes in the code, you could:
a. Change the code in host and run the script again to repeat
   the whole process.
OR
b. vagrant ssh into the VM and make the changes in the VM.

Co-authored-by: Kaushal M <kaushal@redhat.com>
Co-authored-by: Michael Adam <obnox@samba.org>

Change-Id: Ic87801172c8b614cdecbdf2a765e1b3370a5faf7
BUG: 1291537
Signed-off-by: Michael Adam <obnox@samba.org>
Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
Reviewed-on: http://review.gluster.org/12753
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
2015-12-28 00:50:36 -08:00
2015-11-16 07:40:43 -08:00
2014-04-16 06:38:06 -07:00
2010-03-12 04:09:34 -08:00
2015-09-01 06:08:59 -07:00
2011-07-18 17:24:14 +05:30
2014-09-16 02:30:36 -07:00

For information about contributing to GlusterFS, please follow the below link : Contributing to GlusterFS community

GlusterFS does not follow the GitHub: Fork & pull workflow but use Gerrit for code review.

The development guidelines are detailed in Development Workflow.

The GlusterFS documentation can be found at Documentation

For more info, please visit http://www.gluster.org/.

Description
No description provided
Readme 86 MiB
Languages
C 86.6%
Shell 7.5%
Python 3.6%
Perl 0.7%
Makefile 0.4%
Other 0.9%