Chapter 4. Importing content

Procedure

1. In the Satellite web UI, navigate to Content > Content Credentials. In the Content Credentials window, click Create Content Credential.
2. In the Name field, enter a name for your SSL certificate.
3. From the Type list, select SSL Certificate.
4. In the Content Credentials Content field, paste your SSL certificate, or click Browse to upload your SSL certificate.
5. Click Save.

CLI procedure

1. Copy the SSL certificate to your Satellite Server:

   $ scp My_SSL_Certificate root@satellite.example.com:~/.

   Or download the SSL certificate to your Satellite Server from an online source:

   $ wget -P ~ http://upstream-satellite.example.com/pub/katello-server-ca.crt

2. Upload the SSL Certificate to Satellite:

   # hammer content-credential create \
   --content-type cert \
   --name "My_SSL_Certificate" \
   --organization "My_Organization" \
   --path ~/My_SSL_Certificate

Procedure

1. In the Satellite web UI, navigate to Content > Products, click Create Product.
2. In the Name field, enter a name for the product. Satellite automatically completes the Label field based on what you have entered for Name.
3. Optional: From the GPG Key list, select the GPG key for the product.
4. Optional: From the SSL CA Cert list, select the SSL CA certificate for the product.
5. Optional: From the SSL Client Cert list, select the SSL client certificate for the product.
6. Optional: From the SSL Client Key list, select the SSL client key for the product.
7. Optional: From the Sync Plan list, select an existing sync plan or click Create Sync Plan and create a sync plan for your product requirements.
8. In the Description field, enter a description of the product.
9. Click Save.

Procedure

1. In the Satellite web UI, navigate to Content > Products and select the product that you want to use, and then click New Repository.
2. In the Name field, enter a name for the repository. Satellite automatically completes the Label field based on what you have entered for Name.
3. Optional: In the Description field, enter a description for the repository.
4. From the Type list, select yum as type of repository.
5. Optional: From the Restrict to Architecture list, select an architecture. If you want to make the repository available to all hosts regardless of the architecture, ensure to select No restriction.
6. Optional: From the Restrict to OS Version list, select the OS version. If you want to make the repository available to all hosts regardless of the OS version, ensure to select No restriction.

7. Optional: In the Upstream URL field, enter the URL of the external repository to use as a source. Satellite supports three protocols: http://, https://, and file://. If you are using a file:// repository, you have to place it under /var/lib/pulp/sync_imports/ directory.

   If you do not enter an upstream URL, you can manually upload packages.

8. Optional: Check the Ignore SRPMs checkbox to exclude source RPM packages from being synchronized to Satellite.
9. Optional: Check the Ignore treeinfo checkbox if you receive the error Treeinfo file should have INI format. All files related to Kickstart will be missing from the repository if treeinfo files are skipped.
10. Select the Verify SSL checkbox if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.
11. Optional: In the Upstream Username field, enter the user name for the upstream repository if required for authentication. Clear this field if the repository does not require authentication.
12. Optional: In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.
13. Optional: In the Upstream Authentication Token field, provide the token of the upstream repository user for authentication. Leave this field empty if the repository does not require authentication.
14. From the Download Policy list, select the type of synchronization Satellite Server performs. For more information, see Section 4.9, “Download policies overview”.
15. From the Mirroring Policy list, select the type of content synchronization Satellite Server performs. For more information, see Section 4.12, “Mirroring policies overview”.
16. Optional: In the Retain package versions field, enter the number of versions you want to retain per package.
17. Optional: In the HTTP Proxy Policy field, select an HTTP proxy.
18. From the Checksum list, select the checksum type for the repository.
19. Optional: You can clear the Unprotected checkbox to require a subscription entitlement certificate for accessing this repository. By default, the repository is published through HTTP.
20. Optional: From the GPG Key list, select the GPG key for the product.
21. Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.
22. Optional: In the SSL Client cert field, select the SSL Client Certificate for the repository.
23. Optional: In the SSL Client Key field, select the SSL Client Key for the repository.
24. Click Save to create the repository.

