Description of problem:
Incorrect volume info on attaching tier to a disperse volume

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


How reproducible:


Steps to Reproduce:
1. Create a disperse volume 
[root@dhcp35-56 ~]# gluster vol create vol2 disperse 6 redundancy 2 10.70.35.56:/rhs/brick1 10.70.35.67:/rhs/brick1 10.70.35.56:/rhs/brick2 10.70.35.67:/rhs/brick2 10.70.35.56:/rhs/brick3 10.70.35.67:/rhs/brick3 force

2.Attach a tier to this volume 
[root@dhcp35-56 ~]# gluster vol attach-tier vol2 replica 2 10.70.35.56:/rhs/brick4 10.70.35.67:/rhs/brick4  force
volume add-brick: success

3. Check the volume info 
Volume Name: vol2
Type: Tier
Volume ID: b267ba15-82df-4842-bd41-ac233592d5ba
Status: Created
Number of Bricks: 4 x 2 = 8
Transport-type: tcp
Bricks:
Brick1: 10.70.35.67:/rhs/brick4
Brick2: 10.70.35.56:/rhs/brick4
Brick3: 10.70.35.56:/rhs/brick1
Brick4: 10.70.35.67:/rhs/brick1
Brick5: 10.70.35.56:/rhs/brick2
Brick6: 10.70.35.67:/rhs/brick2
Brick7: 10.70.35.56:/rhs/brick3
Brick8: 10.70.35.67:/rhs/brick3

Says "4 x 2 =8", which is incorrect. 

Additionally, the volume info should also show the sub components of the tiered volume. In the above case, the user should be able to figure out that the volume is a combination of disperse (cold) and replica (hot). Output should also explicity tell the bricks in either tiers.