As of now, gluster integration syncs only the brick details provided by the gluster get state command which is limited to mount point of the brick. Tendrl should gather the underlying device details of the brick which is of more interest to the storage admin.
This detail is something that does not change very often, so tendrl should have an efficient sync strategy for syncing these details. So that it does not hamper the performance.
nnDarshan
commented
7 years ago
As of now, gluster integration syncs only the brick details provided by the
gluster get statecommand which is limited to mount point of the brick. Tendrl should gather the underlying device details of the brick which is of more interest to the storage admin. This detail is something that does not change very often, so tendrl should have an efficient sync strategy for syncing these details. So that it does not hamper the performance.