CLI procedure

1. Enter the following command to create the repository:

   # hammer repository create \
   --arch "My_Architecture" \
   --content-type "yum" \
   --gpg-key-id My_GPG_Key_ID \
   --name "My_Repository" \
   --organization "My_Organization" \
   --os-version "My_OS_Version" \
   --product "My_Product" \
   --publish-via-http true \
   --url My_Upstream_URL

Procedure

1. In the Satellite web UI, navigate to Content > Red Hat Repositories.
2. To find repositories, either enter the repository name, or toggle the Recommended Repositories button to the on position to view a list of repositories that you require.
3. In the Available Repositories pane, click a repository to expand the repository set.
4. Click the Enable icon next to the base architecture and release version that you want.

CLI procedure

1. To search for your product, enter the following command:

   # hammer product list --organization "My_Organization"

2. List the repository set for the product:

   # hammer repository-set list \
   --product "Red Hat Enterprise Linux Server" \
   --organization "My_Organization"

3. Enable the repository using either the name or ID number. Include the release version, such as 7Server, and base architecture, such as x86_64.

   # hammer repository-set enable \
   --name "Red Hat Enterprise Linux 7 Server (RPMs)" \
   --releasever "7Server" \
   --basearch "x86_64" \
   --product "Red Hat Enterprise Linux Server" \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Products and select the product that contains the repositories that you want to synchronize.
2. Select the repositories that you want to synchronize and click Sync Now.
3. Optional: To view the progress of the synchronization in the Satellite web UI, navigate to Content > Sync Status and expand the corresponding product or repository tree.

Procedure

1. Log in to your Satellite Server using SSH.

2. Run the following Bash script:

   ORG="My_Organization"
   
   for i in $(hammer --no-headers --csv repository list --organization $ORG --fields Id)
   do
     hammer repository synchronize --id ${i} --organization $ORG --async
   done

Procedure

1. In the Satellite web UI, navigate to Administer > Settings.
2. Click the Content tab.

3. 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.

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select the required product name.
3. On the Repositories tab, click the required repository name, locate the Download Policy field, and click the edit icon.
4. From the list, select the required download policy and then click Save.

CLI procedure

1. List the repositories for an organization:

   # hammer repository list \
   --organization-label My_Organization_Label

2. Change the download policy for a repository to immediate or on_demand:

   # hammer repository update \
   --download-policy immediate \
   --name "My_Repository" \
   --organization-label My_Organization_Label \
   --product "My_Product"

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select the product name.
3. On the Repositories tab, click the repository name, locate the Mirroring Policy field, and click the edit icon.
4. From the list, select a mirroring policy and click Save.

CLI procedure

1. List the repositories for an organization:

   # hammer repository list \
   --organization-label My_Organization_Label

2. Change the mirroring policy for a repository to additive, mirror_complete, or mirror_content_only:

   # hammer repository update \
   --id 1 \
   --mirroring-policy mirror_complete

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Click the name of the custom product.
3. In the Repositories tab, click the name of the custom RPM repository.
4. Under Upload Package, click Browse…​ and select the RPM you want to upload.
5. Click Upload.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Capsules, and select the Capsule where you want to see the synchronized content.
2. Select the Overview tab.
3. Under Content Sync, toggle the Synchronize button to do an Optimized Sync or a Complete Sync to synchronize the Capsule which refreshes the content counts.
4. Select the Content tab.
5. Choose an Environment to view content views available to those Capsules by clicking >.
6. Expand the content view by clicking > to view repositories available to the content view and the specific version for the environment.
7. View the number of content counts under Packages specific to yum repositories.
8. View the number of errata, package groups, files, container tags, container manifests, and Ansible collections under Additional content.
9. Click the vertical ellipsis in the column to the right next to the environment and click Refresh counts to refresh the content counts synchronized on the Capsule under Packages.

