Take a look at the doc i wrote on the cobbler wiki. We have been using that for about 4 months and it works pretty good. One master and 3 slaves.
-- Alastair Munro -----Original Message----- From: "Tomasz Leśniewski" <[email protected]> To: [email protected] Sent: Thu, 23 Oct 2014 19:39 Subject: [cobbler] Replication architecture/patterns Hi. I'm trying to set a cobbler cluster (two nodes) and i have a question about replication architecture. I've read docs and i know that replication is initiated by "slave" node and could be fired over trigger from "master". In my environment i have to do replication as fast as it is possible, so i don't want to use cron, because in worst case i'll have had one minute lag. So far i've tried: 1.on master, script triggered after sync (post-sync) that perform sync on slave (over xmlrpc) 2. on slave, script that before sync (pre-sync, fired by sync from master) invoking replication from master And it doesn't work. Replication process is done without errors, but any changes from master are not visible until cobbler restart. Maybe it's because i'm trying to invoke replication from inside of a sync trigger? Second solution works fine, but i'm not sure about it: 1. On master, script triggered after sync that "curl" script (python over wsgi on apache) on slave 2. script on slave invoke "cobbler replicate" over "system" function Is there any docs with patterns how replication should be done? Official manuals are very pure in this area. -- Pozdrawiam/Best regards Tomasz Leśniewski _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
