Hi Kaushal, As you had suggested on github, I have resubmitted the spec request using gerrit. http://review.gluster.org/#/c/13538/ Regards, Joe ----- Original Message ----- > From: "Joseph Fernandes" <josferna@xxxxxxxxxx> > To: gluster-devel@xxxxxxxxxxx > Cc: "Niels de Vos" <ndevos@xxxxxxxxxx>, "Raghavendra Talur" <rtalur@xxxxxxxxxx>, "Karthik Subrahmanya" > <ksubrahm@xxxxxxxxxx>, "Vijaikumar Mallikarjuna" <vmallika@xxxxxxxxxx> > Sent: Saturday, February 27, 2016 9:32:49 PM > Subject: Re: Proposal of WORM/Retention Translator > > Hi All, > > The pull request for WORM-Compliance is created for gluster-spec > > https://github.com/gluster/glusterfs-specs/pull/8 > > Please review it and merge. > > Regards, > Joe > > ----- Original Message ----- > From: "Karthik Subrahmanya" <ksubrahm@xxxxxxxxxx> > To: gluster-devel@xxxxxxxxxxx > Cc: "Joseph Fernandes" <josferna@xxxxxxxxxx>, "Vijaikumar Mallikarjuna" > <vmallika@xxxxxxxxxx>, "Raghavendra Talur" <rtalur@xxxxxxxxxx> > Sent: Wednesday, February 24, 2016 12:07:05 PM > Subject: Proposal of WORM/Retention Translator > > Hi all, > > I'm Karthik Subrahmanya, working as an intern in Red Hat, Bangalore. > > I, along with Joseph Fernandes (Mentor), will be implementing File-Level > WORM-Retention feature for GlusterFS. > > What is WORM-Retention FS? > 1. WORM/Retention FS is a file system that supports immutable(read-only) and > undeletable files. > 2. Each file will have its own worm/retention attribute. Like Retention > Period, Retention Time/Date, WORM/Retention State etc > 3. It stores data in a tamper-proof and secure way and data accessibility > policies. > > What is already implemented in Gluster? > The existing WORM implementation in GlusterFS works at volume level as a > switch. > It makes all the files in the volume read-only if it is switched on, which is > might be desirable or applicable for Data Compliance usage.[1] > > Our idea is to implement a file level WORM, in which it saves the > WORM/Retention attribute for each file in the volume. > > > Please refer [2] for more on design. > > Our approach will be step by step, > > 1. Implement WORM-Retention Semantics in GlusterFS using the WORM Xlator > 2. Integrate WORM-Retention with Bitrot with WORM-Retention Feature for Data > Validation > 3. Help in implementing Control of atime, mtime, ctime [3], as its a > requirement for us > 4. Tiering based on Compliance (Stress Goal) > > We have done a POC on WORM-Retention Semantics [4]. We are working on making > it well baked. > > Vijai (vmallika@xxxxxxxxxx) and Raghavendra Talur (rtalur@xxxxxxxxxx) have > helped us in implementing the POC. > > Your valuable suggestions are most welcome and expecting your support in the > future work! > > Thanks & Regards, > Karthik Subrahmanya > > [1] https://en.wikipedia.org/wiki/Regulatory_compliance > [2] > http://www.gluster.org/community/documentation/index.php/Features/gluster_compliance_archive > [3] > http://nongnu.13855.n7.nabble.com/distributed-files-directories-and-cm-time-updates-td207822.html > [4] http://review.gluster.org/13429 > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
