[Bugs] [Bug 1219843] New: [RFE] Data Tiering:Need a way from CLI to identify hot and cold tier bricks easily

Fri May 8 13:09:10 UTC 2015

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

            Bug ID: 1219843
           Summary: [RFE] Data Tiering:Need a way from CLI to identify hot
                    and cold tier bricks easily
           Product: GlusterFS
           Version: 3.7.0
         Component: tiering
          Keywords: Triaged
          Severity: medium
          Priority: urgent
          Assignee: bugs at gluster.org
          Reporter: rkavunga at redhat.com
        QA Contact: bugs at gluster.org
                CC: annair at redhat.com, bugs at gluster.org,
                    gluster-bugs at redhat.com, nchilaka at redhat.com,
                    nsathyan at redhat.com, rkavunga at redhat.com
        Depends On: 1206546
            Blocks: 1186580 (qe_tracker_everglades), 1199352
                    (glusterfs-3.7.0), 1219842

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

Description of problem:
======================
Currently there is no easy way of identifying hot and cold tier bricks easily
from the CLI commands like volume info or volume status.
If at all the user wants to know which brick belongs to which tier, he/she
needs to issue a getfattr to see the tier hash value, which is cumbersome.
It would be ideal to display the tiers and the respective bricks in the volume
info command output itself.
For eg, the current o/p of "volume info " of a  distribute tiered volume is as
below:
[root at rhs-client44 ~]# gluster v info tiervol10

Volume Name: tiervol10
Type: Tier
Volume ID: e6223c16-50fa-4916-b8b9-a83db6e8ec6c
Status: Started
Number of Bricks: 5 x 1 = 5
Transport-type: tcp
Bricks:
Brick1: rhs-client37:/pavanbrick2/tiervol10/hb1
Brick2: rhs-client44:/pavanbrick2/tiervol10/hb1
Brick3: rhs-client44:/pavanbrick1/tiervol10/b1
Brick4: rhs-client37:/pavanbrick1/tiervol10/b1
Brick5: rhs-client38:/pavanbrick1/tiervol10/b1

I would suggest something like below should be o/p:
[root at rhs-client44 ~]# gluster v info tiervol10

Volume Name: tiervol10
Type: Tier
Volume ID: e6223c16-50fa-4916-b8b9-a83db6e8ec6c
Status: Started
Number of Bricks: 5 x 1 = 5
Transport-type: tcp

Bricks:
HOT TIER:
Brick1: rhs-client37:/pavanbrick2/tiervol10/hb1
Brick2: rhs-client44:/pavanbrick2/tiervol10/hb1

COLD TIER:
Brick1: rhs-client44:/pavanbrick1/tiervol10/b1
Brick2: rhs-client37:/pavanbrick1/tiervol10/b1
Brick3: rhs-client38:/pavanbrick1/tiervol10/b1

Version-Release number of selected component (if applicable):
============================================================
3.7 upstream nightlies build
http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs/epel-6-x86_64/glusterfs-3.7dev-0.803.gitf64666f.autobuild/

glusterfs 3.7dev built on Mar 26 2015 01:04:24

How reproducible:
================
Easily reproducible

Steps to Reproduce:
1.create a distribute volume
2.attach a tier using attach-tier to the volume
3.issue a volume info or volume status command

Actual results:
==============
No easy way to identify cold/hot tier bricks

Expected results:
================
Enhance the volume info o/p to display hot and cold bricks dedicatedly.

--- Additional comment from Anand Avati on 2015-04-22 02:28:52 EDT ---

REVIEW: http://review.gluster.org/10328 (cli/tiering: display hot tier, and
cold tier separately) posted (#1) for review on master by mohammed rafi  kc
(rkavunga at redhat.com)

--- Additional comment from Anand Avati on 2015-04-22 10:57:15 EDT ---

REVIEW: http://review.gluster.org/10328 (cli/tiering: display hot tier, and
cold tier separately) posted (#2) for review on master by mohammed rafi  kc
(rkavunga at redhat.com)

--- Additional comment from Dan Lambright on 2015-04-22 12:54:43 EDT ---

--- Additional comment from Mohammed Rafi KC on 2015-04-23 07:18:13 EDT ---

upstream patch : http://review.gluster.org/#/c/10328/

--- Additional comment from Anand Avati on 2015-04-27 02:35:27 EDT ---

REVIEW: http://review.gluster.org/10328 (cli/tiering: display hot tier, and
cold tier separately) posted (#3) for review on master by mohammed rafi  kc
(rkavunga at redhat.com)

--- Additional comment from Anand Avati on 2015-04-29 09:06:12 EDT ---

REVIEW: http://review.gluster.org/10328 (cli/tiering: display hot tier, and
cold tier separately) posted (#4) for review on master by mohammed rafi  kc
(rkavunga at redhat.com)

--- Additional comment from Anand Avati on 2015-05-02 09:23:23 EDT ---

REVIEW: http://review.gluster.org/10328 (cli/tiering: display hot tier, and
cold tier separately) posted (#5) for review on master by mohammed rafi  kc
(rkavunga at redhat.com)

--- Additional comment from Anand Avati on 2015-05-03 07:01:05 EDT ---

REVIEW: http://review.gluster.org/10328 (cli/tiering: display hot tier, and
cold tier separately) posted (#6) for review on master by mohammed rafi  kc
(rkavunga at redhat.com)

--- Additional comment from Anand Avati on 2015-05-05 04:41:35 EDT ---

REVIEW: http://review.gluster.org/10328 (cli/tiering: display hot tier, and
cold tier separately) posted (#7) for review on master by mohammed rafi  kc
(rkavunga at redhat.com)

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1199352
[Bug 1199352] GlusterFS 3.7.0 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1206546
[Bug 1206546] [RFE] Data Tiering:Need a way from CLI to identify hot and
cold tier bricks easily
https://bugzilla.redhat.com/show_bug.cgi?id=1219842
[Bug 1219842] [RFE] Data Tiering:Need a way from CLI to identify hot and
cold tier bricks easily
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.