The Idea of Master and Slave within SysCP-ng is pretty simple. You have one Server which will act as Master and various others, ths Slaves. The Master will notify his slaves if there is a change in configuration, so that the slaves will update.
Master
The Master will be the server which has the SysCP-ng Panel installed on it. All Configuration will be stored here in a DatabaseBackend?.
MORE?!
Slaves
The slaves actually will host the services, like mail, DNS, Webserver etc. pp.
Updating the Slaves
There are currently two possibilyties I can think of how the slaves can be notified that there are updates waiting on the Master.
- The Slaves periodicly check if there are updates available on their own
- The Master contacts the slaves directly after he recieved the new settings and passes them on to right slave(s)
Anyway these connections must be secured. They do not nessesarily must be held open at all time.