Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
6.4. Inter-Satellite Sync
RHN Satellite 5.3 or greater supports synchronization between two Satellites. This synchronization, also called Inter-Satellite Sync, allows administrators to simplify the process of coordinating content from one RHN Satellite source to another or several others.
The following are the basic requirements for Inter-satellite Sync.
- At least two RHN Satellite 5.3 or greater servers
- At least one RHN Satellite populated with at least one channel
- Master RHN Satellite SSL certificate available on each of the slave RHN Satellites for secure connection
6.4.1. Recommended Models for Inter-Satellite Sync
Copia collegamentoCollegamento copiato negli appunti!
The Inter-Satellite Sync feature for Satellite provides facilities for synchronizing content between two or more Satellites. The following are some of the more typical uses that show the possibilities of Inter-Satellite Sync and help guide you in determining how to make the most of this feature in your environment.
Note
If you are not sure if the Inter-Satellite Sync feature is right for your organization, please note that you can continue to use RHN Satellite 5.3 or greater in the typical manner. Installing or upgrading to RHN Satellite 5.3 or greater does not require that you make use of this feature.
Figure 6.1. Staging Satellite
In this example, the Stage Satellite is used to prepare the content and perform quality assurance (QA) work — to make sure that packages are fit for production use. After content is approved to go to production, the Production Satellite will then synchronize the content from the Stage Satellite.
Figure 6.2. Master Server and Slave Peers that include their own custom content
In this example, the master Satellite is the development channel, from which content is distributed to all production slave Satellites. Some slave Satellites have extra content not present in master Satellite channels. These packages are preserved, but all changes from master Satellite are synchronized to Slave Satellite.
Figure 6.3. Slave Satellites are maintained exactly as the master Satellite
In this example, the master Satellite (for example, a software or Hardware vendor) provides data to its customer. These changes are regularly synchronized to slave Satellites.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}