Push artifacts to the back-end boards
Summary
Once #62 will be implemented, the cmsgemos online software will be able to push the required artifacts to the back-end board. This issue aims a discussing and the implementing this feature in the best way.
Any functional back-end board will require artifacts (described in #62) to run smoothly. In order to ensure run-time compatibility, those artifacts are part of the DAQ client software bundle. This does not solve the problem of the last step deployment.
The last step can be done (to be discussed) through SSH, rsync, nfs,... Ideally, the RPC server on the back-end is successfully restarted automatically before notifying the client.
What is the expected correct behavior?
The users (including the experts) should have to worry about the artifacts installation on the back-end board. Those artifacts can be pushed on-demand or during some specified transitions (during back-end board initialization?) To cope with the various requirement, the functionality will have to be reusable.