Procedure

1. On Satellite, to verify the ports that are permitted by SELinux for content synchronization, enter a command as follows:

   # semanage port -l | grep ^http_port_t
   http_port_t     tcp      80, 81, 443, 488, 8008, 8009, 8443, 9000

2. To configure SELinux to permit a port for content synchronization, for example 10011, enter a command as follows:

   # semanage port -a -t http_port_t -p tcp 10011

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select the product containing the corrupted repository.
3. Select the name of a repository you want to synchronize.
4. To perform optimized sync or complete sync, select Advanced Sync from the Select Action menu.
5. Select the required option and click Sync.
6. Optional: To verify the checksum, click Verify Content Checksum from the Select Action menu.

CLI procedure

1. Obtain a list of repository IDs:

   # hammer repository list \
   --organization "My_Organization"

2. Synchronize a corrupted repository using the necessary option:

   • For the optimized synchronization:

     # hammer repository synchronize \
     --id My_ID

   • For the complete synchronization:

     # hammer repository synchronize \
     --id My_ID \
     --skip-metadata-check true

   • For the validate content synchronization:

     # hammer repository synchronize \
     --id My_ID \
     --validate-contents true

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select the product that includes the repository for which you want to republish metadata.
3. On the Repositories tab, select a repository.

4. To republish metadata for the repository, click Republish Repository Metadata from the Select Action menu.

   Note

   This action is not available for repositories that use the Complete Mirroring policy because the metadata is copied verbatim from the upstream source of the repository.

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Select a content view.
3. On the Versions tab, select a content view version.
4. To republish metadata for the content view version, click Republish repository metadata from the vertical ellipsis icon.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > HTTP Proxies.
2. Select New HTTP Proxy.
3. In the Name field, enter a name for the HTTP proxy.
4. In the URL field, enter the URL for the HTTP proxy, including the port number.
5. If your HTTP proxy requires authentication, enter a Username and Password.
6. Optional: In the Test URL field, enter the HTTP proxy URL, then click Test Connection to ensure that you can connect to the HTTP proxy from Satellite.
7. Click the Locations tab and add a location.
8. Click the Organization tab and add an organization.
9. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Content > Products and select the products that you want to change.
2. From the Select Action list, select Manage HTTP Proxy.

3. Select an HTTP Proxy Policy from the list:

   • Global Default: Use the global default proxy setting.
   • No HTTP Proxy: Do not use an HTTP proxy, even if a global default proxy is configured.
   • Use specific HTTP Proxy: Select an HTTP Proxy from the list. You must add HTTP proxies to Satellite before you can select a proxy from this list. For more information, see Section 4.21, “Adding an HTTP proxy”.
4. Click Update.

Procedure

1. In the Satellite web UI, navigate to Content > Products and click the name of the product that contains the repository.
2. In the Repositories tab, click the name of the repository.
3. Locate the HTTP Proxy field and click the edit icon.

4. Select an HTTP Proxy Policy from the list:

   • Global Default: Use the global default proxy setting.
   • No HTTP Proxy: Do not use an HTTP proxy, even if a global default proxy is configured.
   • Use specific HTTP Proxy: Select an HTTP Proxy from the list. You must add HTTP proxies to Satellite before you can select a proxy from this list. For more information, see Section 4.21, “Adding an HTTP proxy”.
5. Click Save.

Procedure

1. In the Satellite web UI, navigate to Content > Sync Plans and click New Sync Plan.
2. In the Name field, enter a name for the plan.
3. Optional: In the Description field, enter a description of the plan.
4. From the Interval list, select the interval at which you want the plan to run.
5. From the Start Date and Start Time lists, select when to start running the synchronization plan.
6. Click Save.

CLI procedure

