On 09/05/18 16:10, Max Rees wrote:
I think another thing that needs fleshing out in this area is how
multiple build servers of the same architecture will be handled -
perhaps a build server can post a message so that it can "claim" a
task before the other same-architecture build servers get to it.
My suggestion would be to have the agent daemon be 'smart enough' to know:
- that a build server is available
- that all build servers are busy
- that a build server has become available
If "busy" and "available" are MQTT messages, then I would assume that
this would not be difficult.
In this design, the agent would be the one that chooses which server to
use for an architecture, and send the job directly to the server which
is first available.
There could likely be an operator-maintained order of servers to choose
when all or multiple are available (sorted by CPU core count or so on).
I am not in any way attached to this proposal; better ones are welcome.
A. Wilcox (awilfox)
Project Lead, Adélie Linux