Change-Id: I1a9cefd16ddb376d8c496089d114c92efa1fd1ea
Signed-off-by: Manisha Saini <msaini@redhat.com>

Adding tests to verify memory leak when
1. Management encryption enabled and gluster v heal info
   is run for 12 hrs

2. Management encryption is enabled, brick-mux enabled

Change-Id: If6ff76afe87490a135c450cbec99bceb3a6011ae
Signed-off-by: Pranav <prprakas@redhat.com>

Moving the gluster mem_leak test case to resource_leak
dir

Change-Id: I8189dc9b509a09f793fe8ca2be53e8546babada7
Signed-off-by: Pranav <prprakas@redhat.com>

Scenarios added:
----------------

Test case:
1. Create a volume, start it and mount it.
2. Start I/O from mount point.
3. Check if there are any memory leaks and OOM killers.

Test case:
1. Create a volume, start it and mount it.
2. Set features.cache-invalidation to ON.
3. Start I/O from mount point.
4. Run gluster volume heal command in a loop
5. Check if there are any memory leaks and OOM killers on servers.

Design change:
--------------

- self.id() is moved into test class as it was hitting bound
errors in the original logic.
- Logic changed for checking leaks fuse.
- Fixed breakage in methods where ever needed.

Change-Id: Icb600d833d0c08636b6002abb489342ea1f946d7
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>