Bug 1470964 - Provide a way to create gluster volumes for access via NFS or SMB
Summary: Provide a way to create gluster volumes for access via NFS or SMB
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Gdeploy
Version: 0.10.7-0.0.20
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-14 07:17 UTC by Sahina Bose
Modified: 2022-01-18 12:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-30 12:09:21 UTC
oVirt Team: Gluster
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44489 0 None None None 2022-01-18 12:36:40 UTC

Description Sahina Bose 2017-07-14 07:17:01 UTC 
Description of problem:

In the hyperconverged setup, there's increasing demand for the ability to run gluster volumes on the 3 node setup, that can be accessed via NFS or SMB. (These volumes will not be used as storage domains in oVirt)
The cockpit-gdeploy plugin should allow the user to create and configure volume for NFS or SMB access.

Version-Release number of selected component (if applicable):
4.1

How reproducible:
NA
Comment 1 Sahina Bose 2017-07-14 07:48:59 UTC 
Sean, the volumes that are created for NFS/SMB access could be any volume type right? I mean not restricted to replica 3 - could be disperse / distributed
Comment 2 Sean Murphy 2017-09-22 14:09:51 UTC 
(In reply to Sahina Bose from comment #1)
> Sean, the volumes that are created for NFS/SMB access could be any volume
> type right? I mean not restricted to replica 3 - could be disperse /
> distributed

Correct - the volume type should not be restricted.
Comment 3 Sandro Bonazzola 2019-01-28 09:41:59 UTC 
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Comment 4 Sahina Bose 2019-01-30 12:09:21 UTC 
Priority for this ask has changed, and closing this bug now.
Note You need to log in before you can comment on or make changes to this bug.