Make tansiv provide the socket address as an argument when deploying tansiv clients
The socket address of the tansiv
coordinator is currently hardcoded in tansiv but is taken as a parameter by tansiv-client
(see the implementation and usage in Qemu as well as in sample programs). We should keep this address as a parameter to anticipate evolutions with clients deployed in remote machines and communicating with TCP.
To make the current code more consistent, we should let tansiv
provide its clients with the socket address as a parameter when deploying them.