Bug 1395607 - [RFE] Shared volume for NFS-Ganesha should be configurable
Summary: [RFE] Shared volume for NFS-Ganesha should be configurable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: common-ha
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Patric Uebele
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 09:49 UTC by Niels de Vos
Modified: 2019-07-09 08:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-09 08:21:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Niels de Vos 2016-11-16 09:49:57 UTC 
Description of problem:
In certain environments it makes sense to have different NFS-Ganesha clusters on top of a single Trusted Storage Pool. At the moment it is not possible to configure two or more NFS-Ganesha clusters without editing the ganesha-ha.sh script and modifying the location of the shared volume.

Most likely, the HA_VOL_MNT variable in the ganesha-ha.sh script should be configurable through the ganesha-ha.conf file, with the current default in case it is missing. Manual creation and mounting of the non-standard shared volume is acceptable.

Separate shared volumes might be the best approach, but maybe it makes sense to be able to use different directories on the same shared volume too?
Comment 5 Kaleb KEITHLEY 2017-08-23 12:36:57 UTC 
storhaug
Comment 9 Patric Uebele 2019-07-09 08:21:45 UTC 
Don't see large demand for this, closing.
Note You need to log in before you can comment on or make changes to this bug.