tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Add section on node role archetypes and deployment experiences. 

[Imported from Trac: page UseCases, version 10]
nejucomo 2007-11-05 08:30:43 +00:00
parent ec481a658f
commit 5f5c0f45a7
1 changed files with 34 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

35
UseCases.md

@ -1,6 +1,8 @@
# Network Configurations
There are several ways that people might want to use Tahoe. We're not necessarily committed to satisfying all of these use cases -- these are just possibilities.
Use Cases
As these network configurations develop, the *node roles* section develops in complement.
| | | | | | |
|---|---|---|---|---|---|
@ -20,4 +22,35 @@ Use Cases
* *global grid*: A large, diverse ecosystem of people and organizations who want a storage grid with extremely high reliability and availability.
# Node Roles
Network configurations can usually be thought of in terms of a topology connecting particular *node roles*. These roles often fulfill the same abstraction across network configurations. By allowing specialized role configurations, a plethora of custom network configurations can be deployed without modifying the code.
Here are some archetypal roles:
* The *Available Migrator* consumes storage from a changing address.
* **Migration Pattern Availability** - Availability is high, but address changes are frequent.
* Examples: Laptops, mobile devices, poor DHCP configurations.
* Should this role supply storage? If so, how does it affect average file availability? -reliability?
* The *Ephemeral Consumer* consumes storage, but lacks availability.
* **Poor availability** - Availability is low, such as a node that is only up when consuming storage service.
* Examples: Backup service customer.
* Hints:
* Set *size limit* config option to 0. (Is this a kludge currently? -Nejucomo)
* A *Grid Storage Servant* provides storage but does not consume it.
* **High Availability** - An individual file's availability is largely dependent on average storage availability.
* **Remote Control** - Typically a provider configures many nodes through a centralized manner for convenience.
* **Non Consumer** - Specialized storage providers do not consume storage services.
* A *Grid Manager* does not provide storage services but controls storage servents.
# Deployment
## The Test Grid
... Put your experience with particular configurations here ...