Orchestrator interfaces / protocol

[davidemalagoli]

Define:

• shared directory name/position
• input data ready for (training)
• exec command (start training, get recommendation)
• receive notification (ended training, ended recommendation)

[robertoturrin]

protocol v0.1

A protocol example has been implemented and tried (raw version based on shell scripts):

• the machine writes a file with the message READY and starts listening to any command by the orchestrator. A command consists of a file with a message inside
• the orchestrator writes a file with the message READ_INPUT, followed by two lines that specifies the path of entities and relations
• the machine reads the input and, if necessary, converts the dataset into the format that is able to process. Therefore it notifies the orchestrator by writing a file with the message OK
• the orchestrator writes a file with the message TRAIN
• the machine trains the algorithm and, once terminated, it writes a file with the message OK
• the orchestrator writes a file with the message RECOMMEND, followed by a line with the name of the output file, and a set of lines, each one indicating the userid to recommend
• the machine recommends the specified users and write the output items into the specified file. At the end, it writes a file with the message OK
• the orchestrator finally writes a file with the command STOP
• the machine stops listening for further commands

[robertoturrin]

see version 1.0: https://drive.google.com/a/moviri.com/folderview?id=0B2qIQUxlCIn9djZyN0R5ODVSNkE&usp=sharing