Difference between revisions of "Distributed Space"
m |
m |
||
| Line 7: | Line 7: | ||
The DHT network overlay can be used to maintain a global shared object tree (a semantic space, or TripleSpace). This layer holds small (kilobyte scale) information concerning the relational aspect of the objects not the content associated with them which could be large binary files etc. Rather than maintain a local object cache, we could expect the DHT to handle this - or should be easily extended to do so. | The DHT network overlay can be used to maintain a global shared object tree (a semantic space, or TripleSpace). This layer holds small (kilobyte scale) information concerning the relational aspect of the objects not the content associated with them which could be large binary files etc. Rather than maintain a local object cache, we could expect the DHT to handle this - or should be easily extended to do so. | ||
| − | == Resource Allocation == | + | == Resource Allocation & Scheduling == |
The storage and communications to content is achieved by the resource allocation layer, which should be a multiplexing solution. Descriptions of resources must include the ability to define the process of completing jobs on a part-by-part basis. | The storage and communications to content is achieved by the resource allocation layer, which should be a multiplexing solution. Descriptions of resources must include the ability to define the process of completing jobs on a part-by-part basis. | ||
| − | Even more preferable to a Hydranode type solution would be a generic resource allocation and scheduling solution. [[Grid]] technology uses this approach to allocate and account for resource. The layer of the grid architecture which handles this allocation is called [[w:Grid middleware]] | + | Even more preferable to a Hydranode type solution would be a generic resource allocation and scheduling solution. [[Grid]] technology uses this approach to allocate and account for resource. The layer of the grid architecture which handles this allocation is called [[w:Grid middleware|Grid middleware]] |
*[[w:Advanced Resource Connector|Advanced Resource Connector]] | *[[w:Advanced Resource Connector|Advanced Resource Connector]] | ||
*[[w:Parallel Virtual Machine|Parallel Virtual Machine]] | *[[w:Parallel Virtual Machine|Parallel Virtual Machine]] | ||
| + | *[[w:O(1) scheduler|O(1) scheduler]] | ||
| + | *[[w:Statistical multiplexing|Statistical multiplexing]] | ||
== Organisation == | == Organisation == | ||
Revision as of 11:00, 14 May 2007
In the project we need a space with the following properties:
- Decentralised and self-organising (like most modern DHT's)
- Protocol-independent content distribution (like Hydranode)
- Event-capable (ie changes "pushed" to viewers, tuple-spaces don't work this way)
DHT
The DHT network overlay can be used to maintain a global shared object tree (a semantic space, or TripleSpace). This layer holds small (kilobyte scale) information concerning the relational aspect of the objects not the content associated with them which could be large binary files etc. Rather than maintain a local object cache, we could expect the DHT to handle this - or should be easily extended to do so.
Resource Allocation & Scheduling
The storage and communications to content is achieved by the resource allocation layer, which should be a multiplexing solution. Descriptions of resources must include the ability to define the process of completing jobs on a part-by-part basis.
Even more preferable to a Hydranode type solution would be a generic resource allocation and scheduling solution. Grid technology uses this approach to allocate and account for resource. The layer of the grid architecture which handles this allocation is called Grid middleware
Organisation
Organisation objects have resource availability and current work which the allocation layer will connect over time. Execution is an event model connecting processes to environmental conditions and recipients groups.
