Bug 1249997 - [RFE] [Future Feature] FUSE for Microsoft Windows clients
[RFE] [Future Feature] FUSE for Microsoft Windows clients
Status: CLOSED WONTFIX
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: fuse (Show other bugs)
unspecified
x86_64 Windows
unspecified Severity low
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
storage-qa-internal@redhat.com
: FutureFeature, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-04 06:14 EDT by Marcel Hergaarden
Modified: 2018-04-02 07:25 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-02 07:25:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marcel Hergaarden 2015-08-04 06:14:54 EDT
Description of problem:
RHGS can only be used with either NFS or SMB in MS Windows environments.
Additional software like i.e. CTDB needs to be used to bring on semi redundancy as natively present within the GlusterFS FUSE protocol.

Version-Release number of selected component (if applicable):
N/A

How reproducible:
Setup an MS Windows client, connect to RHGS. Fuse is not an option here.

Steps to Reproduce:
1.Install Windows
2.Connect to RHGS
3.No FUSE capability

Actual results:
N/A

Expected results:
N/A

Additional info:
Having a GlusterFS FUSE client for MS Windows would enable us to have more capabilities in customer cases where MS WIndows environments are being used.
Customers sometimes ask for this kind of functionality.
Comment 4 Amar Tumballi 2018-04-02 07:25:23 EDT
We are not planning to fix this anytime in near future. But people who want to use gluster Backend on fuse can use 'gluster-block' project.

Closing it as a WONTFIX, please talk to product management to get this feature agreed for some future release.

Note You need to log in before you can comment on or make changes to this bug.