From a15f64598613ca9aae0a373c4c466bf6367c37fd Mon Sep 17 00:00:00 2001 From: Kaleb S KEITHLEY Date: Tue, 15 Mar 2016 06:19:41 -0400 Subject: gluster-nfs-off: change default value of nfs.disable to true Next step to eventually deprecate glusterfs nfs server in favor of ganesha.nfsd Change-Id: I1ec86457429b3a5f382125b38b24e2cb70e9871a Signed-off-by: Kaleb S KEITHLEY Reviewed-on: http://review.gluster.org/13739 Reviewed-by: Niels de Vos --- under_review/gluster-nfs-off.md | 117 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 117 insertions(+) create mode 100644 under_review/gluster-nfs-off.md diff --git a/under_review/gluster-nfs-off.md b/under_review/gluster-nfs-off.md new file mode 100644 index 0000000..007d9fd --- /dev/null +++ b/under_review/gluster-nfs-off.md @@ -0,0 +1,117 @@ +Feature +------- + +Gluster NFS Defaults to Off. + +Summary +------- + +Currently, when a volume is created and started, the default setting for nfs.disable +is off/false; when the volume is started, a glusterfs nfs server process is started. + +The Gluster NFS server is NFSv3 only, and is not being actively developed. Meanwhile +NFS-Ganesha supprts NFSv3, NFSv4, NFSv4.1, and pNFS; and NFSv4.2 is under development. + +Initial support for NFS-Ganesha first appeared in GlusterFS 3.7 with the introduction +of CLI support for using ganesha.nfsd instead of the glusterfs nfs server, however +the glusterfs nfs server remained enabled by default. + +The next step toward eventual deprecation of the glusterfs nfs server is to change the +default setting for nfs.disable to on/true. Users who wish to continue to use the +glusterfs nfs server will have to explicitly set nfs.disable to off/false after they +create the volume. Existing volumes that had nfs.disable set to off/false will not be +altered, those volumes will continue to start the glusterfs nfs server. + +Eventually the glusterfs nfs server will be fully deprecated in favor of NFS-Ganesha. + +Owners +------ + +Kaleb KEITHLEY +Niels De Vos + +Current status +-------------- + +Under development + +Related Feature Requests and Bugs +--------------------------------- + +None. + +Detailed Description +-------------------- + +None + +Benefit to GlusterFS +-------------------- + +Need to maintain the NFS server xlator is eliminated. + + +Scope +----- + +#### Nature of proposed change + +Change default option value in xlators/mgmt/glusterd/... + +#### Implications on manageability + +None + +#### Implications on presentation layer + +None + +#### Implications on persistence layer + +None + +#### Implications on 'GlusterFS' backend + +None + +#### Modification to GlusterFS metadata + +None + +#### Implications on 'glusterd' + +None + +How To Test +----------- + +1. Start glusterd +2. Create volume e.g. `gluster volume create $vol $host:$path [force]` +3. Start volume, e.g. `gluster volume start $vol` +4. check ps to see that glusterfs nfs process is not started + +User Experience +--------------- + +None + +Dependencies +------------ + +None + +Documentation +------------- + +Change any reference to default value of nfs.disable + +Status +------ + +One line change to .../xlators/mgmt/glusterd/src/glusterd-nfs-svc.c has been +posted for review at http://review.gluster.org/13738 + + +Comments and Discussion +----------------------- + -- cgit