Bug 1507841

Currently the volume level georep session status is calculated in tendrl based on status values reported from `gluster get-state` for individual georep pairs. the logic is as below

--------------------
if no of faulty pairs == 0: volume level georep status is marked as active(UP)
else if no of faulty pairs == total no of pairs: volume level georep status is marked as faulty (DOWN)
else volume level georep status is partial
---------------------

I would request suggestions from Aravinda, Atin, Amar to comment and suggest.

Also I feel in this situation all the pairs would move to faulty state and next sync cycle in gluster-integration would mark the volume level georep session overall as DOWN. Darshan??

(In reply to Shubhendu Tripathi from comment #2)
> Currently the volume level georep session status is calculated in tendrl
> based on status values reported from `gluster get-state` for individual
> georep pairs. the logic is as below
> 
> --------------------
> if no of faulty pairs == 0: volume level georep status is marked as
> active(UP)

Add one more condition if num_faulty_pairs == 0 and num_stopped_or_paused_or_created == 0

> else if no of faulty pairs == total no of pairs: volume level georep status
> is marked as faulty (DOWN)

Add one more condition if num_faulty_pairs == total_pairs and num_stopped_or_paused_or_created == 0

> else volume level georep status is partial

Add one more condition elif num_stopped_or_paused_or_created == 0

> ---------------------
> 
> I would request suggestions from Aravinda, Atin, Amar to comment and suggest.

For Grafana you can push the following states

- created
- up
- down
- partial
- stopped
- paused

Thanks Aravinda for clearly marking the requirements. So as per my understanding the logic could be as below now

-----------------
if all pairs are in created state, georep session status = CREATED

if no faulty pairs and num_stopped_or_paused_or_created == 0, georep session status = UP 

if no of faulty pairs = total no of pairs and num_stopped_or_paused_or_created == 0, georep session status = DOWN

if all pairs are in stopped state, georep sesion status = STOPPED

if all pairs in paused state, georep session status = PAUSED
-----------------

@Aravinda, Ack if this looks fine.

@Ju, ack if these states could be depicted in dashboards.

(In reply to Shubhendu Tripathi from comment #6)
> Thanks Aravinda for clearly marking the requirements. So as per my
> understanding the logic could be as below now
> 
> -----------------
> if all pairs are in created state, georep session status = CREATED
> 
> if no faulty pairs and num_stopped_or_paused_or_created == 0, georep session
> status = UP 
> 
> if no of faulty pairs = total no of pairs and
> num_stopped_or_paused_or_created == 0, georep session status = DOWN
> 
> if all pairs are in stopped state, georep sesion status = STOPPED
> 
> if all pairs in paused state, georep session status = PAUSED
> -----------------
> 
> @Aravinda, Ack if this looks fine.
> 
> @Ju, ack if these states could be depicted in dashboards.

Looks good to me.

@Ju, we need comments from you regarding UX here.

@shtripat

Ack the new 6 statuses for geo-repl sessions, and these should be reflected on the applicable Grafana dashboards.

CREATED: Geo-replication session is established
STOPPED: Geo-replication session is stopped
ONLINE/UP: Geo-replication session (All bricks) are UP and Running
OFFLINE/DOWN: Geo-replication session (All bricks) are Down
PARTIAL: Geo-replication session - some bricks are Online and Some bricks are offline
PAUSED: all the pairs are in paused state

I've updated https://github.com/Tendrl/gluster-integration/issues/459 and https://github.com/Tendrl/specifications/issues/222 accordingly.

After stopping the geo-rep session as well as the slave volume, the slave volume going down was reflected successfully but the session moving to "stopped" state was not reflected after waiting for about 10 minutes after stopping the session. 

    Checked in the following version : tendrl-api-1.5.4-2.el7rhgs.noarch

All the states with respect geo-replication were reflected correctly on the Grafana dashboard. 

Moving this bug to verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3478