[Bugs] [Bug 1488018] New: [RFE] Gluster get state command should provide volume and cluster utilization related information

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1488018

            Bug ID: 1488018
           Summary: [RFE] Gluster get state command should provide volume
                    and cluster utilization related information
           Product: Red Hat Gluster Storage
           Version: 3.3
         Component: glusterd
          Keywords: Triaged
          Assignee: amukherj at redhat.com
          Reporter: amukherj at redhat.com
        QA Contact: bmekala at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    dnarayan at redhat.com, rhs-bugs at redhat.com,
                    sbairagy at redhat.com, storage-qa-internal at redhat.com,
                    vbellur at redhat.com
        Depends On: 1431192



+++ This bug was initially created as a clone of Bug #1431192 +++

Description of problem:
Currently "gluster get-state" command does not give any volume and cluster
usage related information. It should give information about the usage of volume
and cluster like what is the full size of a volume/cluster and how much of it
is currently full. Also it should give the status of cluster just like
gstatus(https://github.com/gluster/gstatus) tool provides

Version-Release number of selected component (if applicable):
3.9

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
If its very costly to provide this information please enhance gluster get-state
to take an option something like "--detail". When "--detail" is provided
get-state must provide all the details including the ones which are costly to
fetch. Without this option it should only give information which are not
costly.

This is needed for tendrl project:
https://redhat.invisionapp.com/share/589XIRJBW#/screens/213318639

--- Additional comment from Samikshan Bairagya on 2017-03-15 07:35:18 EDT ---

This is what the gstatus README says:

"Capacity information is derived from the brick information taken from a 'vol
status detail' command. The accuracy of this number therefore depends on the
nodes/bricks being all up - elements missing from the configuration will simply
be missing from the calculation."

The get-state CLI doesn't intend to aggregate results from individual nodes to
provide a cluster level result like gstatus does. What get-state can do is
provide the per-node information needed to compute the required data like
volume and cluster utilisation on another layer.

--- Additional comment from Worker Ant on 2017-04-10 09:18:12 EDT ---

REVIEW: https://review.gluster.org/17029 (glusterd: Add brick capacity details
to get-state CLI output) posted (#1) for review on master by Samikshan Bairagya
(samikshan at gmail.com)

--- Additional comment from Worker Ant on 2017-04-14 14:14:39 EDT ---

REVIEW: https://review.gluster.org/17029 (glusterd: Add brick capacity details
to get-state CLI output) posted (#2) for review on master by Samikshan Bairagya
(samikshan at gmail.com)

--- Additional comment from Worker Ant on 2017-04-14 21:40:51 EDT ---

COMMIT: https://review.gluster.org/17029 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit c09f5a28bfd14066f9b8cfca53c7a9d999f1613e
Author: Samikshan Bairagya <samikshan at gmail.com>
Date:   Mon Apr 10 18:46:42 2017 +0530

    glusterd: Add brick capacity details to get-state CLI output

    Change-Id: I53fe180e71d41d56b129254b93bb74014a2cdb43
    BUG: 1431192
    Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
    Reviewed-on: https://review.gluster.org/17029
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

--- Additional comment from Shyamsundar on 2017-05-30 14:47:11 EDT ---

This bug is getting closed because a release has been made available that
should address the reported issue. In case the problem is still not fixed with
glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages
for several distributions should become available in the near future. Keep an
eye on the Gluster Users mailinglist [2] and the update infrastructure for your
distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1431192
[Bug 1431192] [RFE] Gluster get state command should provide volume and
cluster utilization related information
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=HKk2xsx1XN&a=cc_unsubscribe