Bug 1475016

Summary: RFE: S3 object expiration support
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Uday Boppana <uboppana>
Component: RGW-MultisiteAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: Persona non grata <nobody+410372>
Severity: high Docs Contact: Bara Ancincova <bancinco>
Priority: high    
Version: 3.0CC: anharris, ceph-eng-bugs, ceph-qe-bugs, hnallurv, kdreyer, mbenjamin
Target Milestone: rcKeywords: FutureFeature
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.1.4-1.el7cp Ubuntu: ceph_12.1.4-2redhat1xenial Doc Type: Enhancement
Doc Text:
.S3 object expiration is now supported The Ceph Object Gateway now supports the Amazon Simple Storage Service (S3) object expiration. For details see the link:https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/developer_guide/#features-support[Object Gateway S3 Application Programming Interface (API)] chapter and the link:https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/developer_guide/#s3-api-bucket-lifecycle[Bucket Lifecycle] section in the Developer Guide for Red{nbsp}Hat Ceph Storage 3.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:38:03 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: 1494421    

Description Uday Boppana 2017-07-25 20:49:03 UTC
Support for S3 object expiration. 

Should be compatible with AWS S3: https://aws.amazon.com/blogs/aws/amazon-s3-object-expiration/

Comment 8 errata-xmlrpc 2017-12-05 23:38:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3387