Bug 1421842

Summary:	RFE: Support transitions as part of bucket lifecycle
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Kyle Bader <kbader>
Component:	RGW	Assignee:	Yehuda Sadeh <yehuda>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:	Erin Donnelly <edonnell>
Priority:	medium
Version:	2.2	CC:	anharris, cbodley, ceph-eng-bugs, ceph-qe-bugs, hnallurv, kbader, kdreyer, mbenjamin, sweil, tserlin
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-14.2.0-142.g2f9c072.el8cp	Doc Type:	Enhancement
Doc Text:	.Addition of storage classes and lifecycle transitions to the Ceph Object Gateway The Ceph Object Gateway now provides support for storage classes, an S3 compatible representation of the Ceph Object Gateway's underlying placement targets, and for lifecycle transitions, a mechanism to migrate objects between classes. Storage classes and lifecycle transitions provide a higher level of control over data placement for the applications that need it. They have many potential uses, including performance tuning for specific workloads, as well as automatic migration of inactive data to cold storage.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-31 12:44:52 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:	1473188, 1730176

Description Kyle Bader 2017-02-13 20:14:49 UTC

Bucket lifecycle includes both expiration and transition. Amazon documentation for the feature is here:

https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-transition-general-considerations.html
https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html

Use case:

Two different storage classes, say HDD and SSD, mapped to distinct CRUSH branches. Bucket lifecycle would transition objects from SSD to HDD after $n days. Instead of distinct CRUSH branches, the pools could be configured to use replication vs erasure coding, etc.

Filter Elements and NoncurrentVersionTransition should be supported.

Comment 2 Kyle Bader 2017-02-13 20:36:50 UTC

Transitions can be configure per object version as well:

https://docs.aws.amazon.com/AmazonS3/latest/dev/transitioning-object-versions.html

Comment 10 Giridhar Ramaraju 2019-08-05 13:11:46 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 11 Giridhar Ramaraju 2019-08-05 13:12:41 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 18 errata-xmlrpc 2020-01-31 12:44:52 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-2020:0312

Comment 19 Red Hat Bugzilla 2023-09-14 03:53:34 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days