Wiki code for HoneyComb Fixed Content Storage

Hide Line numbers
1: = SPOTLIGHT
2: 
3: [[The ST5800 Storage Plugin for Fedora Commons>>attach:Project honeycomb.WebHome@ST5800FedoraPlugin.zip]] allows for the use of the Sun StorageTek 5800 as the underlying back end storage for the Fedora Commons Open Source Repository.
4: 
5: [[StorageTek 5800 1.1.1 Open Edition Now Available>>http://mediacast.sun.com/users/DavidSobeck/media/ST5800-OpenEdition-1.1-96.zip]] (source code, licensed under the [[BSD License>>Project honeycomb.LICENSE]]) for download. The [[ST5800 1.1.1 SDK>>http://mediacast.sun.com/users/DavidSobeck/media/StorageTek5800_SDK_1_1_96.zip]] (with pre-compiled binaries) is also available.
6: 
7:  If you need the older SDK, the [[ST5800 1.1 SDK>>attach:Project honeycomb.files@StorageTek5800SDK1184.zip]] is available for download too.
8: 
9: = OVERVIEW
10: 
11: The Honeycomb project will store and manage large amounts of fixed content - data that never changes over the course of its life (YouTube videos, x-rays, digital books, etc.). Recent studies have shown that 80% of the data that’s created today will not be modified during its lifetime. And the amount of fixed content is predicted to accelerate growing at a 90% increase through 2010 while mutable (updated) data will grow at a 60% increase (Hal Varian, UC Berkeley).
12: 
13: This project proposes to manage this explosion of data by providing an object-oriented storage system with traditional Java and C interfaces later expanded by a "StorageBean" Java interface. Large data-repository applications access the fixed content through these interfaces which are designed to manage data collections that can total up to 100 million objects or petabytes of storage.
14: 
15: = Goals of the project
16: 
17: The goal of this OpenSolaris project is to provide client and server implementations for the Honeycomb fixed content system. Although there are some existing Honeycomb C and Java [[APIs>>Project honeycomb.api]], we anticipate that OpenSolaris and other open source communities will help shape and define these APIs. We also want to encourage OpenSolaris members to contribute their ideas and code to this project. You can join the conversation over on the [[OpenSolaris storage discussion list>>http://www.opensolaris.org/jive/forum.jspa?forumID=94]].
18: 
19: Another goal of this project is to add the standard [[XAM>>http://www.snia.org/xam]] fixed content interface to both HoneyComb and Solaris itself.
20: 
21: = Related open source communities
22: 
23: There are a number of open source large data-repository applications used by health care, scientific, and educational communities that need a fixed content storage system. These open source communities include:
24: 
25: === [[Fedora Commons>>http://www.fedora-commons.org/]]
26: 
27: Fedora open source software gives organizations a flexible service-oriented architecture for managing and delivering their digital content. At its core is a powerful digital object model that supports multiple views of each digital object and the relationships among digital objects. Digital objects can encapsulate locally-managed content or make reference to remote content. Dynamic views are possible by associating web services with objects. Digital objects exist within a repository architecture that supports a variety of management functions. All functions of Fedora, both at the object and repository level, are exposed as web services. These functions can be protected with fine-grained access control policies. Some examples of applications that are built upon Fedora include library collections management, multimedia authoring systems, archival repositories, institutional repositories, and digital libraries for education.
28: 
29: === [[Dspace.org>>http://dspace.org/index.html]]
30: 
31: The DSpace digital repository system captures, stores, indexes, preserves, and distributes digital research material. Research institutions use DSpace as an institutional repository, a learning object repository, for records management, and more.
32: 
33: === [[EPrints for Digital Repositories>>http://www.eprints.org/]]
34: 
35:  Open source [[EPrints software>>http://www.eprints.org/software/]] provides a Web-based Institutional Repository and is established as the [[easiest and fastest>>http://www.eprints.org/news/features/worlds_best_practice.php]] way to set up repositories of open access research literature, scientific data, theses, reports and multimedia. We are also creating the environment in which [[Open Access>>http://www.eprints.org/openaccess/]] will become the norm for distributing research.
36: 
37: = Storage standard efforts
38: 
39: There is a storage industry standards effort to create a common access and management interface for fixed-content systems.
40: 
41: === [[Storage Networking Industry Association XAM Initiative>>http://www.snia.org/xam/home]]
42: 
43: The XAM (eXtensible Access Method) Interface specification defines a standard access method (API) between "Consumers" (application and management software) and "Providers" (storage systems) to manage fixed content reference information storage services. XAM includes metadata definitions to accompany data to achieve application interoperability, storage transparency, and automation for ILM-based practices, long term records retention, and information security. XAM will be expanded over time to include other data types as well as support additional implementations based on the XAM API to XAM conformant storage systems.
44: 
45: = [[More about the proposed API approach...>>Project honeycomb.api]]
OpenSolaris

Top Menu

Wiki code for HoneyComb Fixed Content Storage

Search

Collectives

Community Group

Project

User Group

Subsites

Project honeycomb Pages
