This proposal offers a much more ideal way of dealing storage decisions. It would allow for elegant solutions to the perennial problems of managing data that for delivery reasons may need to be stored differently. Especially appealing to me is that video/audio content could be both managed by fedora and stored in a way to allow direct streaming by any of various commercial or open-source streaming servers. Large archive versions of files could be stored to tape while derivatives could be stored to disk, all without losing or needing to replicate the management functionality or have cleaver hacks to implement the storage decision-making process. In order to meet some of our longstanding requirements storage logic needs access to as much context about the data as possible, and this proposal meets that need.
Thanks for putting together this proposal, I hope this issue gets discussed and something like your proposal is implemented. In creating the final form, I think it's important to ensure that rebuilding from data (as could be done from FOXML and datastream files) is still possible, and to ensure that the disaster recovery that is such an asset to fedora is retained. -Mike Durbin -----Original Message----- From: Aaron Birkland [mailto:[email protected]] Sent: Wednesday, January 27, 2010 1:12 AM To: [email protected] Subject: [Fedora-commons-developers] Proposal for a new storage layer in Fedora Hi all, As you may be aware, there is a face-to-face meeting in London where various committers and (other interested parties) will be discussing future directions for Fedora. One topic slated for discussion is that of Fedora's storage architecture. The ideas of multiplexing storage (so that managed content can be sent to different storage devices based on some criteria), hierarchical storage, alternate object representations, etc have been discussed in the past. I would like to propose a few architectural changes to the Fedora core that could make these tasks easier to implement. I made a skeleton of a page on the wiki: http://fedora-commons.org/confluence/x/syTS A draft is currently written up in a pdf doc (which is linked on the wiki page): http://www.fedora-commons.org/confluence/download/attachments/13771955/fedora-highlevel-storage_draft-proposal.pdf The main purpose of the proposal is to spur conversation on the topic.. the proposal may or may not represent an ideal approach, but it seems to represent a logical next step that would remove some of the existing architectural barriers to implementing more sophisticated storage strategies. I decided to put this up quickly so that people can have some time to read it over, ask questions, discuss, think about how to improve it, or propose alternatives. Hopefully, this is a topic that people would like to discuss. -Aaron ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
