Well in that case I still would like to avoid slony if possible I would prefer using the native postgresql master slave replication with pgpool but I would need dig into the sql queries a bit to figure out how I would want to configure the load ballancing also I'm not sure I need to double check but I think there is a way in potstgresql 9 to do more specific targeting of the replication On Jun 29, 2012 11:52 AM, "Musayev, Ilya" <[email protected]> wrote:
> Paul, > > I'm going to disappoint you a bit here, satellite-sync does not sync > clients/systems. > > Man page only mentions: > Channels > Rpms > Packages > Errata > Kickstart > > > > Hence I figured I may as well setup slony with rsync or extend the satsync > library to include systems - I'm under assumption it was left out on > purpose. > > Regards > ilya > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Paul Robert Marino > Sent: Thursday, June 28, 2012 2:56 PM > To: [email protected] > Subject: Re: [Spacewalk-list] Replicate spacewalk core to another data > center for HA > > well I have a different plan which I'm going to test in the next week or so > > As far as i know satellite-sync should work between instances of spacewalk > so if i combine that with a squid 3 revers proxy (possibly with an ssl bump > configured ) or an LVS based load balancer and finally add in a few bind 9 > tricks to do location based responses. I think I should be able to do this > using stock tools without too much difficulty. > > Ill let you know how it goes > > > > > On Thu, Jun 28, 2012 at 12:07 PM, Musayev, Ilya <[email protected]> > wrote: > > I'm looking for a way to replicate master spacewalk server from one > > IDC to another - asynchronously. > > > > > > > > My setup consists of RHEL5 and Spacewalk 1.7 with CNAME pointing to > > spacewalk.domain.com - which in turn points to host in IDC1. > > > > > > > > I was thinking of using "slony" to replicate postgres 8.4 and rsync > > the content of /vat/satellite/ to another server periodically. The > > standby spacewalk 1.7 instance in second IDC wont have its services > > running until I need to fail over. > > > > > > > > When I'm ready to fail over, I break the replication in "slony", > > change the cname in DNS and start the spacewalk services on standby > > host, stop spacewalk services on active host. > > > > > > > > Are there any other - less complex methods that you know off. I looked > > into spacewalk replication script, but it only covers channel > > replications and leaves the clients out. > > > > > > > > As always, any suggestion and help is appreciated, > > > > > > > > Thanks > > > > ilya > > > > > > _______________________________________________ > > Spacewalk-list mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/spacewalk-list > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
