Feature Community
Subject Evangelist: TBD
Knowledge Gardener: TBD
Member List:
Dan Davis
Support for Hierarchical Storage
...
Also known as tiered storage, the driving rationale for using hierarchical storage is the notion that costs can be reduced by storing all or part of collection of files (bitstreams) on lower performing, less expensive storage technologies while keeping a copy of some part of the collection on a high performing, more expensive storage technology for immediate use. The hierarchical storage system implements some policy for determining on what tier files are stored to meet system goals. In real world implementations, many other requirements needs may need to be considered since hierarchical storage may can be used to help with other system needs requirements such as backup, replication, high availability and disaster recovery. However, it is cost that underlies any decision to deploy hierarchical storage.
The Fedora architecture presents some unique problems and opportunities in supporting hierarchical storage. Even though storage cost is the driving reason for using hierarchical storage, it can provide a solution for other system requirements. We hope in this forum can list those requirements to inform the design for a hierarchical storage integration which fits well as part of the overall Fedora architecture. In addition to the system requirements listed above, the design may need to consider large datastreams, partial reads, updates/versioning, and other features already listed in the JIRA tracker.