Changes of Simple Parallel Exec from #6 to #7

Changed lines at line 43
- on http request for executeable: reply with the binary for the right platform
- on http request for new task:  reply with  the next command to execute and all parameters.
- on post: validate result and mark set and collect results
- no more parameter set to process: exit and display statistics.
1.1 Client
- gets via command line: Session ID, command name (path and name of the executeable), md5 checksum of the executeable, server name and port
- register at the server and fetch configuration
- check for the executeable: if not there or the MD5 checksum is wrong: fetch it (for own platform) from the server 
- fetch a task 
- run program
- check return code: if failed -> Post failture otherwise take the results and post them.
- fetch next task.
- die is there is no more task or the server is not responding.
- different settings for termination: delete executeable (if fetched), delete the client program?
 
1 Protocol
1.1 Configuration
- Request: GET \http://master/config?sessionID=SESSIONID
- Fail (due to wrong session id): 403 (Forbidden)
- Successful Reply: List of Key = Value pairs.
{code:none}
DeleteProgram=Yes/No
DeleteClient=Yes/No
Ping=#
{code}
1.1 Ping (HTTP)
- Ping interval is given in seconds. 0 for no ping.
- Purpose of the ping is that the client realises if the server is stopped or finished or even dead.
- Request: GET \http://master/ping?sessionID=SESSIONID&ticket=TICKET
- Fail due to wrong session id: 403 (Forbidden)
- Successful, but ticket expired (task allready done): 205 Reset Content
- Successful (keep on it!): 204 (No Content)
1.1 Binary
- Request: GET \http://master/binary?sessionID=SESSIONID&name=NAME&platform=PLATFORM
- Fail (due to wrong session id, or wrong name): 403 (Forbidden)
- Fail (due to unsupported platform): 415 Unsupported Media Type
- Success: binary file
1.1 Task
- Request: GET \http://master/task?sessionID=SESSIONID
- Fail (due to wrong session id): 403 (Forbidden)
- Fail (because no task left): 503 Service Unavailable
- Success: 
{code:none}
Ticket=#  (unique number (usually 5 digits))
Timeout=# (in seconds)
CommandLine=commandline
[Input]*
File=filename (or "stdin")
--begin content--
real file content here (binary)
--end content--
[Result]+
Name=resultname
File=filename (or "stdout")
{code}
1.1 Task completed
- Successful: POST \http://master/complete?sessionID=SESSIONID&ticket=TICKET
{code:none}
[Result]+
Name=resultname
--begin content--
file content here (binary)
--end content--
{code}
- Failed: GET \http://master/failed?sessionID=SESSIONID&ticket=TICKET
- Reply Fail due to wrong session id: 403 (Forbidden)
- Reply Otherwise:  200 OK
1 Implementation Details
1.1 Configuation and Files
- Cluster file: list of computers, one per line
- Parameter file: csv file, cells seperated with |, parameter names in the headline and every following line contains one parameter set. All lines have to have the same amount of cells like the headline!
- Commandline specification: Command line: a perl syntax string with parameter Variables for the parameters; Input files: Name of the file and parameter name to write in.
- Result specification: A result consists of a list of name and value pairs. Where name specifies the name of the particular output and value decides where the output comes from. For example output="stdout", outputfile="out.txt".
- Validation function: function template that gets the parameter set and the result of the programm and returns success or not
- Collection function: gets the parameters set and the result of the programm and can do whatever with it (usually print it in a file). 
1.1 Error detection
Remote shell command (ssh) termination code:
- 0 => Success: The program has been executed with success!
- otherswise => Failure: Can have the following reasons: connection failed, programm not found or terminated without success.
- on http request for worker executeable: reply with the binary for the right platform
- on http request for new task:  reply with  the next command to execute and all parameters.
- on post: validate result and mark set and collect results
- no more parameter set to process: exit and display statistics.
1.1 Client
- gets via command line: Session ID, command name (path and name of the executeable), md5 checksum of the executeable, server name and port
- register at the server and fetch configuration
- check for the executeable: if not there or the MD5 checksum is wrong: fetch it (for own platform) from the server 
- fetch a task 
- run worker
- check return code: if failed -> Post failture otherwise take the results and post them.
- fetch next task.
- die is there is no more task or the server is not responding.
- different settings for termination: delete executeable (if fetched), delete the client program?
 
1 Protocol
1.1 Configuration
- Request: GET \http://master/config?sessionID=SESSIONID
- Fail (due to wrong session id): 403 (Forbidden)
- Successful Reply: List of Key = Value pairs.
{code:none}
DeleteWorker=Yes/No
DeleteClient=Yes/No
Ping=#
{code}
1.1 Ping (HTTP)
- Ping interval is given in seconds. 0 for no ping.
- Purpose of the ping is that the client realises if the server is stopped or finished or even dead.
- Request: GET \http://master/ping?sessionID=SESSIONID&ticket=TICKET
- Fail due to wrong session id: 403 (Forbidden)
- Successful, but ticket expired (task allready done): 205 Reset Content
- Successful (keep on it!): 204 (No Content)
1.1 Worker
- Request: GET \http://master/worker?sessionID=SESSIONID&name=NAME&platform=PLATFORM
- Fail (due to wrong session id, or wrong name): 403 (Forbidden)
- Fail (due to unsupported platform): 415 Unsupported Media Type
- Success: binary file
1.1 Task
- Request: GET \http://master/task?sessionID=SESSIONID
- Fail (due to wrong session id): 403 (Forbidden)
- Fail (because no task left): 503 Service Unavailable
- Success: 
{code:none}
Ticket=#  (unique number (usually 5 digits))
Timeout=# (in seconds)
CommandLine=commandline
[Input]*
File=filename (or "stdin")
--begin content--
real file content here (binary)
--end content--
[Result]+
Name=resultname
File=filename (or "stdout")
{code}
1.1 Task completed
- Successful: POST \http://master/complete?sessionID=SESSIONID&ticket=TICKET
{code:none}
[Result]+
Name=resultname
--begin content--
file content here (binary)
--end content--
{code}
- Failed: GET \http://master/failed?sessionID=SESSIONID&ticket=TICKET
- Reply Fail due to wrong session id: 403 (Forbidden)
- Reply Otherwise:  200 OK
1 Implementation Details
1.1 Configuation and Files
- Cluster file: list of computers, one per line
- Parameter file: csv file, cells seperated with |, parameter names in the headline and every following line contains one parameter set. All lines have to have the same amount of cells like the headline!
- Specification of worker: Command line: a perl syntax string with parameter Variables for the parameters; Input files: Name of the file and parameter name to write in.
- Result specification: A result consists of a list of name and value pairs. Where name specifies the name of the particular output and value decides where the output comes from. For example output="stdout", outputfile="out.txt".
- Validation function: function template that gets the parameter set and the result of the worker and returns success or not
- Collection function: gets the parameters set and the result of the worker and can do whatever with it (usually print it in a file). 
1.1 Error detection
Remote shell command (ssh) termination code:
- 0 => Success: The worker has been executed with success!
- otherswise => Failure: Can have the following reasons: connection failed, program not found or terminated without success.