Bug 1219843

Summary: [RFE] Data Tiering:Need a way from CLI to identify hot and cold tier bricks easily
Product: [Community] GlusterFS Reporter: Mohammed Rafi KC <rkavunga>
Component: tieringAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: urgent    
Version: 3.7.0CC: annair, bugs, gluster-bugs, nchilaka, nsathyan, rkavunga
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1206546 Environment:
Last Closed: 2015-05-08 22:19:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1206546    
Bug Blocks: 1186580, 1199352, 1219842, 1260923    

Description Mohammed Rafi KC 2015-05-08 13:09:10 UTC
+++ 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@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@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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

--- 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)

Comment 1 Anand Avati 2015-05-08 13:12:17 UTC
REVIEW: http://review.gluster.org/10676 (cli/tiering: volume info should display details about tier) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Mohammed Rafi KC 2015-05-08 22:19:23 UTC

*** This bug has been marked as a duplicate of bug 1219842 ***