You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Gluster admin, I want to be able to know which bricks are arbiter bricks. Note: Just looking at volume type does not tell me if a volume is a distributed-replicat using the arbiter feature or not.
# gluster volume info
Volume Name: testvol
Type: Distributed-Replicate
Volume ID: ae6c4162-38c2-4368-ae5d-6bad141a4119
Status: Created
Number of Bricks: 2 x (2 + 1) = 6
Transport-type: tcp
Bricks:
Brick1: server1:/bricks/brick
Brick2: server2:/bricks/brick
Brick3: server3:/bricks/brick (arbiter)
Brick4: server4:/bricks/brick
Brick5: server5:/bricks/brick
Brick6: server6:/bricks/brick (arbiter)
Options Reconfigured :
transport.address-family: inet
performance.readdir-ahead: on
I proposed that we show arbiter in Brick Details and also show device UUID in the Brick Details.
Regarding UUID, due to hot swappable disks being commonly used, it would be good to show the device UUID as this is needed for Day 2 and Day 3 operations, e.g. disk/brick replacement.
For the Brick Details views for the Host and Volume, I suggest we do the following:
Add new column to indicate if brick is an arbiter or not
Remove Port column
Add new column for UUID; Note: This is similar to information one gets from running the ls -l /dev/disk/by-uuid command.
Add filter option for Arbiter (Filter by Arbiter Brick, Data Arbiter), Disk Device UUID
The following is a brick details for Volume mockup:
As a Gluster admin, I want to be able to know which bricks are arbiter bricks. Note: Just looking at volume type does not tell me if a volume is a distributed-replicat using the arbiter feature or not.
@nthomas-redhat @Tendrl/qe @shirshendu @shtripat @GowthamShanmugam @anmolsachan
The text was updated successfully, but these errors were encountered: