Difference between revisions of "ToPoS"

From BioAssist
Jump to: navigation, search
(Future developments)
Line 1: Line 1:
 
The '''Token Pool Server (ToPoS)''' is a ReST webservice that supports distribution of large computational tasks on distributed systems, such as [[compute cluster|clusters]], [[cloud computing|compute clouds]], the [[Grid]] or processes on a [[super computer]].
 
The '''Token Pool Server (ToPoS)''' is a ReST webservice that supports distribution of large computational tasks on distributed systems, such as [[compute cluster|clusters]], [[cloud computing|compute clouds]], the [[Grid]] or processes on a [[super computer]].
  
== ToPoS III ==
+
== ToPoS IV ==
The current version of ToPoS is 3.0.
+
The current version of ToPoS is 1.4.0.
  
 
== Links ==
 
== Links ==
* [http://topos.grid.sara.nl/3/ ToPoS III]
+
* [http://purl.org/sara/topos/4 ToPoS IV]
* [http://topos.grid.sara.nl/3/topos3_reference_manual.pdf ToPoS III Reference Manual]
+
* [http://purl.org/sara/topos/4/reference_manual ToPoS IV Reference Manual]
  
 
== Older versions ==
 
== Older versions ==
Line 16: Line 16:
  
 
The performance of ToPoS 2 was not good enough to support 100k+ of tokens and the file-token model did not work out as expected. The problem there is that with the token files there are two places to put information: both in the file name and in the file content. To solve these problems a new version will be developed.
 
The performance of ToPoS 2 was not good enough to support 100k+ of tokens and the file-token model did not work out as expected. The problem there is that with the token files there are two places to put information: both in the file name and in the file content. To solve these problems a new version will be developed.
 +
 +
=== ToPoS 3 ===
 +
Still in production as of writing. Will be discontinued in December 2009.
  
 
== Future developments ==
 
== Future developments ==
* Zou het handig zijn om een counter in ToPoS te implementeren om bij te houden hoe vaak een token is opgevraagd? We zouden dat eventueel kunnen gebruiken voor debugging zodat je kunt zien dat de nodes een bepaalde job gewoon niet aankunnen. --[[User:Jjbot|Jan Bot]] 16:38, 3 February 2009 (CET)
+
Currently, there are no open requests.
* Uniformeren van informatie per token/lock.
+
* Meer informatie over tokens in pool-directory listing: aantal uitgiftes, creation-timestamp, ...
+
  
 
=== Done ===
 
=== Done ===
Line 27: Line 28:
 
* Opleuken van de interface dmv stylesheets.
 
* Opleuken van de interface dmv stylesheets.
 
* Uniforme directory-listings.
 
* Uniforme directory-listings.
 +
* Zou het handig zijn om een counter in ToPoS te implementeren om bij te houden hoe vaak een token is opgevraagd? We zouden dat eventueel kunnen gebruiken voor debugging zodat je kunt zien dat de nodes een bepaalde job gewoon niet aankunnen. --[[User:Jjbot|Jan Bot]] 16:38, 3 February 2009 (CET)
 +
* Uniformeren van informatie per token/lock.
 +
* Meer informatie over tokens in pool-directory listing: aantal uitgiftes, creation-timestamp, ...
  
 
== Usage ==
 
== Usage ==

Revision as of 17:36, 23 November 2009

The Token Pool Server (ToPoS) is a ReST webservice that supports distribution of large computational tasks on distributed systems, such as clusters, compute clouds, the Grid or processes on a super computer.

ToPoS IV

The current version of ToPoS is 1.4.0.

Links

Older versions

ToPoS 1

The first version of ToPoS provided a simple counter which could be used to specify which job to run. The functionality provided was not enough for more sophisticated jobs which required multiple parameters to be set.

ToPoS 2

The second version of ToPoS was build as a virtual webdav server, which didn't actually hold files but provided a webdav interface to a database. Job tokens could be accessed as files, holding the parameters of a job as the file content. One of the strong points of ToPoS 2 was the ability to upload output and delete a token in one atomic operation. This ensures that no token is deleted unless the output is uploaded.

The performance of ToPoS 2 was not good enough to support 100k+ of tokens and the file-token model did not work out as expected. The problem there is that with the token files there are two places to put information: both in the file name and in the file content. To solve these problems a new version will be developed.

ToPoS 3

Still in production as of writing. Will be discontinued in December 2009.

Future developments

Currently, there are no open requests.

Done

  • Currently, the "Web interface" of ToPoS lacks "Go up one directory" navigation buttons. These should be added. --Jan Bot 23:03, 21 January 2009 (CET)
  • The $BASE/<realm>/pools/<pool>/ URL doesn't show the number of tokens in the tokens/ subdirectory, but the interface suggests that this information should be there. --Jan Bot 12:52, 22 January 2009 (CET)
  • Opleuken van de interface dmv stylesheets.
  • Uniforme directory-listings.
  • Zou het handig zijn om een counter in ToPoS te implementeren om bij te houden hoe vaak een token is opgevraagd? We zouden dat eventueel kunnen gebruiken voor debugging zodat je kunt zien dat de nodes een bepaalde job gewoon niet aankunnen. --Jan Bot 16:38, 3 February 2009 (CET)
  • Uniformeren van informatie per token/lock.
  • Meer informatie over tokens in pool-directory listing: aantal uitgiftes, creation-timestamp, ...

Usage

A number of projects have used ToPoS to circumvent some of the problems related to the EGEE grid middleware.

KCSmart

ToPoS was used in combination with KCSmart to analyze copy number variation.