Bug 1363591

Summary:	Geo-replication user driven Events
Product:	[Community] GlusterFS	Reporter:	Aravinda VK <avishwan>
Component:	eventsapi	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-27 18:17:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aravinda VK 2016-08-03 06:58:02 UTC

Description of problem:
Add Events for Geo-replication Operations: Create/Start/Stop/Pause/Resume/Delete/Config Set/Config Reset

Comment 1 Vijay Bellur 2016-08-03 08:25:51 UTC

REVIEW: http://review.gluster.org/15077 (eventsapi: Geo-replication User driven events) posted (#1) for review on master by Aravinda VK (avishwan)

Comment 2 Vijay Bellur 2016-08-04 09:00:53 UTC

COMMIT: http://review.gluster.org/15077 committed in master by Aravinda VK (avishwan) 
------
commit 3b4c9e525e931a703cc526b3fbe27ee86f2fd70a
Author: Aravinda VK <avishwan>
Date:   Wed Aug 3 12:16:43 2016 +0530

    eventsapi: Geo-replication User driven events
    
    Following Geo-replication Events are added
    
    GEOREP_CREATE/GEOREP_START/GEOREP_STOP/GEOREP_DELETE/GEOREP_PAUSE/GEOREP_RESUME
      {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": EVENT_TYPE,
        "message": {
           "master": MASTER_VOLUME_NAME,
           "slave": SLAVE_DETAILS
         }
      }
    
    GEOREP_CONFIG_SET
      {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": GEOREP_CONFIG_SET,
        "message": {
           "master": MASTER_VOLUME_NAME,
           "slave": SLAVE_DETAILS,
           "option": OPTION_NAME,
           "value": OPTION_VALUE
         }
      }
    
    GEOREP_CONFIG_RESET
      {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": GEOREP_CONFIG_RESET,
        "message": {
           "master": MASTER_VOLUME_NAME,
           "slave": SLAVE_DETAILS,
           "option": OPTION_NAME
         }
      }
    
    BUG: 1363591
    Change-Id: I78c81aabd022ebb042b3eae3c6b5a284a6c2801f
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/15077
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Kotresh HR <khiremat>

Comment 3 Shyamsundar 2017-03-27 18:17:28 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report.

glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/