红帽全球峰会此内容没有您所选择的语言版本。
Chapter 6. Optimizing content synchronization and storage
Download and mirroring policies control how much content is stored locally and how repositories stay in sync with upstream sources. Tune defaults, concurrency, and retention to balance disk use, bandwidth, and freshness.
6.1. Download policies overview
Red Hat Satellite provides multiple download policies for synchronizing RPM content. For example, you might want to download only the content metadata while deferring the actual content download for later.
Satellite Server has the following policies:
- Immediate
- Satellite Server downloads all metadata and packages during synchronization.
- On Demand
- Satellite Server downloads only the metadata during synchronization. Satellite Server only fetches and stores packages on the file system when Capsules or directly connected clients request them. This setting has no effect if you set a corresponding repository on a Capsule to Immediate because Satellite Server is forced to download all the packages.
The On Demand policy acts as a Lazy Synchronization feature because they save time synchronizing content. The lazy synchronization feature must be used only for Yum repositories. You can add the packages to content views and promote to lifecycle environments as normal.
Capsule Server has the following policies:
- Immediate
- Capsule Server downloads all metadata and packages during synchronization. Do not use this setting if the corresponding repository on Satellite Server is set to On Demand as Satellite Server is forced to download all the packages.
- On Demand
- Capsule Server only downloads the metadata during synchronization. Capsule Server fetches and stores packages only on the file system when directly connected clients request them. When you use an On Demand download policy, content is downloaded from Satellite Server if it is not available on Capsule Server.
- Inherit
- Capsule Server inherits the download policy for the repository from the corresponding repository on Satellite Server.
- Streamed Download Policy
- Streamed Download Policy for Capsules permits Capsules to avoid caching any content. When content is requested from the Capsule, it functions as a proxy and requests the content directly from the Satellite.
You can set the default download policy that Satellite applies to repositories that you create in all organizations.
Depending on whether it is a Red Hat or non-Red Hat custom repository, Satellite uses separate settings. Changing the default value does not change the setting in existing repositories, but only the default setting for new repositories.
Procedure
- In the Satellite web UI, navigate to Administer > Settings.
- Click the Content tab.
Change the default download policy depending on your requirements:
- To change the default download policy for a Red Hat repository, change the value of the Default Red Hat Repository download policy setting.
- To change the default download policy for a custom repository, change the value of the Default Custom Repository download policy setting.
You can set the default download policy that Satellite applies to repositories that you create in all organizations.
Depending on whether it is a Red Hat or non-Red Hat custom repository, Satellite uses separate settings. Changing the default value does not change the setting in existing repositories, but only the default setting for new repositories.
Procedure
To change the default download policy for Red Hat repositories to one of
immediateoron_demand, enter the following command:$ hammer settings set \ --name default_redhat_download_policy \ --value immediateTo change the default download policy for a non-Red Hat custom repository to one of
immediateoron_demand, enter the following command:$ hammer settings set \ --name default_download_policy \ --value immediate
You can set the download policy for a repository by using the Satellite web UI.
Procedure
- In the Satellite web UI, navigate to Content > Products.
- Select the required product name.
- On the Repositories tab, click the required repository name, locate the Download Policy field, and click the edit icon.
- From the list, select the required download policy and then click Save.
You can set the download policy for a repository by using Hammer CLI.
Procedure
List the repositories for an organization:
$ hammer repository list \ --organization-label My_Organization_LabelChange the download policy for a repository to
immediateoron_demand:$ hammer repository update \ --download-policy immediate \ --name "My_Repository" \ --organization-label My_Organization_Label \ --product "My_Product"
6.6. Mirroring policies overview
Mirroring keeps the local repository exactly in synchronization with the upstream repository. If any content is removed from the upstream repository since the last synchronization, with the next synchronization, it will be removed from the local repository as well.
You can use mirroring policies for finer control over mirroring of repodata and content when synchronizing a repository. For example, if it is not possible to mirror the repodata for a repository, you can set the mirroring policy to mirror only content for this repository.
Satellite Server has the following mirroring policies:
- Additive
- Neither the content nor the repodata is mirrored. Thus, only new content added since the last synchronization is added to the local repository and nothing is removed.
- Content Only
- Mirrors only content and not the repodata. Some repositories do not support metadata mirroring, in such cases you can set the mirroring policy to content only to only mirror the content.
- Complete Mirroring
Mirrors content as well as repodata. This is the fastest method. This mirroring policy is only available for Yum content.
WarningAvoid republishing metadata for repositories with Complete Mirror mirroring policy. This also applies to content views containing repositories with the Complete Mirror mirroring policy.
You can set the default mirroring policy that Satellite applies to your custom repository that you create in all organizations.
Depending on whether it is a Yum or non-Yum custom repository, Satellite uses separate settings. Only Yum repositories support the mirror_complete mirroring policy. Red Hat repositories use the mirror_complete policy by default and are not affected by these settings. Changing the default value does not change existing mirroring policy settings per repository. For more information on mirroring policies, see Section 6.6, “Mirroring policies overview”.
Procedure
- In the Satellite web UI, navigate to Administer > Settings.
- Click the Content tab.
Change the default mirroring policy depending on your requirements:
- To change the default mirroring policy for a Yum custom repository, change the value of the Default custom yum repository mirroring policy setting.
- To change the default mirroring policy for a non-Yum custom repository, change the value of the Default custom non-yum repository mirroring policy setting.
You can set the default mirroring policy that Satellite applies to your custom repository that you create in all organizations.
Depending on whether it is a Yum or non-Yum custom repository, Satellite uses separate settings. Only Yum repositories support the mirror_complete mirroring policy. Red Hat repositories use the mirror_complete policy by default and are not affected by these settings. Changing the default value does not change existing mirroring policy settings per repository. For more information on mirroring policies, see Section 6.6, “Mirroring policies overview”.
Procedure
Change the default mirroring policy for a Yum custom repository to
additive,mirror_content_only, ormirror_complete:$ hammer settings set \ --name default_yum_mirroring_policy \ --value mirror_completeChange the default mirroring policy for a non-Yum custom repository to
additiveormirror_content_only:$ hammer settings set \ --name default_non_yum_mirroring_policy \ --value additive
You can set the mirroring policy for a repository by using the Satellite web UI.
Procedure
- In the Satellite web UI, navigate to Content > Products.
- Select the product name.
- On the Repositories tab, click the repository name, locate the Mirroring Policy field, and click the edit icon.
- From the list, select a mirroring policy and click Save.
You can set the mirroring policy for a repository by using Hammer CLI.
Procedure
List the repositories for an organization:
$ hammer repository list \ --organization-label My_Organization_LabelChange the mirroring policy for a repository to
additive,mirror_complete, ormirror_content_only:$ hammer repository update \ --id My_Repository_ID \ --mirroring-policy mirror_complete
6.11. Limiting synchronization concurrency
By default, each Repository Synchronization job can fetch up to ten files at a time. This can be adjusted on a per repository basis.
Increasing the limit may improve performance, but can cause the upstream server to be overloaded or start rejecting requests. If you are seeing Repository syncs fail due to the upstream servers rejecting requests, you may want to try lowering the limit.
Procedure
Define a value for synchronization concurrency:
$ hammer repository update \ --download-concurrency 5 \ --id Repository_ID \ --organization "My_Organization"
You can limit the growth of content in the Library lifecycle environment on Satellite Server by restraining the number of package versions in synchronized repositories.
Procedure
- In the Satellite web UI, navigate to Content > Products.
- Select your product.
- On the Repository tab, select your repository.
-
Set the Mirroring Policy to
Additive. Define the number of retained package versions:
-
Set Retain package versions to
1to only keep the latest synchronized package version on Satellite. -
Set Retain package versions to
2or higher to keep multiple package versions on Satellite.
-
Set Retain package versions to
Additional resources
You can limit the growth of content in the Library lifecycle environment on Satellite Server by restraining the number of package versions in synchronized repositories.
Procedure
Configure your repository to retain a limited number of package versions in Satellite:
$ hammer repository update \ --id My_Repository_ID \ --mirroring-policy additive \ --retain-package-versions-count My_Package_Versions_Count-
Set My_Package_Versions_Count to
1to only keep the latest synchronized package version on Satellite. -
Set My_Package_Versions_Count to
2or higher to keep multiple package versions on Satellite.
-
Set My_Package_Versions_Count to
Additional resources
'%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}