Re: [Gluster-Maintainers] Updating the repository's actual 'ACTIVE'ness status

I archived the following projects - gluster/restapi - gluster/glusterd2 - gluster/gcs - gluster/gluster-csi-driver - gluster/gluster-block-restapi - gluster/python-gluster-mgmt-client Please let me know if anyone interested to unarchive and maintain any project from the above list. — regards

[Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #1737

See Changes: -- [...truncated 3.71 MB...] ./tests/basic/afr/granular-esh/replace-brick.t - 9 second ./tests/line-coverage/cli-peer-and-volume-operations.t - 8 second

[Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #1736

See Changes: -- [...truncated 3.69 MB...] ./tests/basic/afr/granular-esh/replace-brick.t - 9 second ./tests/basic/afr/granular-esh/add-brick.t - 9 second

[Gluster-Maintainers] Updating the repository's actual 'ACTIVE'ness status

Hi all, We have 101 repositories in gluster org in github. Only handful of them are being actively managed, and progressing. After seeing https://github.com/gluster/gluster-kubernetes/issues/644, I feel we should at least keep the status of the project up-to-date in the repository, so the users

[Gluster-Maintainers] Fwd: [gluster/glusterfs] Disperse volume only showing one third of the available space on client (#1131)

I am thinking of disabling this option altogether. This was developed to make sure we have better reporting when same disk gets shared by multiple volumes (was an option discussed for container use-cases, and +1 scaling feature. But considering the amount of bugs and confusion it got-in, and as