summaryrefslogtreecommitdiffstats
path: root/accepted/gluster-nfs-off.md
diff options
context:
space:
mode:
authorNiels de Vos <ndevos@redhat.com>2016-04-27 10:11:51 +0200
committerNiels de Vos <ndevos@redhat.com>2016-04-29 01:32:44 -0700
commit689a2374009b41d0790265cb277bb924ffa5cff5 (patch)
tree6d129f3f1f6ac4983aad0b30236f3cc22a3ae618 /accepted/gluster-nfs-off.md
parent539d750fe573633a4df9fb26035a028207210f32 (diff)
Move Gluster/NFS disabled by default to 'done/3.8'
Change-Id: I192df0b5e42f8f442bc674f46b8f4405e58d6ef9 Signed-off-by: Niels de Vos <ndevos@redhat.com> Reviewed-on: http://review.gluster.org/14087 Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
Diffstat (limited to 'accepted/gluster-nfs-off.md')
-rw-r--r--accepted/gluster-nfs-off.md117
1 files changed, 0 insertions, 117 deletions
diff --git a/accepted/gluster-nfs-off.md b/accepted/gluster-nfs-off.md
deleted file mode 100644
index 007d9fd..0000000
--- a/accepted/gluster-nfs-off.md
+++ /dev/null
@@ -1,117 +0,0 @@
-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 <kkeithle [at] redhat.com>
-Niels De Vos <ndevos [at] redhat.com>
-
-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
------------------------
-