Description of problem: Once a geo-replication session is created from a volume to a remote volume, the engine should have the ability to monitor the session's status. This includes the following: i) Monitoring the health of the session ii) Monitoring the details of files moved, skipped etc periodically iii) Detecting new sessions that may be created using gluster CLI and updating details of these in the engine database How reproducible: N/A
Tested with RHEV 3.6.3.3 by adding RHGS 3.1.2 RC to 3.5 cluster Geo-replication session could be created, started, monitored and managed from RHEVM UI