From 0db08ade29746822c6d679b1b596f7ce9599db5c Mon Sep 17 00:00:00 2001 From: Samikshan Bairagya Date: Tue, 13 Dec 2016 18:03:50 +0530 Subject: Feature page for max-op-version retrieval support Change-Id: Ib83c345e7071d38ecb1e47604fa9948e233738b3 Signed-off-by: Samikshan Bairagya Reviewed-on: http://review.gluster.org/16118 Reviewed-by: Atin Mukherjee Reviewed-by: Kaushal M Tested-by: Kaushal M --- under_review/max-opversion.md | 118 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 118 insertions(+) create mode 100644 under_review/max-opversion.md diff --git a/under_review/max-opversion.md b/under_review/max-opversion.md new file mode 100644 index 0000000..16d4ee4 --- /dev/null +++ b/under_review/max-opversion.md @@ -0,0 +1,118 @@ +Feature +------- + +Summary +------- + +Support to retrieve the maximum supported op-version (cluster.op-version) in a +heterogeneous cluster. + +Owners +------ + +Samikshan Bairagya + +Current status +-------------- + +Currently users can retrieve the op-version on which a cluster is operating by +using the gluster volume get command on the global option cluster.op-version as +follows: + +# gluster volume get cluster.op-version + +There is however no way for an user to find out the maximum op-version to which +the cluster could be bumped upto. + +Related Feature Requests and Bugs +--------------------------------- + +https://bugzilla.redhat.com/show_bug.cgi?id=1365822 + +Detailed Description +-------------------- + +A heterogeneous cluster operates on a common op-version that can be supported +across all the nodes in the trusted storage pool.Upon upgrade of the nodes in +the cluster, the cluster might support a higher op-version. However, since it +is currently not possible for the user to get this op-version value, it is +difficult for them to bump up the op-version of the cluster to the supported +value. + +The maximum supported op-version in a cluster would be the minimum of the +maximum op-versions in each of the nodes. To retrieve this, the volume get +functionality could be invoked as follows: + +# gluster volume get all cluster.max-op-version + +Benefit to GlusterFS +-------------------- + +This would make the user-experience better as it would make it easier for users +to know the maximum op-version on which the cluster can operate. + +Scope +----- + +#### Nature of proposed change + +This adds a new non-settable global option, cluster.max-op-version. + +#### 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 on a cluster with at least one node running on version 'n+1' +and others on version 'n' where n = 3.10. The maximum supported op-version +(cluster.max-op-version) should be returned by `volume get` as n in this case. + +User Experience +--------------- + +Upon upgrade of one or more nodes in a cluster, users can get the new maximum +op-version the cluster can support. + +Dependencies +------------ + +None + +Documentation +------------- + +None. + +Status +------ + +In development. + +Comments and Discussion +----------------------- + + 1. [Discussion on gluster-devel ML](http://www.gluster.org/pipermail/gluster-devel/2016-December/051650.html) + 2. [Discussion on Github](https://github.com/gluster/glusterfs/issues/56) + -- cgit