ISPConfig installation into multiple OpenVZ containers

[Justin Albstmeijer]

sounds scary,,
Any idea what could go wrong with the approach you propose? besides that fact that these slaves will contain unnecessary data from the master.
I can imagine some queries could figure out which data you actually need to get to the slave, starting with server_id en tables related.

- will the master in the at all time contain all data (users/aliases/sites) for all slaves?
- will there be somekind of check if master and slave are inconsistant?

[till]

Any idea what could go wrong with the approach you propose?

will the master in the at all time contain all data (users/aliases/sites) for all slaves?

Yes, at the master runs the interface and the interface must be able to show all data. the master itself is not able to connect to the slave databases. The replication works the other way, the slaves are connection to the master and replicate data if there are new records. this has the benefit that you can shutdown a slave for maintenance and no data gets lost when someone edits data on the master server in the meantime.

[QUOTE]- will there be somekind of check if master and slave are inconsistant?/QUOTE]

There is no such script available yet. We might offer that in a later release. But as long as you use a complete copy to set this up, there should be no such problem and later the slave syncs itself with the master so even if the slave is offline for some days it will sync back as soon as it gets online again.