That is great. I just relabled all the FSAL_GLUSTER github issues that were labeled as UNSUPPORTED FSAL as GLUSTER.
If you could start taking a look at them, that would be a big help.
We also invite you to join our weekly community call, Tuesday’s 7:00 AM Pacific Time. If you’d like me to add you to the calendar invite, I will do so, but here’s the call details:
Ganesha community call
Tuesday, April 8 · 7:00 – 8:00am
Time zone: America/Los_Angeles
Google Meet joining info
Video call link: https://meet.google.com/mkh-ctnj-tqz
Or dial: (US) +1 401-702-0462 PIN: 495 972 631#
More phone numbers: https://tel.meet/mkh-ctnj-tqz?pin=2844708468265
Or join via SIP: sip:2844708468265@gmeet.redhat.com
Thanks
Frank
From: Rafi Kavungal [mailto:rafi.kavungal@iternity.com]
Sent: Tuesday, April 8, 2025 7:17 AM
To: Frank Filz <ffilzlnx@mindspring.com>; devel@lists.nfs-ganesha.org
Cc: support@lists.nfs-ganesha.org
Subject: RE: [NFS-Ganesha-Devel] Unsupported FSALs
Hi Frank,
We heavily rely on Gluster FSAL for our archive product. We have two active developers working on the project. While we mostly mastered the gluster project, we are confident that we can support the Gluster FSAL with the help of community. Since NFS-Ganesha is such an important part of our project, we will definitely want to do everything to keep Gluster FSAL moving with Ganesha community.
Let us know how we can take it forward.
Regards
Rafi
| |||||||||||||||||||||||||||||||||||||||||||
|
From: Frank Filz <ffilzlnx@mindspring.com>
Sent: 01 April 2025 02:29 AM
To: devel@lists.nfs-ganesha.org
Cc: support@lists.nfs-ganesha.org
Subject: [NFS-Ganesha-Devel] Unsupported FSALs
Community,
We have a number of FSALs in Ganesha that have no effective support, I’d like to understand who might still be relying on them and if there is anyone who might step up to support them, or whether we can consider removing some on an expedited timeline (normally we declare a FSAL is deprecated in one release, and then remove it in the next). Note that with the magic of git, deleted FSALs could easily be resurrected (though they might not have been updated to match API changes). The risk of not removing unsupported code is first that folks will use code with little or no support and open github issues that cannot effectively be addressed, and that unsupported code may not be properly updated as API changes are made.
The following FSALs are suspect:
src/FSAL/FSAL_VFS/xfs – this is marginally supported, but could be replaced with plain FSAL_VFS
src/FSAL/FSAL_VFS – there is also a Lustre FSAL that is built from this
src/FSAL/FSAL_GLUSTER
src/FSAL/FSAL_LIZARDFS
src/FSAL/FSAL_PROXY_V3
src/FSAL/FSAL_PROXY_V4
src/FSAL/FSAL_KVSFS
src/FSAL/FSAL_SAUNAFS
Thank for your thoughts
Frank Filz