search

Tendrl / specifications

Tendrl specs go here
GNU Lesser General Public License v3.0
6 stars 16 forks source link

Gluster Metrics-MileStone 2 #229

Closed anmolbabu closed 6 years ago

anmolbabu commented 7 years ago

tendrl-bug-id: Tendrl/specifications#188 Signed-off-by: anmolbabu anmolbudugutta@gmail.com

anmolbabu commented 7 years ago

This is a WIP PR

@nthomas-redhat @shtripat @r0h4n @brainfunked Please review

shtripat commented 7 years ago

Based on discussion with Aravinda, the volume level geo-rep session could be in one of the states below

The logic to calculate these values could be as below

if no of non-faulty pairs is zero (all the pairs status is faulty):
    volume geo-rep status = down
else:
    if no of non faulty pairs is equal to the no of bricks in the volume (all the pairs are either active/passive):
        volume geo-rep status = up
    else:
        volume geo-rep status = partial
shtripat commented 7 years ago

As per latest discussion with @nthomas-redhat amd @nnDarshan we would add volume level aggregated geo-rep status value as per above logic. Basically it would be a field like cluster/{int-id}/Volumes/{vol-id}/GeoReplicationSessions/{session_id}/status which would be an aggregated value from the geo-rep pair status values.