Where / How do you indicate whether the underlying GlusterFS is used/tested using fusemount or libgfapi method or both ?
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 I will send separate mails for each of the categories above highlighting plans for them.Use this thread to indicate addition/deletion/changes to this matrix.We will put this at gluster.org website once it is final.Thanks,Raghavendra Talur & MSV Bhat
_______________________________________________
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