From aa2f48dbd8f8ff1d10230fb9656f2ac7d99a48f8 Mon Sep 17 00:00:00 2001 From: Shyam Date: Mon, 27 Feb 2017 13:25:14 -0500 Subject: doc: Moved feature pages that were delivered as a part of 3.10.0 Change-Id: I35a6b599eebbe42b5ef1244d2d72fa103bcf8acb Signed-off-by: Shyam Reviewed-on: https://review.gluster.org/16775 Reviewed-by: Vijay Bellur --- done/GlusterFS 3.10/client-opversion.md | 111 ++++++++++++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 done/GlusterFS 3.10/client-opversion.md (limited to 'done/GlusterFS 3.10/client-opversion.md') diff --git a/done/GlusterFS 3.10/client-opversion.md b/done/GlusterFS 3.10/client-opversion.md new file mode 100644 index 0000000..8c9991e --- /dev/null +++ b/done/GlusterFS 3.10/client-opversion.md @@ -0,0 +1,111 @@ +Feature +------- + +Summary +------- + +Support to get the op-version information for each client through the volume +status command. + +Owners +------ + +Samikshan Bairagya + +Current status +-------------- + +Currently the only way to get an idea regarding the version of the connected +clients is to grep for "accepted client from" in /var/log/glusterfs/bricks. +There is no command that gives that information out to the users. + +Related Feature Requests and Bugs +--------------------------------- + +https://bugzilla.redhat.com/show_bug.cgi?id=1409078 + +Detailed Description +-------------------- + +The op-version information for each client can be added to the already existing +volume status command. `volume status clients` currently gives the +following information for each client: + +* Hostname:port +* Bytes Read +* Bytes Written + +Benefit to GlusterFS +-------------------- + +This would make the user-experience better as it would make it easier for users +to know the op-version of each client from a single command. + +Scope +----- + +#### Nature of proposed change + +Adds more information to `volume status clients` output. + +#### 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 +----------- + +This can be tested by having clients with different glusterfs versions connected +to running volumes, and executing the `volume status clients` +command. + +User Experience +--------------- + +Users can use the `volume status clients` command to get +information on the op-versions for each client along with information that were +already available like (hostname, bytes read and bytes written). + +Dependencies +------------ + +None + +Documentation +------------- + +None. + +Status +------ + +In development. + +Comments and Discussion +----------------------- + + 1. Discussion on gluster-devel ML: + - [Thread 1](http://www.gluster.org/pipermail/gluster-users/2016-January/025064.html) + - [Thread 2](http://www.gluster.org/pipermail/gluster-devel/2017-January/051820.html) + 2. [Discussion on Github](https://github.com/gluster/glusterfs/issues/79) + -- cgit