Bug 1138116

Summary: [RFE] Support monitoring of geo-replication sessions for a gluster volume
Product: [oVirt] ovirt-engine Reporter: Sahina Bose <sabose>
Component: RFEsAssignee: Sahina Bose <sabose>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: bugs, gklein, iheim, mgoldboi, rbalakri, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: FutureFeature
Target Release: 3.6.0Flags: rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
sasundar: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764 Doc Type: Enhancement
Doc Text:
Feature: Enables users to easily manage geo-replication between managed clusters
 Story Points: ---
Clone Of:
: 1224279 (view as bug list) Environment:
Last Closed: 2016-03-11 07:21:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1187461, 1224279    

Description Sahina Bose 2014-09-04 06:18:56 UTC 
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
Comment 2 SATHEESARAN 2016-02-25 08:40:22 UTC 
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