Time triggered storage policy transitions

Registered by Paul T Burke on 2014-10-02

With the introduction of Erasure Coding, it would be very beneficial to have an object move from a replica based storage policy to an erasure coded storage policy in an automated way where the trigger is a time component. In this context, an object can be persisted with a policy of 3 replicas and after some duration of time (when the content becomes cold) it would transition from the 3 replica footprint on the storage cluster to one EC copy.

Time triggered policy transitions have many applications, however from a cluster storage utilization perspective being able to transition between replica and EC based storage policies after a designated time duration is very powerful.

A natural evolution of being able to transition through storage policies would then be to trigger based on system or user defined meta data.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Paul T Burke
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.