On 07/29/2009 04:36 PM, James Cammarata wrote: > So, we're deploying Cobbler here at work (finally!) and I'm looking to > setup replication between our data centers. I'd like to do master-master > replication, though the wiki says this is not a recommended setup. I know > some work had been done on this, but I'm not sure if that's in 1.6 or > upstream, so I was looking for some feedback on the best way to set this > up. > > Second, as far as firewalls go, is port 80 the only port that needs to be > opened up or is anything done over the XMLRPC port? > > Finally, I see there is an option to sync kickstarts and import trees, but > I don't see anything specifically mentioning snippets or anything else > under /var/lib/cobbler being synced. Does --full-data-sync cover those? > > Thanks, > > James C. > >
FWIW, one of the things I want to be doing (on devel) in the next few weeks is making replication work more intelligently, understanding both mtimes and UIDs. If we do this, then master-master would be sane. Right now, it's a bit of a "shoot-foot" scenario as it doesn't have the logic to know which one wins, so if you do that and don't edit consistently at both places and sync unpredictably, unpredictable results occur. With synchronized clocks and mtimes though, all should be (mostly) well for replicating near continuously (i.e. on heavy crontab -- I don't think I want XMLRPC communications firing off other XMLRPC communications so that it must be pushed based, I'd rather have the users decide -- thoughts welcome of course though). That is my goal. (While I don't plan to backport this to 1.6.6 and support it, you could probably do so on your own if you liked.) --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
