Re: [Spacewalk-list] Spacewalk packages in Debian
Dne 27.6.2012 21:44, Miroslav Suchy napsal(a): I will make it short: http://packages.debian.org/search?suite=unstablesection=allarch=anysearchon=nameskeywords=rhn Enjoy. Mirek Mirku, Sounds good. We are going to test. David Hrbáč ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] adding multiple base channels to a system
You'll need to make the EPEL and Space walk channels child channels in both of the CentOS 6 and 6.2 channels. Yes, its a pain. No, a child can only have a single parent. CC On Jun 28, 2012 8:53 AM, Gregory Machin g...@linuxpro.co.za wrote: Hi. I have setup a dedicated channel for the CentOS repositories and another channel for EPEL . Parent Channel Button CentOS 6.0 Base - x86_64 Child Channel CentOS 6.0 CentOSPlus - x86_64 Child Channel CentOS 6.0 Update - x86_64 Parent Channel Button CentOS 6.2 Base - x86_64 Child Channel CentOS 6.2 CentOSPlus - x86_64 Child Channel CentOS 6.2 Update - x86_64 Parent Channel Button EPEL 6 Parent Channel Button Spacewalk Client - x64 Parent Channel Button Spacewalk Server - x64 The problem is the system can only belong to both the Parent Channel and the EPEL Channel at the same time. I don't want to duplicate EPEL channel the data for both the CentOS channels otherwise this I a waist of space etc. How can I achieve this have I missed a configuration some where ? Thanks G ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Status of Solaris support
Hello, Did you have time to review the patch? Now that I got patch working, I wanted to try patch_cluster and ZipFile class is complaining! # solaris2mpm --tempdir=/data/solaris/tmp/ 10_Recommended.zip Opening archive, this may take a while Bad magic number for central directory Error creating mpm for /data/solaris/10_Recommended.zip: zipfile.BadZipfile instance at 0x2ad1050c5e18 The Bad magic number for central directory appears during the creation of ZipFile object (before my code modification. The zip file is correct as unzip command is uncompressing it without any problem. I'm starting to wonder: is using ZipFile class really better thant old code, which called unzip command? Anyway, any help would be greatly appreciated on this one too. Pierre 2012/6/27 Pierre Casenove pcasen...@gmail.com: OK, I finally got it working... but please, have a deep look on my code. 1) for python 2.4, I use only method read on zipfile 2) I modify _archive_dir value : if it has a trailing slash, I remove it. otherwise, solaris2mpm command was nont able to detect it was a patch, and consider the archive as a package. Thanks, Pierre 2012/6/26 Michael Mraka michael.mr...@redhat.com: Pierre Casenove wrote: % One last point on Solaris support: the hardware information page. I % attach a screenshot of the page with Chrome web browser. % 1) Under, General, we have (2) sparcv9 (1503 MHZ) right in the middle... % 2) Is it normal to get so few information? Unfortunately yes. -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Status of Solaris support
I've ran unzip command on 10_recommended.zip and here is the message I get at the beggining: # unzip -d tmp/ -q 10_Recommended.zip warning [10_Recommended.zip]: 76 extra bytes at beginning or within zipfile (attempting to process anyway) error [10_Recommended.zip]: reported length of central directory is -76 bytes too long (Atari STZip zipfile? J.H.Holm ZIPSPLIT 1.1 zipfile?). Compensating... So, it seems that the zip is not correct (I've tested 3 different patch_cluster for Sol 10) but unzip can handle thias, whereas python fails. Pierre 2012/6/28 Pierre Casenove pcasen...@gmail.com: Hello, Did you have time to review the patch? Now that I got patch working, I wanted to try patch_cluster and ZipFile class is complaining! # solaris2mpm --tempdir=/data/solaris/tmp/ 10_Recommended.zip Opening archive, this may take a while Bad magic number for central directory Error creating mpm for /data/solaris/10_Recommended.zip: zipfile.BadZipfile instance at 0x2ad1050c5e18 The Bad magic number for central directory appears during the creation of ZipFile object (before my code modification. The zip file is correct as unzip command is uncompressing it without any problem. I'm starting to wonder: is using ZipFile class really better thant old code, which called unzip command? Anyway, any help would be greatly appreciated on this one too. Pierre 2012/6/27 Pierre Casenove pcasen...@gmail.com: OK, I finally got it working... but please, have a deep look on my code. 1) for python 2.4, I use only method read on zipfile 2) I modify _archive_dir value : if it has a trailing slash, I remove it. otherwise, solaris2mpm command was nont able to detect it was a patch, and consider the archive as a package. Thanks, Pierre 2012/6/26 Michael Mraka michael.mr...@redhat.com: Pierre Casenove wrote: % One last point on Solaris support: the hardware information page. I % attach a screenshot of the page with Chrome web browser. % 1) Under, General, we have (2) sparcv9 (1503 MHZ) right in the middle... % 2) Is it normal to get so few information? Unfortunately yes. -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Status of Solaris support
Pierre Casenove wrote: % Hello, % Did you have time to review the patch? % % Now that I got patch working, I wanted to try patch_cluster and % ZipFile class is complaining! % # solaris2mpm --tempdir=/data/solaris/tmp/ 10_Recommended.zip % Opening archive, this may take a while % Bad magic number for central directory % Error creating mpm for /data/solaris/10_Recommended.zip: % zipfile.BadZipfile instance at 0x2ad1050c5e18 % % The Bad magic number for central directory appears during the % creation of ZipFile object (before my code modification. % The zip file is correct as unzip command is uncompressing it without % any problem. % % I'm starting to wonder: is using ZipFile class really better thant old % code, which called unzip command? % % Anyway, any help would be greatly appreciated on this one too. AFAIR this means patch zip file is newer than you zip command can understand. Solution is to upgrade zip package. % Pierre Regards, -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Status of Solaris support
Hello, Indeed, on RHEL 5: rpm -qf /usr/bin/unzip unzip-5.52-3.el5 on RHEL 6: # rpm -qa | grep unzip unzip-6.0-1.el6.x86_64 Problem is: unzip v6 is not available on RHEL 5... Is the conclusion that solaris2mpm is not compatible with RHEL 5? Pierre 2012/6/28 Michael Mraka michael.mr...@redhat.com: Pierre Casenove wrote: % Hello, % Did you have time to review the patch? % % Now that I got patch working, I wanted to try patch_cluster and % ZipFile class is complaining! % # solaris2mpm --tempdir=/data/solaris/tmp/ 10_Recommended.zip % Opening archive, this may take a while % Bad magic number for central directory % Error creating mpm for /data/solaris/10_Recommended.zip: % zipfile.BadZipfile instance at 0x2ad1050c5e18 % % The Bad magic number for central directory appears during the % creation of ZipFile object (before my code modification. % The zip file is correct as unzip command is uncompressing it without % any problem. % % I'm starting to wonder: is using ZipFile class really better thant old % code, which called unzip command? % % Anyway, any help would be greatly appreciated on this one too. AFAIR this means patch zip file is newer than you zip command can understand. Solution is to upgrade zip package. % Pierre Regards, -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Corrected query for pgsql support
Pierre Casenove wrote: % Hello, % Please find attached a complementary patch to correct the remove patch query. % Note that the first patch was already correcting part of the query % % Thanks, % % Pierre Hi Pierre, I've reviewed and commited both patches. Thanks. -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Corrected query for pgsql support
Thanks a lot. 2012/6/28 Michael Mraka michael.mr...@redhat.com: Pierre Casenove wrote: % Hello, % Please find attached a complementary patch to correct the remove patch query. % Note that the first patch was already correcting part of the query % % Thanks, % % Pierre Hi Pierre, I've reviewed and commited both patches. Thanks. -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6
I'm in the early stages of setting up Spacewalk on a RHEL5 server. The installation was started by someone else before 1.7 came out so they decided to hold of on RHEL6. Most of the environment here is running RHEL5 and we only have 1 or 2 test servers running RHEL6. I'm wondering how complicated it's likely to be to upgrade the server to RHEL6. I just found out this morning that RHEL6.3 was released recently, so I'm thinking I might be better off to bite the bullet before I get a bunch of servers registered into the system. Have you gone through an OS upgrade on your server? What are the essential steps? I have mrepo and Spacewalk running on the same server currently. What would I need to do to make the upgrade as smooth as possible without completely re-inventing the server from scratch? I know it's possible to do a database backup and restore it after upgrading. I looked at the wiki page for doing a spacewalk 1.6-1.7 upgrade. It looks like some of the pieces might be pulled from that procedure.Is there a Red Hat guide for upgrading the server hosting Satellite Server? That would presumably be pretty similar to what I'd need to do. Thanks for any thoughts you're willing to share about this. If there's already a guide written for this great! If not, maybe now is the time to add one to the wiki? And I'd be willing to help write and verify it. Thanks, Robert Robert Boyd Senior Systems Engineer robert.b...@peoplefluent.commailto:michael.dileona...@peoplefluent.com ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6
Hi Robert, I’m wondering how complicated it’s likely to be to upgrade the server to RHEL6. Upgrades from RHEL5 to 6 are not supported by RedHat, so if you care about support (what I would suspect since you're paying for it) this is not an option for you. I would go for: install RHEL6 in parallel, take Spacewalk offline, install Spacewalk on RHEL6, restore Database to replacement Spacewalk on RHEL6, sync /var/satellite and phase out the RHEL5 server. Before or afterwards, upgrade Spacewalk from 1.6 to 1.7 according to https://fedorahosted.org/spacewalk/wiki/HowToUpgrade regards Jens www.biotronik.com BIOTRONIK SE Co. KG Woermannkehre 1, 12359 Berlin, Germany Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501 Vertreten durch ihre Komplementärin: BIOTRONIK MT SE Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 118866 B Geschäftsführende Direktoren: Christoph Böhmer, Dr. Werner Braun, Dr. Lothar Krings, Dr. Torsten Wolf BIOTRONIK - A global manufacturer of advanced Cardiac Rhythm Management systems and Vascular Intervention devices. Quality, innovation, and reliability define BIOTRONIK and our growing success. We are innovators of technologies like the first wireless remote monitoring system - Home Monitoring®, Closed Loop Stimulation and coveted lead solutions as well as state-of-the-art stents, balloons and guide wires for coronary and peripheral indications. We highly invest in the development of drug eluting devices and are leading the industry with our drug eluting absorbable metal scaffold program. This e-mail and the information it contains including attachments are confidential and meant only for use by the intended recipient(s); disclosure or copying is strictly prohibited. If you are not addressed, but in the possession of this e-mail, please notify the sender immediately and delete the document. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6
Robert, Here is what I would do - It may seem like a lot, but you will have a lot of flexibility with nothing but time and a bit of resource to use. We are heavy vmware shop, but the same can be done in KVM/Xen or other virtualization platforms. This is how I hand all major upgrades - that no one knows how it turns out. 1) Create a virtual machine with proper parameters, and replicate your current RHEL5 with SPWLK 1.6 to test VM. 2) Upgrade your spacewalk 1.6 to 1.7 on test VM that still runs RHEL5. 3) Stand up another VM with RHEL6 and install vanilla spacewalk 1.7, install mrepo and rsync mrepo configs and repositories, if its postgres or oracle, replicate the cofigs - using the same settings as you had in previous prod setup. 4) Run export and import of DB, be it oracle or postgres from virtual RHEL5 (spacewalk 1.7) to virtual RHEL6 (spacewalk 1.7). 5) Rsync the content of /var/satellite/redhat/* to virtual RHEL6 with spacewalk 1.7 * You may need to match the hostnames or run hostname changer script. * There may be additional house cleaning, but in theory this should work. Once you have the process squared away, you can do the same thing on your prod system, or promote your virtual instance to prod, if you run it virtually. Good luck -ilya From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Boyd, Robert Sent: Thursday, June 28, 2012 11:04 AM To: spacewalk-list@redhat.com Subject: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6 I'm in the early stages of setting up Spacewalk on a RHEL5 server. The installation was started by someone else before 1.7 came out so they decided to hold of on RHEL6. Most of the environment here is running RHEL5 and we only have 1 or 2 test servers running RHEL6. I'm wondering how complicated it's likely to be to upgrade the server to RHEL6. I just found out this morning that RHEL6.3 was released recently, so I'm thinking I might be better off to bite the bullet before I get a bunch of servers registered into the system. Have you gone through an OS upgrade on your server? What are the essential steps? I have mrepo and Spacewalk running on the same server currently. What would I need to do to make the upgrade as smooth as possible without completely re-inventing the server from scratch? I know it's possible to do a database backup and restore it after upgrading. I looked at the wiki page for doing a spacewalk 1.6-1.7 upgrade. It looks like some of the pieces might be pulled from that procedure.Is there a Red Hat guide for upgrading the server hosting Satellite Server? That would presumably be pretty similar to what I'd need to do. Thanks for any thoughts you're willing to share about this. If there's already a guide written for this great! If not, maybe now is the time to add one to the wiki? And I'd be willing to help write and verify it. Thanks, Robert Robert Boyd Senior Systems Engineer robert.b...@peoplefluent.commailto:michael.dileona...@peoplefluent.com ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6
Ilya and Jens, I suppose my language wasn't clear in my request. I'm not upgrading from 1.6 to 1.7. I already installed 1.7 on RHEL5. I'm wanting to find out what the process would be to upgrade the server from RHEL5 to RHEL6. So I think I can take out the items related to upgrading from 1.6 to 1.7 here. Is that a fair statement? Robert From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Musayev, Ilya Sent: Thursday, June 28, 2012 11:49 AM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6 Robert, Here is what I would do - It may seem like a lot, but you will have a lot of flexibility with nothing but time and a bit of resource to use. We are heavy vmware shop, but the same can be done in KVM/Xen or other virtualization platforms. This is how I hand all major upgrades - that no one knows how it turns out. 1) Create a virtual machine with proper parameters, and replicate your current RHEL5 with SPWLK 1.6 to test VM. 2) Upgrade your spacewalk 1.6 to 1.7 on test VM that still runs RHEL5. 3) Stand up another VM with RHEL6 and install vanilla spacewalk 1.7, install mrepo and rsync mrepo configs and repositories, if its postgres or oracle, replicate the cofigs - using the same settings as you had in previous prod setup. 4) Run export and import of DB, be it oracle or postgres from virtual RHEL5 (spacewalk 1.7) to virtual RHEL6 (spacewalk 1.7). 5) Rsync the content of /var/satellite/redhat/* to virtual RHEL6 with spacewalk 1.7 * You may need to match the hostnames or run hostname changer script. * There may be additional house cleaning, but in theory this should work. Once you have the process squared away, you can do the same thing on your prod system, or promote your virtual instance to prod, if you run it virtually. Good luck -ilya From: spacewalk-list-boun...@redhat.commailto:spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Boyd, Robert Sent: Thursday, June 28, 2012 11:04 AM To: spacewalk-list@redhat.commailto:spacewalk-list@redhat.com Subject: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6 I'm in the early stages of setting up Spacewalk on a RHEL5 server. The installation was started by someone else before 1.7 came out so they decided to hold of on RHEL6. Most of the environment here is running RHEL5 and we only have 1 or 2 test servers running RHEL6. I'm wondering how complicated it's likely to be to upgrade the server to RHEL6. I just found out this morning that RHEL6.3 was released recently, so I'm thinking I might be better off to bite the bullet before I get a bunch of servers registered into the system. Have you gone through an OS upgrade on your server? What are the essential steps? I have mrepo and Spacewalk running on the same server currently. What would I need to do to make the upgrade as smooth as possible without completely re-inventing the server from scratch? I know it's possible to do a database backup and restore it after upgrading. I looked at the wiki page for doing a spacewalk 1.6-1.7 upgrade. It looks like some of the pieces might be pulled from that procedure.Is there a Red Hat guide for upgrading the server hosting Satellite Server? That would presumably be pretty similar to what I'd need to do. Thanks for any thoughts you're willing to share about this. If there's already a guide written for this great! If not, maybe now is the time to add one to the wiki? And I'd be willing to help write and verify it. Thanks, Robert Robert Boyd Senior Systems Engineer robert.b...@peoplefluent.commailto:michael.dileona...@peoplefluent.com ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] Replicate spacewalk core to another data center for HA
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 Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6
It makes it easier, I personally would look to stand up a fresh RHEL6 instance and install fresh spacewalk 1.7 and migrate spacewalk content (and other components) over. As Jens mentioned, there is no supported method of going from major RHEL5 to RHEL6. It may work, but you will end up with a very messy system. From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Boyd, Robert Sent: Thursday, June 28, 2012 12:03 PM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6 Ilya and Jens, I suppose my language wasn't clear in my request. I'm not upgrading from 1.6 to 1.7. I already installed 1.7 on RHEL5. I'm wanting to find out what the process would be to upgrade the server from RHEL5 to RHEL6. So I think I can take out the items related to upgrading from 1.6 to 1.7 here. Is that a fair statement? Robert From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Musayev, Ilya Sent: Thursday, June 28, 2012 11:49 AM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6 Robert, Here is what I would do - It may seem like a lot, but you will have a lot of flexibility with nothing but time and a bit of resource to use. We are heavy vmware shop, but the same can be done in KVM/Xen or other virtualization platforms. This is how I hand all major upgrades - that no one knows how it turns out. 1) Create a virtual machine with proper parameters, and replicate your current RHEL5 with SPWLK 1.6 to test VM. 2) Upgrade your spacewalk 1.6 to 1.7 on test VM that still runs RHEL5. 3) Stand up another VM with RHEL6 and install vanilla spacewalk 1.7, install mrepo and rsync mrepo configs and repositories, if its postgres or oracle, replicate the cofigs - using the same settings as you had in previous prod setup. 4) Run export and import of DB, be it oracle or postgres from virtual RHEL5 (spacewalk 1.7) to virtual RHEL6 (spacewalk 1.7). 5) Rsync the content of /var/satellite/redhat/* to virtual RHEL6 with spacewalk 1.7 * You may need to match the hostnames or run hostname changer script. * There may be additional house cleaning, but in theory this should work. Once you have the process squared away, you can do the same thing on your prod system, or promote your virtual instance to prod, if you run it virtually. Good luck -ilya From: spacewalk-list-boun...@redhat.commailto:spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Boyd, Robert Sent: Thursday, June 28, 2012 11:04 AM To: spacewalk-list@redhat.commailto:spacewalk-list@redhat.com Subject: [Spacewalk-list] Updating Spacewalk Server from RHEL5 to RHEL6 I'm in the early stages of setting up Spacewalk on a RHEL5 server. The installation was started by someone else before 1.7 came out so they decided to hold of on RHEL6. Most of the environment here is running RHEL5 and we only have 1 or 2 test servers running RHEL6. I'm wondering how complicated it's likely to be to upgrade the server to RHEL6. I just found out this morning that RHEL6.3 was released recently, so I'm thinking I might be better off to bite the bullet before I get a bunch of servers registered into the system. Have you gone through an OS upgrade on your server? What are the essential steps? I have mrepo and Spacewalk running on the same server currently. What would I need to do to make the upgrade as smooth as possible without completely re-inventing the server from scratch? I know it's possible to do a database backup and restore it after upgrading. I looked at the wiki page for doing a spacewalk 1.6-1.7 upgrade. It looks like some of the pieces might be pulled from that procedure.Is there a Red Hat guide for upgrading the server hosting Satellite Server? That would presumably be pretty similar to what I'd need to do. Thanks for any thoughts you're willing to share about this. If there's already a guide written for this great! If not, maybe now is the time to add one to the wiki? And I'd be willing to help write and verify it. Thanks, Robert Robert Boyd Senior Systems Engineer robert.b...@peoplefluent.commailto:michael.dileona...@peoplefluent.com ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 imusa...@webmd.net 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 Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
