https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Network_Satellite/5.5/html-single/Installation_Guide/index.html#chap-Installation_Guide-Inter-Sat_Sync 7.1 After content is approved to go to production, the Production Satellite will then synchronize the content from the Stage Satellite. 7.2 These packages are preserved, but all changes from Master Satellite are synchronized to Slave Satellite. In 7.1, it implies that the Production Satellite will be performing the action, while in 7.2, it implies that the Master Satellite will perofrm the action. Expected Result: Documentation needs to clarify if the action is from Master to Production or the other way around. Who performs the action?
OK. So, for Inter Satellite Sync, assume setup like: MASTER (QA Satellite) ------ SLAVE1 - Satellite Production ------ SLAVE2 - Satellite Stage The master Satellite runs satellite-sync and imports content from RHN. The Satellite Admin will clone channels and clone errata/packages on the Master Satellite. The Slave Satellites *never* see those changes, until the Satellite Admin runs satellite-sync on the Slave Satellite. We /should/ be consistent with the terms, and I'd recommend master/slave to be used consistently, with maybe an example topology where master = stage & slave = production. If that was the case, then read: 7.1 After content is approved to go to production, the Slave Satellite (Production) will then synchronize the content from the Master Satellite (Stage). - This will use satellite-sync to pull the content from the Master onto the Slave Satellite. 7.2 These packages are preserved, but all changes from Master Satellite (Stage) are synchronized to Slave Satellite (production). Hope this helps. Cliff
ISS chapter has been removed from the Install Guide and is now in the Reference Guide.