9장. Synchronizing content between Satellite Servers
In a Satellite setup with multiple Satellite Servers, you can use Inter-Satellite Synchronization (ISS) to synchronize content from one upstream server to one or more downstream servers.
There are two possible ISS configurations of Satellite, depending on how you deployed your infrastructure:
- ISS Network Sync
If your upstream server can communicate with the downstream server over a network, you can synchronize content over HTTPS.
Configure your Satellite to synchronize content over a network.
- ISS Export Sync
If your upstream and downstream servers are air gapped, you can synchronize content by using export and import.
Configure your Satellite to synchronize content by using export and import.
Additional resources
- For more information on ISS use cases and scenarios, see Inter-Satellite Synchronization scenarios in Overview, concepts, and deployment considerations.
- Hammer content export fails with "Path '/the/path' is not an allowed export path" in the Red Hat Knowledgebase
9.1. Content synchronization by using export and import
There are multiple approaches for synchronizing content by using the export and import workflow:
- You employ the upstream Satellite Server as a content store, which means that you sync the whole Library rather than content view versions. This approach offers the simplest export/import workflow. In such case, you can manage the content view versions downstream. For more information, see 9.1.1절. “Using an upstream Satellite Server as a content store”.
- You use the upstream Satellite Server to sync content view versions. This approach offers more control over what content is synced between Satellite Servers. For more information, see 9.1.2절. “Using an upstream Satellite Server to synchronize content view versions”.
- You sync a single repository. This can be useful if you use the content-view syncing approach, but you want to sync an additional repository without adding it to an existing content view. For more information, see 9.1.3절. “Synchronizing a single repository”.
Synchronizing content by using export and import requires the same major version of Satellite on both the downstream and upstream Satellite Servers.
When you are unable to match upstream and downstream Satellite versions, you can use:
- Syncable exports and imports.
- Inter-Satellite Synchronization (ISS) with your upstream Satellite connected to the Internet and your downstream Satellite connected to the upstream Satellite.
9.1.1. Using an upstream Satellite Server as a content store
In this scenario, you use the upstream Satellite Server as a content store for updates rather than to manage content. You use the downstream Satellite Server to manage content for all infrastructure behind the isolated network. You export the Library content from the upstream Satellite Server and import it into the downstream Satellite Server.
On the upstream Satellite Server
Ensure that repositories are using the Immediate download policy in one of the following ways:
- For existing repositories using On Demand, change their download policy on the repository details page to Immediate.
- For new repositories, ensure that the Default Red Hat Repository download policy setting is set to Immediate before enabling Red Hat repositories, and that the Default download policy is set to Immediate for custom repositories.
For more information, see 4.9절. “Download policies overview”.
Enable the content that you want to synchronize. For more information, see 4.6절. “Enabling Red Hat repositories”.
If you want to sync custom content, first create a custom product and then synchronize repositories.
Synchronize the enabled content:
-
On the first export, perform a
completeLibrary export so that all the synchronized content is exported. This generates content archives that you can later import into one or more downstream Satellite Servers. For more information on performing a complete Library export, see 9.3절. “Exporting the Library environment”. - Export all future updates on the upstream Satellite Server incrementally. This generates leaner content archives that contain only a recent set of updates. For example, if you enable and synchronize a new repository, the next exported content archive contains content only from the newly enabled repository. For more information on performing an incremental Library export, see 9.6절. “Exporting the Library environment incrementally”.
-
On the first export, perform a
On the downstream Satellite Server
- Bring the content exported from the upstream Satellite Server over to the hard disk.
-
Place it inside a directory under
/var/lib/pulp/imports. Import the content to an organization using the procedure outlined in 9.15절. “Importing into the Library environment”.
You can then manage content using content views or lifecycle environments as you require.
9.1.2. Using an upstream Satellite Server to synchronize content view versions
In this scenario, you use the upstream Satellite Server not only as a content store, but also to synchronize content for all infrastructure behind the isolated network. You curate updates coming from the CDN into content views and lifecycle environments. Once you promote content to a designated lifecycle environment, you can export the content from the upstream Satellite Server and import it into the downstream Satellite Server.
On the upstream Satellite Server
Ensure that repositories are using the Immediate download policy in one of the following ways:
- For existing repositories using On Demand, change their download policy on the repository details page to Immediate.
- For new repositories, ensure that the Default Red Hat Repository download policy setting is set to Immediate before enabling Red Hat repositories, and that the Default download policy is set to Immediate for custom repositories.
For more information, see 4.9절. “Download policies overview”.
Enable the content that you want to synchronize. For more information, see 4.6절. “Enabling Red Hat repositories”.
If you want to sync custom content, first create a custom product and then synchronize repositories.
Synchronize the enabled content:
-
For the first export, perform a
completeversion export on the content view version that you want to export. For more information see, 9.7절. “Exporting a content view version”. This generates content archives that you can import into one or more downstream Satellite Servers. - Export all future updates in the connected Satellite Servers incrementally. This generates leaner content archives that contain changes only from the recent set of updates. For example, if your content view has a new repository, this exported content archive contains only the latest changes. For more information, see 9.9절. “Exporting a content view version incrementally”.
- When you have new content, republish the content views that include this content before exporting the increment. For more information, see 7장. Managing content views. This creates a new content view version with the appropriate content to export.
-
For the first export, perform a
On the downstream Satellite Server
- Bring the content exported from the upstream Satellite Server over to the hard disk.
-
Place it inside a directory under
/var/lib/pulp/imports. - Import the content to the organization that you want. For more information, see 9.17절. “Importing a content view version”. This will create a content view version from the exported content archives and then import content appropriately.
9.1.3. Synchronizing a single repository
In this scenario, you export and import a single repository.
On the upstream Satellite Server
Ensure that the repository is using the Immediate download policy in one of the following ways:
- For existing repositories using On Demand, change their download policy on the repository details page to Immediate.
- For new repositories, ensure that the Default Red Hat Repository download policy setting is set to Immediate before enabling Red Hat repositories, and that the Default download policy is set to Immediate for custom repositories.
For more information, see 4.9절. “Download policies overview”.
Enable the content that you want to synchronize. For more information, see 4.6절. “Enabling Red Hat repositories”.
If you want to sync custom content, first create a custom product and then synchronize product repositories.
Synchronize the enabled content:
-
On the first export, perform a
completerepository export so that all the synchronized content is exported. This generates content archives that you can later import into one or more downstream Satellite Servers. For more information on performing a complete repository export, see 9.10절. “Exporting a repository”. - Export all future updates on the upstream Satellite Server incrementally. This generates leaner content archives that contain only a recent set of updates. For more information on performing an incremental repository export, see 9.12절. “Exporting a repository incrementally”.
-
On the first export, perform a
On the downstream Satellite Server
- Bring the content exported from the upstream Satellite Server over to the hard disk.
-
Place it inside a directory under
/var/lib/pulp/imports. Import the content to an organization. See 9.19절. “Importing a repository”.
You can then manage content using content views or lifecycle environments as you require.
'%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}