storage tiers

Registered by John Dickinson on 2012-08-07

A cluster can be provisioned with tiers of storage (eg high and low IOPS) for customers to choose. Either objects or entire containers could be selected for a particular tier.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
paul luse on 2015-07-01

Related branches

Sprints

Whiteboard

It would be great if data could be dynamically allocated to tiers based on usage patterns. For example, if the data is infrequently accessed, it would be moved to a slower IOPS tier, while data being accessed often would reside in a faster tier. Age of data could also be a consideration.

P.Luse> So I'd like to look more into this and put some related comments in a blueprint that Clay posted because I think there's some good overlap at least in possible implementation of what his idea is for experimenting with durability policies and what I was thinking in terms of a possible implementation for Tiers

FYI Storage Policies patch set updated (part of EC work) and can serve as foundation for Tiers

J.Dickinson> absolutely, and the actual migration effort should probably be kept outside of Swift's core codebase, or at minimum outside the scope of the current work.

P.Luse> Totally agree, just keeping this item updated with related work for anyone interested in/tracking tier'ing as a feature (whether it be part of the core or not)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.