On Thu, Dec 17, 2015 at 4:33 PM, Deepak Shetty <dpkshetty@xxxxxxxxx> wrote:
Where / How do you indicate whether the underlying GlusterFS is used/tested using fusemount or libgfapi method or both ?
There is no mechanism as of today to run the same test on GFAPI of FUSE mount. Hence the tests explicitly choose the mount option.
The above line holds true for smoke, functional, regression and performance categories.
If your question is regarding integration testing, it would depend entirely on how the outside product likes to integrate with Gluster.
On Wed, Nov 25, 2015 at 5:39 PM, Raghavendra Talur <rtalur@xxxxxxxxxx> wrote:_______________________________________________Hi All,Here is a table representing the current state of Gluster testing.* Things in green are categories for which we have some kind of testing in place.* Things in red are the ones which don't have any tests.* Things in yellow are the ones which have no known tests or are not managed by Gluster community.
Test Category/Sub-Category smoke source build + Posix complaince + Dbench functional tests/basic regression tests/bugs performance regression N/A integration Backends/FS Protocols Consumers/Cloud Environments Tools libgfapi bindings OS environment xfs smb qemu gdeploy java firewalld ext4 nfs openstack/cinder heketi python ufw btrfs swift openshift/docker/containers ruby selinux zfs aws go apparmor azure hadoop update major version upgrades minor version upgrades longevity a. memory leaks
b. log accumulationdistro packaging a. pkg build + smoke
b. sysvinit/systemd
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
