Bug 1262118 - [RFE] Swift Object Expiration support
Summary: [RFE] Swift Object Expiration support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW
Version: 1.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 2.0
Assignee: Yehuda Sadeh
QA Contact: shilpa
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1322504
TreeView+ depends on / blocked
 
Reported: 2015-09-10 20:23 UTC by Neil Levine
Modified: 2019-12-16 04:56 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Swift Object Expiration is now supported Ceph now supports expiration of Swift objects. For details see the http://docs.openstack.org/developer/swift/overview_expiring_objects.html[Expiring Object Support] section of the OpenStack documentation.
Clone Of:
Environment:
Last Closed: 2016-08-23 19:26:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2909141 None None None 2017-02-06 22:53:09 UTC
Red Hat Product Errata RHBA-2016:1755 normal SHIPPED_LIVE Red Hat Ceph Storage 2.0 bug fix and enhancement update 2016-08-23 23:23:52 UTC

Description Neil Levine 2015-09-10 20:23:02 UTC 
Implement Swift object expiration.
Comment 2 Yehuda Sadeh 2015-09-22 18:09:43 UTC 
Do we really want it for 1.3.2?
Comment 3 Neil Levine 2015-09-22 18:50:04 UTC 
Is a backport too difficult or too risky?
Comment 4 Neil Levine 2015-09-23 18:57:26 UTC 
*** Bug 1262117 has been marked as a duplicate of this bug. ***
Comment 11 shilpa 2016-08-02 08:51:23 UTC 
Feature testing is complete. Doc text looks fine. Moving to verified
Comment 13 errata-xmlrpc 2016-08-23 19:26:55 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-2016:1755
Note You need to log in before you can comment on or make changes to this bug.