1. To create the synchronization plan, enter the following command:

   # hammer sync-plan create \
   --description "My_Description" \
   --enabled true \
   --interval daily \
   --name "My_Products" \
   --organization "My_Organization" \
   --sync-date "2023-01-01 01:00:00"

2. View the available sync plans for an organization to verify that the sync plan has been created:

   # hammer sync-plan list --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select a product.
3. On the Details tab, select a Sync Plan from the drop down menu.

CLI procedure

1. Assign a sync plan to a product:

   # hammer product set-sync-plan \
   --name "My_Product_Name" \
   --organization "My_Organization" \
   --sync-plan "My_Sync_Plan_Name"

Procedure

1. Run the following Bash script:

   ORG="My_Organization"
   SYNC_PLAN="daily_sync_at_3_a.m"
   
   hammer sync-plan create --name $SYNC_PLAN --interval daily --sync-date "2023-04-5 03:00:00" --enabled true --organization $ORG
   for i in $(hammer --no-headers --csv --csv-separator="|" product list --organization $ORG --per-page 999 | grep -vi not_synced | awk -F'|' '$5 != "0" { print $1}')
   do
     hammer product set-sync-plan --sync-plan $SYNC_PLAN --organization $ORG --id $i
   done

2. After executing the script, view the products assigned to the sync plan:

   # hammer product list --organization $ORG --sync-plan $SYNC_PLAN

1. Download a copy of the version specific repository package to your local machine:

   $ wget http://www.example.com/9.5/example-9.5-2.noarch.rpm

2. Extract the RPM file without installing it:

   $ rpm2cpio example-9.5-2.noarch.rpm | cpio -idmv

Procedure

1. In the Satellite web UI, navigate to Content > Content Credentials and in the upper-right of the window, click Create Content Credential.
2. Enter the name of your repository and select GPG Key from the Type list.

3. Either paste the GPG key into the Content Credential Contents field, or click Browse and select the GPG key file that you want to import.

   If your custom repository contains content signed by multiple GPG keys, you must enter all required GPG keys in the Content Credential Contents field with new lines between each key, for example:

   -----BEGIN PGP PUBLIC KEY BLOCK-----
   
   mQINBFy/HE4BEADttv2TCPzVrre+aJ9f5QsR6oWZMm7N5Lwxjm5x5zA9BLiPPGFN
   4aTUR/g+K1S0aqCU+ZS3Rnxb+6fnBxD+COH9kMqXHi3M5UNzbp5WhCdUpISXjjpU
   XIFFWBPuBfyr/FKRknFH15P+9kLZLxCpVZZLsweLWCuw+JKCMmnA
   =F6VG
   -----END PGP PUBLIC KEY BLOCK-----
   
   -----BEGIN PGP PUBLIC KEY BLOCK-----
   
   mQINBFw467UBEACmREzDeK/kuScCmfJfHJa0Wgh/2fbJLLt3KSvsgDhORIptf+PP
   OTFDlKuLkJx99ZYG5xMnBG47C7ByoMec1j94YeXczuBbynOyyPlvduma/zf8oB9e
   Wl5GnzcLGAnUSRamfqGUWcyMMinHHIKIc1X1P4I=
   =WPpI
   -----END PGP PUBLIC KEY BLOCK-----

4. Click Save.

CLI procedure

1. Copy the GPG key to your Satellite Server:

   $ scp ~/etc/pki/rpm-gpg/RPM-GPG-KEY-EXAMPLE-95 root@satellite.example.com:~/.

2. Upload the GPG key to Satellite:

   # hammer content-credentials create \
   --content-type gpg_key \
   --name "My_GPG_Key" \
   --organization "My_Organization" \
   --path ~/RPM-GPG-KEY-EXAMPLE-95

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Click the product that contains the repository sets you want to restrict.
3. In the Repositories tab, click the repository you want to restrict.

4. In the Publishing Settings section, set the following options:

   • Set Restrict to OS version to restrict the operating system version.
   • Set Restrict to architecture to restrict the architecture.