#228 evaluate communication methods between task initiator and executor
Closed: Fixed None Opened 9 years ago by tflink.

In the PoC, paramiko was used to communicate between the task initiator and task executor. The problem with that implementation is that return codes are not used. There may be [[http://stackoverflow.com/questions/3562403/how-can-you-get-the-ssh-return-code-using-paramiko|a way to get the return code using paramiko]] but either way, we need a better way to facilitate this communication.

Another thought was to use something like ansible to handle the commands, since a lot of the error handling is already done there. Not sure that's a great idea but it may be another option.

Evaluate the communication methods available (ssh preferred but not really required)


At this point, using ansible seems like overkill to me, slowing down the execution. Using paramiko seems like better option to use here. I checked and paramiko offers getting the return code of commands execution. I have written an initial implementation of paramiko wrapper that we might use in #415.

We'll go with paramiko, at least for now.

Login to comment on this ticket.

Metadata