Index: /trunk/Nebulous-Server/docs/design.txt =================================================================== --- /trunk/Nebulous-Server/docs/design.txt (revision 5049) +++ /trunk/Nebulous-Server/docs/design.txt (revision 5050) @@ -1,30 +1,47 @@ # Copyright (C) 2004-2005 Joshua Hoblitt # -# $Id: design.txt,v 1.3 2005-09-14 00:46:58 jhoblitt Exp $ +# $Id: design.txt,v 1.4 2005-09-14 03:24:45 jhoblitt Exp $ + +Abstract +-- + +Nebulous is a user-space distributed object (file) storage system. It is much +more a database of where objects are stored then a filesystem in the +traditional sense. Nebulous is considered distributed because of it's data +storage model, where objects are stored across a number of storage volumes and +may have redundant copies. While IPC is done in the traditional client/server +model with a single[1] centralized server containing all storage object +meta-data. This system was designed, unlike most distributed filesystems, +specifically so that clients have the option of hosting one or more storage +volumes. Although, if you so choose, clients and storage volumes can reside +on independent hardware. Above all else, Nebulous is designed to make +efficient use of both disk and network bandwidth. + Overview -- -Nebulous is a user-space distributed object (file) storage system. The system -is distributed in the sense of it's data storage model where objects are stored -across a number of storage volumes and may have redundant copies. While IPC -is done in the traditional client/server model with a single[1] centralized -server containing all storage object meta-data. This system was designed, -unlike most distributed filesystems, specifically so that Nebulous clients -could also host one or more storage volumes. Although, there is no requirement -that clients also provide storage space. If you so choose, clients and the -storage volumes can reside on independent hardware. - There are 4 principle components required for a working Nebulous system; -server, client, data transport, and data storage. The Nebulous system only -provides the server and the client software. Data transport[2] and Data -storage are left to 3rd party software packages. As this function is typically -included with most operation system it is unlikely that those specific -technologies can be improved upon. - -A centralized server model was used to allow efficient use of 'like' searches -on storage object names. The current 'best' technique for a distributed -metadata store is with distributed hash tables. Unfortunately, no widely -available DHT implementation allows 'like' searches on key names. +server, client, data transport, and data storage. The Nebulous software +distribution provides only the server and the client software. Data +transport[2] and Data storage are left to 3rd party software packages. As +those functionalities are typically included with most operation system. +Instead, Nebulous build upon and benfits from advances made in those +technologies. + +Server +-- + +The server is responsible for keeping track of storage objects, all instances +of that object, and enforcing locking semantics. Extensive logging and +tracing support is provided for debug and to allow for statics generation and +possible X optimization. + +Nebulous uses a centralized server model. This model was choosen because it +allows efficient X of storage object names. The current +'best' technique for a distributed metadata store is with distributed hash +tables. Unfortunately, no widely available DHT implementation allows efficent +I of key names. + [1] Multiple Nebulous servers should be possible via database replication. Index: /trunk/Nebulous/docs/design.txt =================================================================== --- /trunk/Nebulous/docs/design.txt (revision 5049) +++ /trunk/Nebulous/docs/design.txt (revision 5050) @@ -1,30 +1,47 @@ # Copyright (C) 2004-2005 Joshua Hoblitt # -# $Id: design.txt,v 1.3 2005-09-14 00:46:58 jhoblitt Exp $ +# $Id: design.txt,v 1.4 2005-09-14 03:24:45 jhoblitt Exp $ + +Abstract +-- + +Nebulous is a user-space distributed object (file) storage system. It is much +more a database of where objects are stored then a filesystem in the +traditional sense. Nebulous is considered distributed because of it's data +storage model, where objects are stored across a number of storage volumes and +may have redundant copies. While IPC is done in the traditional client/server +model with a single[1] centralized server containing all storage object +meta-data. This system was designed, unlike most distributed filesystems, +specifically so that clients have the option of hosting one or more storage +volumes. Although, if you so choose, clients and storage volumes can reside +on independent hardware. Above all else, Nebulous is designed to make +efficient use of both disk and network bandwidth. + Overview -- -Nebulous is a user-space distributed object (file) storage system. The system -is distributed in the sense of it's data storage model where objects are stored -across a number of storage volumes and may have redundant copies. While IPC -is done in the traditional client/server model with a single[1] centralized -server containing all storage object meta-data. This system was designed, -unlike most distributed filesystems, specifically so that Nebulous clients -could also host one or more storage volumes. Although, there is no requirement -that clients also provide storage space. If you so choose, clients and the -storage volumes can reside on independent hardware. - There are 4 principle components required for a working Nebulous system; -server, client, data transport, and data storage. The Nebulous system only -provides the server and the client software. Data transport[2] and Data -storage are left to 3rd party software packages. As this function is typically -included with most operation system it is unlikely that those specific -technologies can be improved upon. - -A centralized server model was used to allow efficient use of 'like' searches -on storage object names. The current 'best' technique for a distributed -metadata store is with distributed hash tables. Unfortunately, no widely -available DHT implementation allows 'like' searches on key names. +server, client, data transport, and data storage. The Nebulous software +distribution provides only the server and the client software. Data +transport[2] and Data storage are left to 3rd party software packages. As +those functionalities are typically included with most operation system. +Instead, Nebulous build upon and benfits from advances made in those +technologies. + +Server +-- + +The server is responsible for keeping track of storage objects, all instances +of that object, and enforcing locking semantics. Extensive logging and +tracing support is provided for debug and to allow for statics generation and +possible X optimization. + +Nebulous uses a centralized server model. This model was choosen because it +allows efficient X of storage object names. The current +'best' technique for a distributed metadata store is with distributed hash +tables. Unfortunately, no widely available DHT implementation allows efficent +I of key names. + [1] Multiple Nebulous servers should be possible via database replication. Index: /trunk/Nebulous/lib/Nebulous/Client/QuickStart.pod =================================================================== --- /trunk/Nebulous/lib/Nebulous/Client/QuickStart.pod (revision 5049) +++ /trunk/Nebulous/lib/Nebulous/Client/QuickStart.pod (revision 5050) @@ -3,5 +3,5 @@ =head1 NAME -Nebulous::Server::QuickStart- Nebulous QuickStart Guide +Nebulous::Server::QuickStart - Nebulous QuickStart Guide =head1 Perl CLIENT @@ -77,5 +77,5 @@ PKG_CHECK_MODULES([NEBCLIENT], [nebclient >= 0.0.1]) -This Will setup the variables C and C for +This will setup the variables C and C for you and C them.