Bug 1395607

Summary:	[RFE] Shared volume for NFS-Ganesha should be configurable
Product:	Red Hat Gluster Storage	Reporter:	Niels de Vos <ndevos>
Component:	common-ha	Assignee:	Patric Uebele <puebele>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.2	CC:	apaladug, fw, jthottan, pasik, puebele, rhs-bugs, skoduri, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature, Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-09 08:21:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.