Bug 1259326

Summary: [RFE] Enable WORM (Write Once Read Many) support in RHCS
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vimal Kumar <vikumar>
Component: RADOSAssignee: Josh Durgin <jdurgin>
Status: CLOSED DEFERRED QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.3.0CC: asriram, ceph-eng-bugs, dzafman, ealcaniz, hgurav, jdurgin, jfenal, kchai, mhackett, nlevine, vumrao
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 4.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-11 16:11:23 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:
Bug Depends On:    
Bug Blocks: 1258382    

Comment 3 Edu Alcaniz 2016-09-16 06:45:09 UTC
Hi, could you update the status of the BZ please

Comment 4 Ian Colle 2016-09-16 07:05:58 UTC
Sam,

It looks like this was started upstream with https://github.com/ceph/ceph/pull/3409/files. What additional work do we need here?

Comment 6 Edu Alcaniz 2016-10-25 06:10:05 UTC
morning, could we have an update about this RFE?

Comment 7 Samuel Just 2016-10-26 16:39:58 UTC
I'm not sure that that PR addresses this bz at all.  All that PR does is make it harder to accidentally delete or mess with a whole pool.  It sounds like this user wants per-rgw-object (for example) control over deletion and modification, and for that to propagate down to the rados level.  We'd need better definition on exactly what operations the user wants to disallow.  Presumably the user would want to map some rgw level authenticated users as capable of tagging and untagging the objects.  Those users would probably need to map onto rados level users and be enforced there.  It would be pretty weird to try to enforce this at the rados level since rgw object modification doesn't look like a rados level object modification at all -- it's a bucket update, an object creation, and an object removal.  By the time the "object removal" happens at the rados level, the rgw level object has already been logically updated at the rgw level, so disallowing that wouldn't even really do the trick.

Comment 17 Josh Durgin 2019-02-11 16:11:23 UTC
No plans for this in the short term.