Since version 0.9.3 of GêBR, flow execution is carried out by GêBR daemon. In that sense, GêBR interface is responsible for managing projects and lines as well as for assembling processing flows. It does not run the flow, but just submit it to some server, which will actually execute it and report the results. This dissociation allows that many servers could be used to run flows simultaneously, remote submition, later recovery of flow status, among many other advantages.

The machine running GêBR interface is denoted as client and the one running the daemon is denoted as server. The list of servers is configured in the GêBR interface. In case of an empty list (for example, when starting GêBR for the first time), the machine where GêBR is running is automatically added (local server). To be able to add remote servers, the user has to have access to those hosts through ssh connection, with public key authentication. In case the host does not allow such authentication method contact the system admin. That is not a concern if you just want to run flows locally.

Since remote running is supported from 0.9.3 (the current release at this moment), we expected to improve this feature, turning the setup process easier.

As usual, we expect feedback.

Comments Off on Client/Server architeture since version 0.9.3
Trackback

no comment until now

Sorry, comments closed.