[Spacewalk-list] Need to sync SW data via PUSH between environments

[Snyder, Chris]

Ok - thanks.  I'll investigate this angle.

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Matt Micene
Sent: Wednesday, May 15, 2013 12:18 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Need to sync SW data via PUSH between environments

Chris,

I deal with a few folks who have disconnected Satellites in multiple enclaves.  Depending on your needs, I would suggest looking into rhn-satellite-exporter and the associated man / documentation

https://access.redhat.com/site/documentation/en-US/Red_Hat_Network_Satellite/5.5/html/Installation_Guide/sect-Installation_Guide-Content_and_Synchronization-Satellite_Export.html

Essentially, the exporter can be used to dump and copy Satellite data from the source (in your case test) to the other environments.  How you actually move the data can comply with your security requirements (shared access point, sneakernet, etc).  Once you have the export available on the targeted Satellite, you can use satellite-sync with the -m option to pull from a mount instead of RHN.

HTH,
Matt


From: spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Snyder, Chris
Sent: Wednesday, May 15, 2013 11:54 AM
To: Spacewalk-list at redhat.com<mailto:Spacewalk-list at redhat.com>
Subject: [Spacewalk-list] Need to sync SW data via PUSH between environments

I'm just starting to investigate how to synchronize between spacewalk servers.  And I think I have a problem.  >From what I've read it appears that the only way to synchronize data using the 'satellite-sync' command is via a PULL from the master server by a slave server.  This is not possible in my environments.

We have test,  staging, and production environments, each physically separate and completely network independent and we only allow connections from test to production or test to staging, not the other way around.    Our normal operating procedures require us to apply all updates to the test environment, work out any issues, then push those updates to our staging, check everything again, and then finally from test to our production environments.  Currently our sole Spacewalk instance exists in our test environment and we want to implement slaves in both staging and production.

So is it possibly to use the 'satellite-sync' tool to PUSH updates to slaves from a master server?  If not, what other options do I have to sync my software channels, packages, kickstart configurations, and configuration channels between environments?

Thx
Chris.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130515/8577dee4/attachment.htm>