10.3. Inter-Satellite Synchronization Use Cases

This example uses one Satellite as a staging Satellite to prepare content and perform quality assurance on the packages to ensure they are fit for production use. When content is approved to go to production, the production satellite can synchronize the content from the stage satellite.

In this example, the master satellite provides data directly to the slaves and changes are regularly synchronized.

This example uses the master satellite as a development channel, from which content is distributed to all production slave satellites. Some of the slave satellites have extra content that is not present in the master satellite channels. These packages are preserved, but all changes from the master satellite are synchronized to the slaves.

In this environment, two Red Hat Satellite servers act as both master and salve to each other and can synchronize content between them. The Satellite server where the command satellite-sync is run will pull the content from the other Satellite server and the synchronized data will depend on the options run with satellite-sync. Without any options, the synchronization will attempt to update everything that was previously synchronized.

See Section 10.1.1, “Manual Configuration” for configuring a Master Satellite. Configuring both Satellite servers as a Master will create a bi-directional sync.