| 25 | 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. |
| 26 | |
| 27 | Here are some archetypal roles: |
| 28 | |
| 29 | * The ''Available Migrator'' consumes storage from a changing address. |
| 30 | * '''Migration Pattern Availability''' - Availability is high, but address changes are frequent. |
| 31 | * Examples: Laptops, mobile devices, poor DHCP configurations. |
| 32 | * Should this role supply storage? If so, how does it affect average file availability? -reliability? |
| 33 | |
| 34 | * The ''Ephemeral Consumer'' consumes storage, but lacks availability. |
| 35 | * '''Poor availability''' - Availability is low, such as a node that is only up when consuming storage service. |
| 36 | * Examples: Backup service customer. |
| 37 | * Hints: |
| 38 | * Set ''size limit'' config option to 0. (Is this a kludge currently? -Nejucomo) |
| 39 | |
| 40 | * A ''Grid Storage Servant'' provides storage but does not consume it. |
| 41 | * '''High Availability''' - An individual file's availability is largely dependent on average storage availability. |
| 42 | * '''Remote Control''' - Typically a provider configures many nodes through a centralized manner for convenience. |
| 43 | * '''Non Consumer''' - Specialized storage providers do not consume storage services. |
| 44 | |
| 45 | * A ''Grid Manager'' does not provide storage services but controls storage servents. |
| 46 | |
| 47 | |
| 48 | = Deployment = |
| 49 | |
| 50 | == The Test Grid == |
| 51 | |
| 52 | ... Put your experience with particular configurations here ... |
| 53 | |
| 54 | |