I’m creating a server management interface for a few of my servers (which host virtual servers) and I wanted to know the best way to implement a master-slave configuration for said interface.
The master server should connect to all the slave servers in order to retrieve information (provide a high level overview) and send them commands (keeps management centralized). However, the master server itself may also have virtual servers on it, which is why I was planning to deploy the same application across all the physical nodes and figure out whether the node is a master or a slave.
//Side Note: almost seems like recursion in a way haha
A few ideas I had in mind:
- Separate database schemas for a master and a slave, the app checks the schema to determine the server type.
- A field in the server listing table that designates a server in the table as a master or slave
I came up with a simple solution to my problem. I just added a SLAVE file to the installation of a slave, and the program checks to see if that file is there. If it is, it designates that server as a slave…..totally over thought this…