[Gluster-devel] WORM/Retention Feature - 26/02/2016

[Karthik Subrahmanya]

Hi all,

The current status of the project is:

-It works as a file level WORM
-Handles the setattr call if all the write bits are removed
-Sets an xattr storing the WORM/Retention state along with the retention period
-atime of the file will point to the time till which the file is retained
-When a write/unlink/rename/truncate request comes for a WORM/Retained file,
 it returns EROFS error
-Whenever a fop request comes for a file, it will do a lookup
-Lookup will do the state transition if the retention period is expired
-It will reset the state from WORM/Retained to WORM
-The atime of the file will also revert back to the actual atime
-The file will still be read-only and blocks the write, truncate, and the rename requests
-The unlink call will succeed for a WORM file
-You can transition back to the WORM/Retained state by again doing setattr


Plans for next week:

-As Niels<ndevos at redhat.com> suggestion, preparing a specs document
-Fixing the bugs in the program
-Working on handling the ctime change

You can find the feature page at:
http://www.gluster.org/community/documentation/index.php/Features/gluster_compliance_archive
Patch: http://review.gluster.org/#/c/13429/

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

Regards,
Karthik Subrahmanya