<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'>Thanks, Michael. Another followup question:<div><br></div><div>If I have two datacenters, and require two spacewalks (proxy or standalone), what is the best way to keep them both in sync?</div><div>1. Using a 'master' spacewalk in conjunction with a proxy at each site (as this email thread suggests)?</div><div>2. Spin up two separate spacewalks with ISS?</div><div>3. Oracle RAC (also mentioned earlier in this thread)?</div><div><br></div><div>From what I have read, ISS will only take care of syncing software channel data (channels, RPMs, errata). But what about kickstarts and configuration channels? Would those have to be sync'd manually via cobbler replicate? Or is this just not a supported feature at this time.</div><div><br></div><div>Thanks,</div><div>Giovanni</div><div><br><div><div id="SkyDrivePlaceholder"></div>> Date: Mon, 4 Mar 2013 16:22:15 +0100<br>> From: michael.mraka@redhat.com<br>> To: spacewalk-list@redhat.com<br>> Subject: Re: [Spacewalk-list] Clustering Spacewalk.<br>> <br>> Giovanni Torres wrote:<br>> % With regards to configuration channels in this situation with two proxies, do the configuration channels get configured on the Spacewalk server only, and the proxies just route to it? In other words, would I only configure configuration channels in one place in this scenario?<br>> <br>> Yes, everything is configured at Spacewalk server.<br>> <br>> % Thanks,Giovanni<br>> <br>> Regards,<br>> <br>> --<br>> Michael Mráka<br>> Satellite Engineering, Red Hat<br>> <br>> _______________________________________________<br>> Spacewalk-list mailing list<br>> Spacewalk-list@redhat.com<br>> https://www.redhat.com/mailman/listinfo/spacewalk-list<br></div></div> </div></body> </html>