...
The Shinken Enterprise architecture is a high availability one. Before looking at how this works, let's take a look at how the load balancing works if it's now already done.
Nobody is perfect. A server can crash, an application too. That is why administrators have spares: they can take configurations of failing elements and reassign them.
For the moment the only daemon that does not have a spare is the Arbiter, but this will be added in the future. The Arbiter regularly checks if everyone is available. If a scheduler or another satellite is dead, it the Arbiter sends its conf to a spare node, defined by the administrator.
- All satellites are informed by this change so they can get their jobs tasks from the new element and do not try to reach the dead one.
- If a node was lost due to a network interruption and it comes back up, the Arbiter will notice and ask the old system to drop its configuration.
...
For each command, Shinken Enterprise knows if it is global or not:
- If global, it just sends orders to all schedulers.
- For specific ones instead it searches which scheduler manages the element referred by the command (host/check) and sends the order to this scheduler.
...