[Gluster-devel] WORM/Retention Feature - 24/03/2016

[Karthik Subrahmanya]

Hi all,

This week's status:

-Implemented the lazy-auto-commit feature:
 Auto commit period is the time interval at/after which
 the namespace scan should take place to check for the
 dormant file to do the state transition.

 In lazy auto commit each file will have a start time
 as an xattr, in which we store the create time of the
 file. If a file already exists in a volume before the
 worm feature is enabled, then the start time will
 points to the time when the next fop has come for
 that file.

 Currently the transition takes place only with the
 rename, unlink, and the truncate fops. If a file is
 not wormed yet during the next fop and if the
 file's auto-commit period is expired, it will convert
 the file to worm-retained state. Then it blocks the
 unlink, rename, truncate, and write fops.

 If a file is in worm-retained state and its auto-
 commit period is expired when the next fop comes, then
 it converts the file to worm state. It will then block
 the rename, write, and truncate fops but the unlink
 will succeed.

-Updated the WORM-Retention design-specs document


Plan for next week:

-Testing the program
-Handling the other fops to do the state transition

Current work:

POC: http://review.gluster.org/#/c/13429/
Spec: http://review.gluster.org/13538
Feature page: http://www.gluster.org/community/documentation/index.php/Features/gluster_compliance_archive

Your valuable suggestions, reviews, and wish lists are most welcome

Thanks & Regards,
Karthik Subrahmanya