Bug 1377437

Summary:	[RFE] Modularizing backend snapshot creation as separate plugin
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, rkavunga
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 05:54:53 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:

Description Avra Sengupta 2016-09-19 17:22:39 UTC

Description of problem:
Currently we use lvm based snapshots in the backend to create snapshot volumes of regular gluster volumes. We need to segregate the lvm specific code, and modularize it in a pluggable format, such that other backend filesystems and their respective snapshots too can be supported, without having to interfere with the basic snapshot infrastructure or other components.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2016-09-23 10:28:31 UTC

REVIEW: http://review.gluster.org/15562 ([BugId:1377437][Patch9]: Refering to the bug ID, - Minor header file inclusion fixes) posted (#1) for review on master by Anonymous Coward

Comment 2 Worker Ant 2016-12-15 06:34:46 UTC

REVIEW: http://review.gluster.org/16138 (This patch follows the discussion from the gluster-devel mail chain of, modularizing backend snapshot code as pluggable modules, which would essentially support more than one snapshot backend. For ex: lvm, zfs, brtfs etc.) posted (#1) for review on master by Anonymous Coward

Comment 4 Mohammed Rafi KC 2018-10-16 05:54:53 UTC


*** This bug has been marked as a duplicate of bug 1426749 ***