Procedure

1. In the Satellite web UI, navigate to Administer > Organizations.
2. Click New Organization.
3. In the Name field, enter a name for the organization.
4. In the Label field, enter a unique identifier for the organization. This is used for creating and mapping certain assets, such as directories for content storage. Use letters, numbers, underscores, and dashes, but no spaces.
5. Optional: in the Description field, enter a description for the organization.
6. Click Submit.
7. If you have hosts with no organization assigned, select the hosts that you want to add to the organization, then click Proceed to Edit.
8. In the Edit page, assign the infrastructure resources that you want to add to the organization. This includes networking resources, installation media, kickstart templates, and other parameters. You can return to this page at any time by navigating to Administer > Organizations and then selecting an organization to edit.
9. Click Submit.

CLI procedure

1. To create an organization, enter the following command:

   # hammer organization create \
   --name "My_Organization" \
   --label "My_Organization_Label" \
   --description "My_Organization_Description"

2. Optional: To edit an organization, enter the hammer organization update command. For example, the following command assigns a compute resource to the organization:

   # hammer organization update \
   --name "My_Organization" \
   --compute-resource-ids 1

Procedure

1. In the Satellite web UI, navigate to Administer > Organizations.
2. Select an organization that you want to generate a debug certificate for.
3. Click Generate and Download.
4. Save the certificate file in a secure location.

Prerequisites

1. Create and download an organization certificate as described in Section 3.3, “Creating an Organization Debug Certificate”.

2. Open the X.509 certificate, for example, for the default organization:

   $ vi 'Default Organization-key-cert.pem'

3. Copy the contents of the file from -----BEGIN RSA PRIVATE KEY----- to -----END RSA PRIVATE KEY-----, into a key.pem file.
4. Copy the contents of the file from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE-----, into a cert.pem file.

1. To create a PKCS12 format certificate, enter the following command:

   $ openssl pkcs12 -keypbe PBE-SHA1-3DES -certpbe PBE-SHA1-3DES -export -in cert.pem -inkey key.pem -out My_Organization_Label.pfx -name My_Organization

2. In the Firefox browser, navigate to Edit > Preferences > Advanced Tab.
3. Select View Certificates, and click the Your Certificates tab.
4. Click Import and select the .pfx file to load.

5. Enter the following URL in the address bar to browse the accessible paths for all the repositories and check their contents:

   https://satellite.example.com/pulp/content/

   Pulp uses the organization label, therefore, you must enter the organization label into the URL.

Procedure

1. In the Satellite web UI, navigate to Administer > Organizations.
2. From the list to the right of the name of the organization you want to delete, select Delete.
3. Click OK to delete the organization.

CLI procedure

1. Enter the following command to retrieve the ID of the organization that you want to delete:

   # hammer organization list

   From the output, note the ID of the organization that you want to delete.

2. Enter the following command to delete an organization:

   # hammer organization delete --id Organization_ID

Procedure

1. In the Satellite web UI, navigate to Administer > Locations.
2. Click New Location.
3. Optional: from the Parent list, select a parent location. This creates a location hierarchy.
4. In the Name field, enter a name for the location.
5. Optional: in the Description field, enter a description for the location.
6. Click Submit.
7. If you have hosts with no location assigned, add any hosts that you want to assign to the new location, then click Proceed to Edit.
8. Assign any infrastructure resources that you want to add to the location. This includes networking resources, installation media, kickstart templates, and other parameters. You can return to this page at any time by navigating to Administer > Locations and then selecting a location to edit.
9. Click Submit to save your changes.

Procedure

1. In the Satellite web UI, navigate to Administer > Locations.
2. Select Delete from the list to the right of the name of the location you want to delete.
3. Click OK to delete the location.

CLI procedure

1. Enter the following command to retrieve the ID of the location that you want to delete:

   # hammer location list

   From the output, note the ID of the location that you want to delete.

2. Enter the following command to delete the location:

   # hammer location delete --id Location ID

Procedure

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. In the Satellite web UI, navigate to Content > Subscriptions and click Manage Manifest.
3. In the Manage Manifest window, click Browse.
4. Navigate to the location that contains the Red Hat subscription manifest file, then click Open. If the Manage Manifest window does not close automatically, click Close to return to the Subscriptions window.

CLI procedure

1. Copy the Red Hat subscription manifest file from your client to Satellite Server:

   $ scp ~/manifest_file.zip root@satellite.example.com:~/.

2. Log in to Satellite Server as the root user and import the Red Hat subscription manifest file:

   # hammer subscription upload \
   --file ~/manifest_file.zip \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. In the Satellite web UI, navigate to Content > Subscriptions.
3. In the Subscriptions window, click the Search field to view the list of search criteria for building your search query.
4. Select search criteria to display further options.
5. When you have built your search query, click the search icon.

Procedure

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. In the Satellite web UI, navigate to Content > Subscriptions.
3. In the Subscriptions window, click Add Subscriptions.
4. On the row of each subscription you want to add, enter the quantity in the Quantity to Allocate column.
5. Click Submit

Procedure

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. In the Satellite web UI, navigate to Content > Subscriptions.
3. On the row of each subscription you want to remove, select the corresponding checkbox.
4. Click Delete, and then confirm deletion.

Procedure

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. In the Satellite web UI, navigate to Content > Subscriptions.
3. In the Subscriptions window, click Manage Manifest.
4. In the Manage Manifest window, click Refresh.

Procedure

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. In the Satellite web UI, navigate to Hosts > Content Hosts.
3. On the row of each content host whose subscription you want to change, select the corresponding checkbox.
4. From the Select Action list, select Manage Subscriptions.
5. Optionally, enter a key and value in the Search field to filter the subscriptions displayed.
6. Select the checkbox to the left of the subscriptions that you want to add or remove and click Add Selected or Remove Selected as required.
7. Click Done to save the changes.

CLI procedure

1. Connect to Satellite Server as the root user, and then list the available subscriptions:

   # hammer subscription list \
   --organization-id 1

2. Attach a subscription to the host:

   # hammer host subscription attach \
   --host host_name \
   --subscription-id subscription_id

Procedure

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. In the Satellite web UI, navigate to Hosts > Content Hosts.
3. On the row of each content host whose subscription you want to change, select the corresponding checkbox.
4. From the Select Action list, select Manage Subscriptions.
5. Optionally, enter a key and value in the Search field to filter the subscriptions displayed.
6. Select the checkbox to the left of the subscriptions to be added or removed and click Add Selected or Remove Selected as required.
7. Click Done to save the changes.

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. Select the Verify SSL checkbox if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.
10. 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.
11. Optional: In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.
12. 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.
13. From the Download Policy list, select the type of synchronization Satellite Server performs. For more information, see Section 6.7, “Download Policies Overview”.
14. From the Mirroring Policy list, select the type of content synchronization Satellite Server performs. For more information, see Section 6.10, “Mirroring Policies Overview”.
15. Optional: In the Retain package versions field, enter the number of versions you want to retain per package.
16. Optional: In the HTTP Proxy Policy field, select an HTTP proxy.
17. From the Checksum list, select the checksum type for the repository.
18. 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.
19. Optional: From the GPG Key list, select the GPG key for the product.
20. Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.
21. Optional: In the SSL Client cert field, select the SSL Client Certificate for the repository.
22. Optional: In the SSL Client Key field, select the SSL Client Key for the repository.
23. 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, for example,7Server and base architecture, for example, x86_64. For example:

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

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.

Procedure

1. In the Satellite web UI, click 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. 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 Infrastructure > HTTP Proxies and select New HTTP Proxy.
2. In the Name field, enter a name for the HTTP proxy.
3. In the URL field, enter the URL for the HTTP proxy, including the port number.
4. If your HTTP proxy requires authentication, enter a Username and Password.
5. 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.
6. Click the Locations tab and add a location.
7. Click the Organization tab and add an organization.
8. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Content > Products and select the checkbox next to each of 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 6.15, “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 6.15, “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 \
   --name "Red Hat Products 2" \
   --description "Example Plan for Red Hat Products" \
   --interval daily \
   --sync-date "2016-02-01 01:00:00" \
   --enabled true \
   --organization "My_Organization"

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

   # hammer sync-plan list --organization "Default 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 "Product_Name" \
   --sync-plan "Sync_Plan_Name" \
   --organization "My_Organization"

Procedure

1. Run the following Bash script:

   ORG="Your_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 client system:

   $ 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. Select the product that contains the repository sets that you want to restrict.
3. In the Repositories tab, click the repository that you want to restrict.
4. From the Restrict to OS list, select the operating system to include Red Hat Enterprise Linux operating systems for their corresponding Red Hat Enterprise Linux repositories.
5. Click Save to submit your change.

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle Environments.
2. Click New Environment Path to start a new application life cycle.
3. In the Name field, enter a name for your environment.
4. In the Description field, enter a description for your environment.
5. Click Save.
6. Optional: To add an environment to the environment path, click Add New Environment, complete the Name and Description fields, and select the prior environment from the Prior Environment list.

CLI procedure

1. To create an environment path, enter the hammer lifecycle-environment create command and specify the Library environment with the --prior option:

   # hammer lifecycle-environment create \
   --name "Environment Path Name" \
   --description "Environment Path Description" \
   --prior "Library" \
   --organization "My_Organization"

2. Optional: To add an environment to the environment path, enter the hammer lifecycle-environment create command and specify the parent environment with the --prior option:

   # hammer lifecycle-environment create \
   --name "Environment Name" \
   --description "Environment Description" \
   --prior "Prior Environment Name" \
   --organization "My_Organization"

3. To view the chain of the life cycle environment, enter the following command:

   # hammer lifecycle-environment paths --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Life Cycle Environments.
2. Click the name of the life cycle environment that you want to remove, and then click Remove Environment.
3. Click Remove to remove the environment.

CLI procedure

1. List the life cycle environments for your organization and note the name of the life cycle environment you want to remove:

   # hammer lifecycle-environment list \
   --organization "My_Organization"

2. Use the hammer lifecycle-environment delete command to remove an environment:

   # hammer lifecycle-environment delete \
   --name "My_Environment" \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Capsules, and select the Capsule that you want to remove a life cycle from.
2. Click Edit and click the Life Cycle Environments tab.
3. From the right menu, select the life cycle environments that you want to remove from Capsule, and then click Submit.
4. To synchronize Capsule’s content, click the Overview tab, and then click Synchronize.
5. Select either Optimized Sync or Complete Sync.

CLI procedure

1. Select Capsule Server that you want from the list and take note of its id:

   # hammer capsule list

2. To verify Capsule Server’s details, enter the following command:

   # hammer capsule info \
   --id Capsule_ID

3. Verify the list of life cycle environments currently attached to Capsule Server and take note of the Environment ID:

   # hammer capsule content lifecycle-environments \
   --id Capsule_ID

4. Remove the life cycle environment from Capsule Server:

   # hammer capsule content remove-lifecycle-environment \
   --id Capsule_ID
   --lifecycle-environment-id Lifecycle_Environment_ID

   Repeat this step for every life cycle environment that you want to remove from Capsule Server.

5. Synchronize the content from Satellite Server’s environment to Capsule Server:

   # hammer capsule content synchronize \
   --id Capsule_ID

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Capsules, and select the Capsule that you want to add a life cycle to.
2. Click Edit and click the Life Cycle Environments tab.
3. From the left menu, select the life cycle environments that you want to add to Capsule and click Submit.
4. To synchronize the content on the Capsule, click the Overview tab and click Synchronize.

5. Select either Optimized Sync or Complete Sync.

   For definitions of each synchronization type, see Recovering a Repository.

CLI procedure

1. To display a list of all Capsule Servers, on Satellite Server, enter the following command:

   # hammer capsule list

   Note the Capsule ID of the Capsule that you want to add a life cycle to.

2. Using the ID, verify the details of your Capsule:

   # hammer capsule info --id capsule_id

3. To view the life cycle environments available for your Capsule Server, enter the following command and note the ID and the organization name:

   # hammer capsule content available-lifecycle-environments --id capsule_id

4. Add the life cycle environment to your Capsule Server:

   # hammer capsule content add-lifecycle-environment \
   --id capsule_id --organization "My_Organization" \
   --lifecycle-environment-id lifecycle-environment_id

   Repeat for each life cycle environment you want to add to Capsule Server.

5. Synchronize the content from Satellite to Capsule.

   • To synchronize all content from your Satellite Server environment to Capsule Server, enter the following command:

     # hammer capsule content synchronize --id capsule_id

   • To synchronize a specific life cycle environment from your Satellite Server to Capsule Server, enter the following command:

     # hammer capsule content synchronize --id external_capsule_id \
     --lifecycle-environment-id lifecycle-environment_id

Procedure

1. In the Satellite web UI, navigate to Content > Content Views and click Create content view.
2. In the Name field, enter a name for the view. Satellite automatically completes the Label field from the name you enter.
3. In the Description field, enter a description of the view.
4. In the Type field, select a Content view or a Composite content view.
5. Optional: If you want to solve dependencies automatically every time you publish this Content View, select the Solve dependencies check box. Dependency solving slows the publishing time and might ignore any Content View filters you use. This can also cause errors when resolving dependencies for errata.
6. Optional: If you want to designate this Content View for importing from an upstream server, select the Import only check box. Import-only content views cannot be published directly.
7. Click Create content view.

Content View Steps

1. Click Create content view to create the Content View.
2. In the Repositories tab, select the repository from the Type list that you want to add to your Content View, select the checkbox next to the available repositories you want to add, then click Add repositories.
3. Click Publish new version and in the Description field, enter information about the version to log changes.
4. Optional: You can enable a promotion path by clicking Promote to Select a lifecycle environment from the available promotion paths to promote new version.
5. Click Next.
6. On the Review page, you can review the environments you are trying to publish.

7. Click Finish.

   Note

   Remove and Delete are similar but the Delete option deletes an entire Content View and the versions associated with that lifecycle environment. The Remove option allows you to choose which version you want removed from the lifecycle environment.

CLI procedure

1. Obtain a list of repository IDs:

   # hammer repository list --organization "My_Organization"

2. Create the Content View and add repositories:

   # hammer content-view create \
   --description "My_Content_View" \
   --name "My_Content_View" \
   --organization "My_Organization" \
   --repository-ids 1,2

   For the --repository-ids option, you can find the IDs in the output of the hammer repository list command.

3. Publish the view:

   # hammer content-view publish \
   --description "My_Content_View" \
   --name "My_Content_View" \
   --organization "My_Organization"

4. Optional: To add a repository to an existing Content View, enter the following command:

   # hammer content-view add-repository \
   --name "My_Content_View" \
   --organization "My_Organization" \
   --repository-id repository_ID

Procedure

1. In the Satellite web UI, navigate to a published version of a Content View > Module Streams to view the module streams that are available for the Content Types.
2. Use the Search field to search for specific modules.
3. To view the information about the module, click the module and its corresponding tabs to include Details, Repositories, Profiles, and Artifacts.

1. promote_or_remove_content_views
2. promote_or_remove_content_views_to_environment.

Procedure

1. In the Satellite web UI, navigate to Content > Content Views and select the Content View that you want to promote.
2. Select the version that you want to promote, click the vertical ellipsis icon, and click Promote.
3. Select the environment where you want to promote the Content View and click Promote.

Procedure

1. To promote a selected Content View version from Library across all life cycle environments within an organization, run the following Bash script:

   ORG="My_Organization"
   CVV_ID=3
   
   for i in $(hammer --no-headers --csv lifecycle-environment list --organization $ORG | awk -F, {'print $1'} | sort -n)
   do
      hammer content-view version promote --organization $ORG --to-lifecycle-environment-id $i --id $CVV_ID
   done

2. Display information about your Content View version to verify that it is promoted to the required lifecycle environments:

   # hammer content-view version info --id 3

Procedure

1. In the Satellite web UI, navigate to Content > Content Views and click Create content view.
2. In the Create content view window, enter a name for the view in the Name field. Red Hat Satellite automatically completes the Label field from the name you enter.
3. Optional: In the Description field, enter a description of the view.
4. On the Type tab, select Composite content view.
5. Optional: If you want to automatically publish a new version of the Composite Content View when a Content View is republished, select the Auto publish checkbox.
6. Click Create content view.
7. On the Content views tab, select the Content Views that you want to add to the Composite Content View, and then click Add content views.
8. In the Add content views window, select the version of each Content View.
9. Optional: If you want to automatically update the Content View to the latest version, select the Always update to latest version checkbox.
10. Click Add, then click Publish new version.
11. Optional: In the Description field, enter a description of the Content View.
12. In the Publish window, set the Promote switch, then select the lifecycle environment.
13. Click Next, then click Finish.

CLI procedure

1. Before you create the Composite Content Views, list the version IDs for your existing Content Views:

   # hammer content-view version list \
   --organization "My_Organization"

2. Create a new Composite Content View. When the --auto-publish option is set to yes, the Composite Content View is automatically republished when a Content View it includes is republished:

   # hammer content-view create \
   --composite \
   --auto-publish yes \
   --name "Example_Composite_Content_View" \
   --description "Example Composite Content View" \
   --organization "My_Organization"

3. Add a Content View to the Composite Content View. You can identify Content View, Content View version, and Organization in the commands by either their ID or their name. To add multiple Content Views to the Composite Content View, repeat this step for every Content View you want to include.

   • If you have the Always update to latest version option enabled for the Content View:

     # hammer content-view component add \
     --component-content-view-id Content_View_ID \
     --composite-content-view "Example_Composite_Content_View" \
     --latest \
     --organization "My_Organization"

   • If you have the Always update to latest version option disabled for the Content View:

     # hammer content-view component add \
     --component-content-view-id Content_View_ID \
     --composite-content-view "Example_Composite_Content_View" \
     --component-content-view-version-id Content_View_Version_ID \
     --organization "My_Organization"

4. Publish the Composite Content View:

   # hammer content-view publish \
   --name "Example_Composite_Content_View" \
   --description "Initial version of Composite Content View" \
   --organization "My_Organization"

5. Promote the Composite Content View across all environments:

   # hammer content-view version promote \
   --content-view "Example_Composite_Content_View" \
   --version 1 \
   --to-lifecycle-environment "Development" \
   --organization "My_Organization"
   # hammer content-view version promote \
   --content-view "Example_Composite_Content_View" \
   --version 1 \
   --to-lifecycle-environment "Testing" \
   --organization "My_Organization"
   # hammer content-view version promote \
   --content-view "Example_Composite_Content_View" \
   --version 1 \
   --to-lifecycle-environment "Production" \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Content Views.
2. From the list of content views, select the required Content View.
3. On the Details tab, toggle Solve dependencies.

Procedure

1. In the Satellite web UI, navigate to Content > Content Views and select a Content View.
2. On the Filters tab, click Create filter.
3. Enter a name.
4. From the Content type list, select a content type.
5. From the Inclusion Type list, select either Include filter or Exclude filter.
6. Optional: In the Description field, enter a description for the filter.
7. Click Create filter to create your content filter.
8. Depending on what you enter for Content Type, add rules to create the filter that you want.
9. Select if you want the filter to Apply to subset of repositories or Apply to all repositories.
10. Click Publish New Version to publish the filtered repository.
11. Optional: In the Description field, enter a description of the changes.

12. Click Create filter to publish a new version of the Content View.

    You can promote this Content View across all environments.

CLI procedure

1. Add a filter to the Content View. Use the --inclusion false option to set the filter to an Exclude filter:

   # hammer content-view filter create \
   --name "Errata Filter" \
   --type erratum --content-view "Example_Content_View" \
   --description "My latest filter" \
   --inclusion false \
   --organization "My_Organization"

2. Add a rule to the filter:

   # hammer content-view filter rule create \
   --content-view "Example_Content_View" \
   --content-view-filter "Errata Filter" \
   --start-date "YYYY-MM-DD" \
   --types enhancement,bugfix \
   --date-type updated \
   --organization "My_Organization"

3. Publish the Content View:

   # hammer content-view publish \
   --name "Example_Content_View" \
   --description "Adding errata filter" \
   --organization "My_Organization"

4. Promote the view across all environments:

   # hammer content-view version promote \
   --content-view "Example_Content_View" \
   --version 1 \
   --to-lifecycle-environment "Development" \
   --organization "My_Organization"
   # hammer content-view version promote \
   --content-view "Example_Content_View" \
   --version 1 \
   --to-lifecycle-environment "Testing" \
   --organization "My_Organization"
   # hammer content-view version promote \
   --content-view "Example_Content_View" \
   --version 1 \
   --to-lifecycle-environment "Production" \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Content Views.
2. Select the Content View.
3. On the Versions tab, select the version you want to delete and click on the vertical ellipsis on the right side of the version line.
4. Click Delete to open the deletion wizard that shows any affected environments.
5. Optional: If there are any affected environments, reassign any hosts or activation keys before deletion.
6. Click Next and review the details of the action.
7. Click Delete.

Connected Satellite Server

1. In the Satellite web UI, navigate to Content > Products.
2. Click on the custom product.
3. Click on the custom repository.
4. Copy the Published At: URL.
5. Continue with the procedure on disconnected Satellite Server.

Disconnected Satellite Server

1. Download the katello-server-ca.crt file from the connected Satellite Server:

   # curl http://satellite.example.com/pub/katello-server-ca.crt

2. Create an SSL Content Credential with the contents of katello-server-ca.crt. For more information on creating an SSL Content Credential, see Section 6.2, “Importing Custom SSL Certificates”.
3. In the Satellite web UI, navigate to Content > Products.

4. Create your custom product with the following:

   • Upstream URL: Paste the link that you copied earlier.
   • SSL CA Cert: Select the SSL certificate that was transferred from your connected Satellite Server.

   For more information on creating a custom product, see Section 6.3, “Creating a Custom Product”.

Export the Library Content of an Organization

1. Use the organization name or ID to export.

   # hammer content-export complete library --organization="My_Organization"

2. Verify that the archive containing the exported version of a Content View is located in the export directory:

   # ls -lh /var/lib/pulp/exports/My_Organization/Export-Library/1.0/2021-03-02T03-35-24-00-00
   total 68M
   -rw-r--r--. 1 pulp pulp 68M Mar  2 03:35 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335.tar.gz
   -rw-r--r--. 1 pulp pulp 333 Mar  2 03:35 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335-toc.json
   -rw-r--r--. 1 pulp pulp 443 Mar  2 03:35 metadata.json

   You need all three files, the tar.gz, the toc.json, and the metadata.json file to be able to import.

3. A new Content View Export-Library is created in the organization. This Content View contains all the repositories belonging to this organization. A new version of this Content View is published and exported automatically.

Procedure

1. Create an incremental export:

   # hammer content-export incremental library --organization="My_Organization"
   
   Generated /var/lib/pulp/exports/My_Organization/Export-Library/3.0/2021-03-02T04-22-14-00-00/metadata.json

2. Optional: View the exported data:

   # ls -lh /var/lib/pulp/exports/My_Organization/Export-Library/3.0/2021-03-02T04-22-14-00-00/
   total 172K
   -rw-r--r--. 1 pulp pulp 161K Mar  2 04:22 export-436882d8-de5a-48e9-a30a-17169318f908-20210302_0422.tar.gz
   -rw-r--r--. 1 pulp pulp  333 Mar  2 04:22 export-436882d8-de5a-48e9-a30a-17169318f908-20210302_0422-toc.json
   -rw-r--r--. 1 pulp pulp  492 Mar  2 04:22 metadata.json

To Export a Content View Version

1. List versions of the Content View that are available for export:

   # hammer content-view version list \
   --content-view="My_Content_View" \
   --organization="My_Organization"
   
   ---|----------|---------|-------------|-----------------------
   ID | NAME     | VERSION | DESCRIPTION | LIFECYCLE ENVIRONMENTS
   ---|----------|---------|-------------|-----------------------
   5  | view 3.0 | 3.0     |             | Library
   4  | view 2.0 | 2.0     |             |
   3  | view 1.0 | 1.0     |             |
   ---|----------|---------|-------------|----------------------

Export a Content View version

1. Get the version number of desired version. The following example targets version 1.0 for export.

   # hammer content-export complete version \
   --content-view="Content_View_Name" \
   --version=1.0 \
   --organization="My_Organization"

2. Verify that the archive containing the exported version of a Content View is located in the export directory:

   # ls -lh /var/lib/pulp/exports/My_Organization/Content_View_Name/1.0/2021-02-25T18-59-26-00-00/

Procedure

1. Create an incremental export:

   # hammer content-export incremental version \
   --content-view="Content_View_Name" \
   --organization="My_Organization" \
   --version=2.0

2. Optional: View the exported Content View:

   # ls -lh /var/lib/pulp/exports/My_Organization/view/2.0/2021-02-25T21-45-34-00-00/

Export a Repository

1. Use the repository name or ID to export.

   # hammer content-export complete repository \
    --organization="My_Organization" \
    --product="My_Product" \
    --name="My_Repository"

2. Optional: Verify that the exported archive is located in the export directory:

   # ls -lh /var/lib/pulp/exports/My_Organization/Export-My_Repository/1.0/2021-03-02T03-35-24-00-00
   total 68M
   -rw-r--r--. 1 pulp pulp 68M Mar  2 03:35 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335.tar.gz
   -rw-r--r--. 1 pulp pulp 333 Mar  2 03:35 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335-toc.json
   -rw-r--r--. 1 root root 443 Mar  2 03:35 metadata.json

1. Export content into archive chunks of a limited size, such as 2 GB:

   # hammer content-export complete repository \
   --chunk-size-gb=2 \
   --organization="My_Organization" \
   --product="My_Product" \
   --name="My_Repository"
   
   Generated /var/lib/pulp/exports/My_Organization/Export-My_Repository/1.0/2021-03-02T03-35-24-00-00/metadata.json

2. Optional: View the exported data:

   # ls -lh /var/lib/pulp/exports/My_Organization/Export-My_Repository/1.0/2021-03-02T03-35-24-00-00/

Procedure

1. Create an incremental export:

   # hammer content-export incremental repository \
    --organization="My_Organization" \
    --product="My_Product" \
    --name="My_Repository"
   
   Generated /var/lib/pulp/exports/My_Organization/Export-My_Repository/3.0/2021-03-02T03-35-24-00-00/metadata.json

2. Optional: View the exported data:

   # ls -lh /var/lib/pulp/exports/My_Organization/Export-My_Repository/3.0/2021-03-02T03-35-24-00-00/
   total 172K
   -rw-r--r--. 1 pulp pulp  20M Mar  2 04:22 export-436882d8-de5a-48e9-a30a-17169318f908-20210302_0422.tar.gz
   -rw-r--r--. 1 pulp pulp  333 Mar  2 04:22 export-436882d8-de5a-48e9-a30a-17169318f908-20210302_0422-toc.json
   -rw-r--r--. 1 root root  492 Mar  2 04:22 metadata.json

Procedure

1. Copy the exported files to a subdirectory of /var/lib/pulp/imports on Satellite Server where you want to import.

2. Set the ownership of the import directory and its contents to pulp:pulp.

   # chown -R pulp:pulp /var/lib/pulp/imports/2021-03-02T03-35-24-00-00
   # ls -lh /var/lib/pulp/imports/2021-03-02T03-35-24-00-00
   total 68M
   -rw-r--r--. 1 pulp pulp 68M Mar  2 04:29 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335.tar.gz
   -rw-r--r--. 1 pulp pulp 333 Mar  2 04:29 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335-toc.json
   -rw-r--r--. 1 pulp pulp 443 Mar  2 04:29 metadata.json

3. Identify the Organization that you wish to import into.

4. To import the Library content to Satellite Server, enter the following command:

   # hammer content-import library \
   --organization="My_Organization" \
   --path=/var/lib/pulp/imports/2021-03-02T03-35-24-00-00

   Note you must enter the full path /var/lib/pulp/imports/My_Exported_Library_Dir. Relative paths do not work.

5. To verify that you imported the Library content, check the contents of the Product and Repositories. A new Content View called Import-Library is created in the target organization. This Content View is used to facilitate the Library content import.

   By default, this Content View is not shown in the Satellite web UI. Import-Library is not meant to be assigned directly to hosts. Instead, assign your hosts to Default Organization View or another Content View as you would normally.

Procedure

1. Copy the exported files to a subdirectory of /var/lib/pulp/imports on Satellite Server where you want to import.

2. Set the ownership of the import directory and its contents to pulp:pulp.

   # chown -R pulp:pulp /var/lib/pulp/imports/2021-02-25T21-15-22-00-00/

3. Verify that the ownership is set correctly:

   # ls -lh /var/lib/pulp/imports/2021-02-25T21-15-22-00-00/

4. To import the Content View version to Satellite Server, enter the following command:

   # hammer content-import version \
   --organization-id=My_Organization_ID \
   --path=/var/lib/pulp/imports/2021-02-25T21-15-22-00-00/

   Note that you must enter the full path /var/lib/pulp/imports/My_Exported_Version_Dir. Relative paths do not work.

5. To verify that you imported the Content View version successfully, list Content View versions for your organization:

   # hammer content-view version list \
   --organization-id=My_Organization_ID

Procedure

1. Copy the exported files to a subdirectory of /var/lib/pulp/imports on Satellite Server where you want to import.

2. Set the ownership of the import directory and its contents to pulp:pulp.

   # chown -R pulp:pulp /var/lib/pulp/imports/2021-03-02T03-35-24-00-00
   # ls -lh /var/lib/pulp/imports/2021-03-02T03-35-24-00-00
   total 68M
   -rw-r--r--. 1 pulp pulp 68M Mar  2 04:29 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335.tar.gz
   -rw-r--r--. 1 pulp pulp 333 Mar  2 04:29 export-1e25417c-6d09-49d4-b9a5-23df4db3d52a-20210302_0335-toc.json
   -rw-r--r--. 1 pulp pulp 443 Mar  2 04:29 metadata.json

3. Identify the Organization that you wish to import into.

4. To import the Library content to Satellite Server, enter the following command:

   # hammer content-import repository \
   --organization="My_Organization" \
   --path=/var/lib/pulp/imports/2021-03-02T03-35-24-00-00

   Note that you must enter the full path /var/lib/pulp/imports/My_Exported_Repo_Dir. Relative paths do not work.

5. To verify that you imported the repository, check the contents of the Product and Repository.

1. Activation key that attaches subscriptions automatically.

   With no subscriptions specified and auto-attach enabled, hosts using the activation key search for the best fitting subscription from the ones provided by the Content View associated with the activation key. This is similar to entering the subscription-manager --auto-attach command. For Red Hat Enterprise Linux 8 hosts, you can configure the activation key to set system purpose on hosts during registration to enhance the automatic subscriptions attachment.

2. Activation key providing a custom set of subscription for auto-attach.

   If there are subscriptions specified and auto-attach is enabled, hosts using the activation key select the best fitting subscription from the list specified in the activation key. Setting system purpose on the activation key does not affect this scenario.

3. Activation key with the exact set of subscriptions.

   If there are subscriptions specified and auto-attach is disabled, hosts using the activation key are associated with all subscriptions specified in the activation key. Setting system purpose on the activation key does not affect this scenario.

Procedure

1. In the Satellite web UI, navigate to Content > Activation keys and click Create Activation Key.
2. In the Name field, enter the name of the activation key.
3. If you want to set a limit, clear the Unlimited hosts checkbox, and in the Limit field, enter the maximum number of systems you can register with the activation key. If you want unlimited hosts to register with the activation key, ensure the Unlimited Hosts checkbox is selected.
4. Optional: In the Description field, enter a description for the activation key.
5. From the Environment list, select the environment to use.
6. From the Content View list, select a Content View to use. If you intend to use the deprecated Katello Agent instead of Remote Execution, the Content View must contain the Satellite Client 6 repository because it contains the katello-agent package.

7. If Simple Content Access (SCA) is enabled:

   1. In the Repository Sets tab, ensure only your named repository is enabled.

8. If SCA is not enabled:

   1. Click the Subscriptions tab, then click the Add submenu.
   2. Click the checkbox under the subscription you created before.
   3. Click Add Selected.
9. Click Save.
10. Optional: For Red Hat Enterprise Linux 8 hosts, in the System Purpose section, you can configure the activation key with system purpose to set on hosts during registration to enhance subscriptions auto attachment.

CLI procedure

1. Create the activation key:

   # hammer activation-key create \
   --name "My_Activation_Key" \
   --unlimited-hosts \
   --description "Example Stack in the Development Environment" \
   --lifecycle-environment "Development" \
   --content-view "Stack" \
   --organization "My_Organization"

2. Optional: For Red Hat Enterprise Linux 8 hosts, enter the following command to configure the activation key with system purpose to set on hosts during registration to enhance subscriptions auto attachment.

   # hammer activation-key update \
   --organization "My_Organization" \
   --name "My_Activation_Key" \
   --service-level "Standard" \
   --purpose-usage "Development/Test" \
   --purpose-role "Red Hat Enterprise Linux Server" \
   --purpose-addons "addons"

3. Obtain a list of your subscription IDs:

   # hammer subscription list --organization "My_Organization"

4. Attach the Red Hat Enterprise Linux subscription UUID to the activation key:

   # hammer activation-key add-subscription \
   --name "My_Activation_Key" \
   --subscription-id My_Subscription_ID \
   --organization "My_Organization"

5. List the product content associated with the activation key:

   1. If Simple Content Access (SCA) is enabled:

      # hammer activation-key product-content \
      --content-access-mode-all true \
      --name "My_Activation_Key" \
      --organization "My_Organization"

   2. If SCA is not enabled:

      # hammer activation-key product-content \
      --name "My_Activation_Key" \
      --organization "My_Organization"

6. Override the default auto-enable status for the Satellite Client 6 repository. The default status is set to disabled. To enable, enter the following command:

   # hammer activation-key content-override \
   --name "My_Activation_Key" \
   --content-label rhel-7-server-satellite-client-6-rpms \
   --value 1 \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Activation keys and click the name of the activation key.
2. Click the Subscriptions tab.
3. To remove subscriptions, select List/Remove, and then select the checkboxes to the left of the subscriptions to be removed and then click Remove Selected.
4. To add subscriptions, select Add, and then select the checkboxes to the left of the subscriptions to be added and then click Add Selected.
5. Click the Repository Sets tab and review the repositories' status settings.
6. To enable or disable a repository, select the checkbox for a repository and then change the status using the Select Action list.
7. Click the Details tab, select a Content View for this activation key, and then click Save.

CLI procedure

1. List the subscriptions that the activation key currently contains:

   # hammer activation-key subscriptions \
   --name My_Activation_Key \
   --organization "My_Organization"

2. Remove the required subscription from the activation key:

   # hammer activation-key remove-subscription \
   --name "My_Activation_Key" \
   --subscription-id ff808181533518d50152354246e901aa \
   --organization "My_Organization"

   For the --subscription-id option, you can use either the UUID or the ID of the subscription.

3. Attach new subscription to the activation key:

   # hammer activation-key add-subscription \
   --name "My_Activation_Key" \
   --subscription-id ff808181533518d50152354246e901aa \
   --organization "My_Organization"

   For the --subscription-id option, you can use either the UUID or the ID of the subscription.

4. List the product content associated with the activation key:

   # hammer activation-key product-content \
   --name "My_Activation_Key" \
   --organization "My_Organization"

5. Override the default auto-enable status for the required repository:

   # hammer activation-key content-override \
   --name "My_Activation_Key" \
   --content-label content_label \
   --value 1 \
   --organization "My_Organization"

   For the --value option, enter 1 for enable, 0 for disable.

Procedure

1. In the Satellite web UI, navigate to Hosts > Register Host.
2. Click Generate to create the registration command.
3. Click on the files icon to copy the command to your clipboard.
4. Log in to the host you want register and run the previously generated command.
5. Check the /etc/yum.repos.d/redhat.repo file and ensure that the appropriate repositories have been enabled.

CLI procedure

1. Generate the host registration command using the Hammer CLI:

   # hammer host-registration generate-command \
   --activation-keys "My_Activation_Key"

   If your hosts do not trust the SSL certificate of Satellite Server, you can disable SSL validation by adding the --insecure flag to the registration command.

   # hammer host-registration generate-command \
   --activation-keys "My_Activation_Key" \
   --insecure true

2. Log in to the host you want register and run the previously generated command.
3. Check the /etc/yum.repos.d/redhat.repo file and ensure that the appropriate repositories have been enabled.

API procedure

1. Generate the host registration command using the Satellite API:

   # curl -X POST https://satellite.example.com/api/registration_commands \
   --user "My_User_Name" \
   -H 'Content-Type: application/json' \
   -d '{ "registration_command": { "activation_keys": ["My_Activation_Key_1, My_Activation_Key_2"] }}'

   If your hosts do not trust the SSL certificate of Satellite Server, you can disable SSL validation by adding the --insecure flag to the registration command.

   # curl -X POST https://satellite.example.com/api/registration_commands \
   --user "My_User_Name" \
   -H 'Content-Type: application/json' \
   -d '{ "registration_command": { "activation_keys": ["My_Activation_Key_1, My_Activation_Key_2"], "insecure": true }}'

   Use an activation key to simplify specifying the environments. For more information, see Managing Activation Keys in the Content Management guide.

   To enter a password as command line argument, use username:password syntax. Keep in mind this can save the password in the shell history.

   For more information about registration see Registering a Host to Red Hat Satellite in Managing Hosts.

2. Log in to the host you want register and run the previously generated command.
3. Check the /etc/yum.repos.d/redhat.repo file and ensure that the appropriate repositories have been enabled.

Procedure

1. In the Satellite web UI, navigate to Content > Activation Keys.
2. Click the activation key name that you want to edit.
3. Click the Subscriptions tab.
4. Click the edit icon next to Auto-Attach.
5. Select or clear the checkbox to enable or disable auto-attach.
6. Click Save.

Procedure

1. In the Satellite web UI, navigate to Content > Activation Keys.
2. Click the activation key name you want to edit.
3. Click the edit icon next to Service Level.
4. Select the required service level from the list. The list only contains service levels available to the activation key.
5. Click Save.

Procedure

1. In the Satellite web UI, navigate to Content > Errata to view the list of available errata.

2. Use the filtering tools at the top of the page to limit the number of displayed errata:

   • Select the repository to be inspected from the list. All Repositories is selected by default.
   • The Applicable checkbox is selected by default to view only applicable errata in the selected repository. Select the Installable checkbox to view only errata marked as installable.

   • To search the table of errata, type the query in the Search field in the form of:

     parameter operator value

     See Section 11.2, “Parameters Available for Errata Search” for the list of parameters available for search. Find the list of applicable operators in Supported Operators for Granular Search in Administering Red Hat Satellite. Automatic suggestion works as you type. You can also combine queries with the use of and and or operators. For example, to display only security advisories related to the kernel package, type:

     type = security and package_name = kernel

     Press Enter to start the search.

3. Click the Errata ID of the erratum you want to inspect:

   • The Details tab contains the description of the updated package as well as documentation of important fixes and enhancements provided by the update.
   • On the Content Hosts tab, you can apply the erratum to selected content hosts as described in Section 11.9, “Applying Errata to Multiple Hosts”.
   • The Repositories tab lists repositories that already contain the erratum. You can filter repositories by the environment and Content View, and search for them by the repository name.

1. In the Satellite web UI, navigate to Hosts > All Hosts and select the host you require.
2. If there are errata associated with the host, an Installable Errata card on the new Host page displays an interactive pie chart showing a breakdown of the security advisories, bugfixes, and enhancements.
3. On the new Host page, select the Content tab.
4. On the Content page select the Errata tab.
5. The page displays installable errata for the chosen host.
6. Click the checkbox for any errata you wish to install.
7. Using the vertical ellipsis icon next to the errata you want to add to the host, select Apply via Katello agent if you have no connectivity to the target host using SSH.
8. Select Apply via Remote Execution to use Remote Execution, or Apply via customized remote execution if you want to customize the remote execution.
9. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts and select the host you require.
2. If there are errata associated with the host, they are displayed in an Installable Errata card on the new Host page.
3. On the Content tab, Errata displays installable errata for the chosen host.
4. Click the checkbox for any errata you wish to install.
5. Using the vertical ellipsis icon next to the errata you want to add to the host, select Apply via Remote Execution to use Remote Execution. Select Apply via customized remote execution if you want to customize the remote execution, or select Apply via Katello agent if you have no connectivity to the target host using SSH.
6. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Content > Content Views and select a Content View that you want to use for applying errata.
2. Select Yum Content > Filters and click New Filter.
3. In the Name field, enter Errata Filter.
4. From the Content Type list, select Erratum – Date and Type.
5. From the Inclusion Type list, select Exclude.
6. In the Description field, enter Exclude errata items from YYYY-MM-DD.
7. Click Save.
8. For Errata Type, select the checkboxes of errata types you want to exclude. For example, select the Enhancement and Bugfix checkboxes and clear the Security checkbox to exclude enhancement and bugfix errata after certain date, but include all the security errata.

9. For Date Type, select one of two checkboxes:

   • Issued On for the issued date of the erratum.
   • Updated On for the date of the erratum’s last update.
10. Select the Start Date to exclude all errata on or after the selected date.
11. Leave the End Date field blank.
12. Click Save.
13. Click Publish New Version to publish the resulting repository.
14. Enter Adding errata filter in the Description field.

15. Click Save.

    When the Content View completes publication, notice the Content column reports a reduced number of packages and errata from the initial repository. This means the filter successfully excluded the all non-security errata from the last year.

16. Click the Versions tab.
17. Click Promote to the right of the published version.
18. Select the environments you want to promote the Content View version to.
19. In the Description field, enter the description for promoting.
20. Click Promote Version to promote this Content View version across the required environments.

CLI procedure

1. Create a filter for the errata:

   # hammer content-view filter create --name "Filter Name" \
   --description "Exclude errata items from the YYYY-MM-DD" \
   --content-view "CV Name" --organization "Default Organization" \
   --type "erratum"

2. Create a filter rule to exclude all errata on or after the Start Date that you want to set:

   # hammer content-view filter rule create --start-date "YYYY-MM-DD" \
   --content-view "CV Name" --content-view-filter="Filter Name" \
   --organization "Default Organization" --types=security,enhancement,bugfix

3. Publish the Content View:

   # hammer content-view publish --name "CV Name" \
   --organization "Default Organization"

4. Promote the Content View to the lifecycle environment so that the included errata are available to that lifecycle environment:

   # hammer content-view version promote \
   --content-view "CV Name" \
   --organization "Default Organization" \
   --to-lifecycle-environment "Lifecycle Environment Name"

Procedure

1. In the Satellite web UI, navigate to Content > Errata.
2. From the Errata list, click the name of the errata that you want to apply.
3. Select the content hosts that you want to apply the errata to, and click Apply to Hosts. This creates the incremental update to the Content View.
4. If you want to apply the errata to the content host, select the Apply Errata to Content Hosts immediately after publishing checkbox.
5. Click Confirm to apply the errata.

CLI procedure

1. List the errata and its corresponding IDs:

   # hammer erratum list

2. List the different content-view versions and the corresponding IDs:

   # hammer content-view version list

3. Apply a single erratum to content-view version. You can add more IDs in a comma-separated list.

   # hammer content-view version incremental-update \
   --content-view-version-id 319 --errata-ids 34068b

Procedure

1. In the Satellite web UI, navigate to Content > Errata.
2. Click the name of an erratum you want to apply.
3. Click to Content Hosts tab.
4. Select the hosts you want to apply errata to and click Apply to Hosts.
5. Click Confirm.

CLI procedure

1. List all installable errata:

   # hammer erratum list \
   --errata-restrict-installable true \
   --organization "Default Organization"

2. Apply one of the errata to multiple hosts:

   Using Remote Execution

   # hammer job-invocation create \
   --feature katello_errata_install \
   --inputs errata=ERRATUM_ID \
   --search-query "applicable_errata = ERRATUM_ID"

   Using Katello Agent (deprecated)

   Identify the erratum you want to use and list the hosts that this erratum is applicable to:

   # hammer host list \
   --search "applicable_errata = ERRATUM_ID" \
   --organization "Default Organization"

   The following Bash script applies an erratum to each host for which this erratum is available:

   for HOST in hammer --csv --csv-separator "|" host list --search "applicable_errata = ERRATUM_ID" --organization "Default Organization" | tail -n+2 | awk -F "|" '{ print $2 }' ;
   do
     echo "== Applying to $HOST ==" ; hammer host errata apply --host $HOST --errata-ids ERRATUM_ID1,ERRATUM_ID2 ;
   done

   This command identifies all hosts with erratum_IDs as an applicable erratum and then applies the erratum to each host.

3. To see if an erratum is applied successfully, find the corresponding task in the output of the following command:

   # hammer task list

4. View the state of a selected task:

   # hammer task progress --id task_ID

Procedure with repository discovery

1. In the Satellite web UI, navigate to Content > Products and click Repo Discovery.
2. From the Repository Type list, select Container Images.
3. In the Registry to Discover field, enter the URL of the registry to import images from.
4. In the Registry Username field, enter the name that corresponds with your user name for the container image registry.
5. In the Registry Password field, enter the password that corresponds with the user name that you enter.
6. In the Registry Search Parameter field, enter any search criteria that you want to use to filter your search, and then click Discover.
7. Optional: To further refine the Discovered Repository list, in the Filter field, enter any additional search criteria that you want to use.
8. From the Discovered Repository list, select any repositories that you want to import, and then click Create Selected.
9. Optional: To change the download policy for this container repository to on demand, see Section 6.9, “Changing the Download Policy for a Repository”.
10. Optional: If you want to create a product, from the Product list, select New Product.
11. In the Name field, enter a product name.
12. Optional: In the Repository Name and Repository Label columns, you can edit the repository names and labels.
13. Click Run Repository Creation.
14. When repository creation is complete, you can click each new repository to view more information.
15. Optional: To filter the content you import to a repository, click a repository, and then navigate to Limit Sync Tags. Click to edit, and add any tags that you want to limit the content that synchronizes to Satellite.
16. In the Satellite web UI, navigate to Content > Products and select the name of your product.
17. Select the new repositories and then click Sync Now to start the synchronization process.

Procedure with creating a repository manually

1. In the Satellite web UI, navigate to Content > Products. Click the name of the required product.
2. Click New repository.
3. From the Type list, select docker. Enter the details for the repository, and click Save.
4. Select the new repository, and click Sync Now.

CLI procedure

1. Create the custom Red Hat Container Catalog product:

   # hammer product create \
   --description "Red Hat Container Catalog content" \
   --name "Red Hat Container Catalog" \
   --organization "My_Organization" \
   --sync-plan "My_Sync_Plan"

2. Create the repository for the container images:

   # hammer repository create \
   --name "RHEL7" \
   --content-type "docker" \
   --url "http://registry.access.redhat.com/" \
   --docker-upstream-name "rhel7" \
   --product "Red Hat Container Catalog" \
   --organization "My_Organization"

3. Synchronize the repository:

   # hammer repository synchronize \
   --name "RHEL7" \
   --product "Red Hat Container Catalog" \
   --organization "My_Organization"

1. In the Satellite web UI, navigate to Content > Lifecycle Environments, and either create a lifecycle environment or select a lifecycle environment to edit.
2. In the Container Image Registry area, click the edit icon to the right of Registry Name Pattern area.
3. Use the list of variables and examples to determine which registry name pattern you require.

4. In the Registry Name Pattern field, enter the registry name pattern that you want to use. For example, to use the repository.docker_upstream_name:

   <%= repository.docker_upstream_name %>

5. Click Save.

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle Environments.
2. Select the lifecycle environment that you want to manage authentication for.
3. To permit unauthenticated access to the containers in this lifecycle environment, select the Unauthenticated Pull checkbox. To restrict unauthenticated access, clear the Unauthenticated Pull checkbox.
4. Click Save.

Procedure

1. In the Satellite web UI, navigate to Content > Red Hat Repositories.
2. In the Search field, enter an image name, for example, Red Hat Enterprise Linux 7 Server (ISOs).
3. In the Available Repositories window, expand Red Hat Enterprise Linux 7 Server (ISOs).
4. For the x86_64 7.2 entry, click the Enable icon to enable the repositories for the image.
5. In the Satellite web UI, navigate to Content > Products and click Red Hat Enterprise Linux Server.
6. Click the Repositories tab of the Red Hat Enterprise Linux Server window, and click Red Hat Enterprise Linux 7 Server ISOs x86_64 7.2.
7. In the upper right of the Red Hat Enterprise Linux 7 Server ISOs x86_64 7.2 window, click Select Action and select Sync Now.

CLI procedure

1. Locate the Red Hat Enterprise Linux Server product for file repositories:

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

2. Enable the file repository for Red Hat Enterprise Linux 7.2 Server ISO:

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

3. Locate the repository in the product:

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

4. Synchronize the repository in the product:

   # hammer repository synchronize \
   --name "Red Hat Enterprise Linux 7 Server ISOs x86_64 7.2" \
   --product "Red Hat Enterprise Linux Server" \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Products, and in the Products window, click Create Product.
2. In the Name field, enter a name to identify the product. This name populates the Label field.
3. Optional: In the GPG Key field, enter a GPG Key for the product.
4. Optional: From the Sync Plan list, select a synchronization plan for the product.
5. Optional: In the Description field, enter a description of the product.
6. Click Save.
7. In the Products window, click the new product and then click Create Repository.
8. In the Name field, enter a name for the repository. This automatically populates the Label field.
9. From the Type list, select file.
10. In the Upstream URL field, enter the URL of the registry to use as a source. Add a corresponding user name and password in the Upstream Username and Upstream Password fields.
11. Click Save.
12. Select the new repository.
13. Navigate to Upload File and click Browse.
14. Select the .iso file and click Upload.

CLI procedure

1. Create the custom product:

   # hammer product create \
   --name "My_ISOs" \
   --sync-plan "Example Plan" \
   --description "My_Product" \
   --organization "My_Organization"

2. Create the repository:

   # hammer repository create \
   --name "My_ISOs" \
   --content-type "file" \
   --product "My_Product" \
   --organization "My_Organization"

3. Upload the ISO file to the repository:

   # hammer repository upload-content \
   --path ~/bootdisk.iso \
   --id repo_ID \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select a product that you want to create a repository for.
3. On the Repositories tab, click New Repository.
4. In the Name field, enter a name for the repository. Satellite automatically completes the Label field based on the name.
5. Optional: In the Description field, enter a description for the repository.
6. From the Type list, select file as type of repository.
7. Optional: In the Upstream URL field, enter the URL of the upstream repository to use as a source.
8. Select the Verify SSL checkbox if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.
9. 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.
10. Optional: In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.
11. 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.
12. From the Mirroring Policy list, select the type of content synchronization Satellite Server performs. For more information, see Section 6.10, “Mirroring Policies Overview”.
13. Optional: In the HTTP Proxy Policy field, select or deselect using a HTTP proxy. By default, it uses the Global Default HTTP proxy.
14. 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.
15. Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.
16. Optional: In the SSL Client Cert field, select the SSL Client Certificate for the repository.
17. Optional: In the SSL Client Key field, select the SSL Client Key for the repository.
18. Click Save to create the repository.

CLI procedure

1. Create a custom product:

   # hammer product create \
   --description "My_Files" \
   --name "My_File_Product" \
   --organization "My_Organization" \
   --sync-plan "My_Sync_Plan"

   Table 14.1. Optional Parameters for the hammer product create Command

   Option	Description
   --gpg-key-id gpg_key_id	GPG key numeric identifier
   --sync-plan sync_plan_name	Sync plan name to search by
   --sync-plan-id sync_plan_id	Sync plan numeric identifier

2. Create a file type repository:

   # hammer repository create \
   --content-type "file" \
   --name "My_Files" \
   --organization "My_Organization" \
   --product "My_File_Product"

   Table 14.2. Optional Parameters for the hammer repository create Command

   Option	Description
   --checksum-type sha_version	Repository checksum, currently 'sha1' & 'sha256' are supported
   --download-policy policy_name	Download policy for yum repos (either 'immediate' or 'on_demand').
   --gpg-key gpg_key_name	Key name to search by
   --gpg-key-id gpg_key_id	GPG key numeric identifier
   --mirror-on-sync boolean	Must this repo be mirrored from the source, and stale RPMs removed, when synced? Set to true or false, yes or no, 1 or 0.
   --publish-via-http boolean	Must this also be published using HTTP? Set to true or false, yes or no, 1 or 0.
   --upstream-username repository_username	Upstream repository user, if required for authentication
   --upstream-password repository_password	Password for the upstream repository user
   --url source_repo_url	URL of the Source repository
   --verify-ssl-on-sync boolean	Must Katello verify that the upstream URL’s SSL certificates are signed by a trusted CA? Set to true or false, yes or no, 1 or 0.

1. Ensure the Utils repository is enabled.

   # subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms \
   --enable=rhel-8-for-x86_64-appstream-rpms \
   --enable=satellite-utils-6.11-for-rhel-8-x86_64-rpms

2. Install the Pulp Manifest package:

   # satellite-maintain packages install python38-pulp_manifest

   Note that this command stops the Satellite service and re-runs satellite-installer. Alternatively, to prevent downtime caused by stopping the service, you can use the following:

   # satellite-maintain packages unlock
   # yum install python38-pulp_manifest
   # satellite-maintain packages lock

3. Create a directory that you want to use as the file type repository in the HTTP server’s public folder, for example, /var/lib/pulp/sync_imports/new_repo

   # mkdir /var/lib/pulp/sync_imports/new_repo

4. Add files to the directory or create a test file:

   # touch my_file_repo/test.txt

5. Enter the Pulp Manifest command to create the manifest:

   # pulp-manifest my_file_repo

6. Verify the manifest was created:

   # ls my_file_repo
   PULP_MANIFEST test.txt

7. Configure additional import paths to sync a file repository that exists on the Satellite. For example, if a file repository is at /path/to/myrepo, enter:

   # satellite-installer --foreman-proxy-content-pulpcore-additional-import-paths /path/to/myrepo

1. Ensure a custom product exists in Satellite Server.
2. In the Satellite web UI, navigate to Content > Products.
3. Select the name of a product.
4. Click the Repositories tab and select New Repository.
5. In the Name field, enter a name for the repository. Satellite automatically completes this field based on what you enter for Name.
6. From the Type list, select the content type of the repository.
7. In the Upstream URL field, enter the local directory with the repository to use as the source, in the form file:///my_file_repo.
8. Select the Verify SSL checkbox to check the SSL certificate for the repository or clear the Verify SSL checkbox.
9. Optional: In the Upstream Username field, enter the upstream user name that you require.
10. Optional: In the Upstream Password field, enter the corresponding password for your upstream user name.
11. 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.
12. From the Mirroring Policy list, select the type of content synchronization Satellite Server performs. For more information, see Section 6.10, “Mirroring Policies Overview”.
13. Optional: In the HTTP Proxy Policy field, select the desired HTTP proxy. The default value is Global Default.
14. 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.
15. Optional: In the GPG Key field, select the GPG key for the repository.
16. Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.
17. Optional: In the SSL Client cert field, select the SSL Client Certificate for the repository.
18. Optional: In the SSL Client Key field, select the SSL Client Key for the repository.
19. Select Save to save this repository entry.

1. In the Satellite web UI, navigate to Content > Products.
2. Select the name of a product.
3. Select the name of the repository you want to update.
4. From the Select Action menu, select Sync Now.
5. Visit the URL where the repository is published to see the files.

1. On your machine, ensure that the correct repositories are enabled.

   • For Red Hat Enterprise Linux 8:

     # subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms \
     --enable=rhel-8-for-x86_64-appstream-rpms \
     --enable=satellite-utils-6.11-for-rhel-8-x86_64-rpms

   • For Red Hat Enterprise Linux 7:

     # subscription-manager repos --enable=rhel-7-server-rpms \
     --enable=rhel-7-server-satellite-utils-6.11-rpms

2. Install the Pulp Manifest package:

   • For Red Hat Enterprise Linux 8:

     # yum install python38-pulp_manifest

   • For Red Hat Enterprise Linux 7:

     # yum install tfm-pulpcore-python3-pulp_manifest

3. Create a directory that you want to use as the file type repository in the HTTP server’s public folder:

   # mkdir /var/www/html/pub/my_file_repo

4. Add files to the directory or create a test file:

   # touch /var/www/html/pub/my_file_repo/test.txt

5. Enter the Pulp Manifest command to create the manifest:

   # pulp-manifest /var/www/html/pub/my_file_repo

6. Verify the manifest was created:

   # ls /var/www/html/pub/my_file_repo
   PULP_MANIFEST test.txt

1. Ensure a custom product exists in Satellite Server, or create a custom product. For more information see Section 14.1, “Creating a Custom File Type Repository”
2. In the Satellite web UI, navigate to Content > Products.
3. Select the name of a product.
4. Click the Repositories tab and select New Repository.
5. In the Name field, enter a name for the repository. Red Hat Satellite automatically completes this field based on what you enter for Name.
6. From the Type list, select file.
7. In the Upstream URL field, enter the URL of the upstream repository to use as a source.
8. Select the Verify SSL checkbox if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.
9. 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.
10. Optional: In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.
11. 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.
12. From the Mirroring Policy list, select the type of content synchronization Satellite Server performs. For more information, see Section 6.10, “Mirroring Policies Overview”.
13. Optional: In the HTTP Proxy Policy field, select the desired HTTP proxy. The default value is Global Default.
14. 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.
15. Optional: In the GPG Key field, select the GPG key for the repository.
16. Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.
17. Optional: In the SSL Client cert field, select the SSL Client Certificate for the repository.
18. Optional: In the SSL Client Key field, select the SSL Client Key for the repository.
19. Click Save.
20. To update the file type repository, navigate to Content > Products. Select the name of a product that contains the repository that you want to update.
21. In the product’s window, select the name of the repository you want to update.
22. From the Select Action menu, select Sync Now.

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select a custom product by name.
3. Select a file type repository by name.
4. Click Browse to search and select the file you want to upload.
5. Click Upload to upload the selected file to Satellite Server.
6. Visit the URL where the repository is published to see the file.

Procedure

1. In the Satellite web UI, navigate to Content > Products.
2. Select a custom product by name.
3. Select a file type repository by name.
4. Ensure to select the Unprotected checkbox to access the repository published through HTTP.
5. Copy the URL where the repository is published.

CLI procedure

1. List the file type repositories.

   # hammer repository list --content-type file
   ---|------------|-------------------|--------------|----
   ID | NAME       | PRODUCT           | CONTENT TYPE | URL
   ---|------------|-------------------|--------------|----
   7  | My_Files   | My_File_Product   | file         |
   ---|------------|-------------------|--------------|----

2. Display the repository information.

   # hammer repository info \
   --name "My_Files" \
   --organization-id My_Organization_ID \
   --product "My_File_Product"

   If Unprotected is enabled, the output is similar to this:

   Publish Via HTTP: yes
   Published At:       https://satellite.example.com/pulp/content/My_Organization_Label/Library/custom/My_File_Product_Label/My_Files_Label/

   If Unprotected is not enabled, the output is similar to this:

   Publish Via HTTP: no
   Published At:       https://satellite.example.com/pulp/content/My_Organization_Label/Library/custom/My_File_Product_Label/My_Files_Label/

3. On the client, enter a command in the appropriate format for HTTP or HTTPS:

   For HTTP:

   # curl -O http://satellite.example.com/pulp/content/My_Organization_Label/Library/custom/My_File_Product_Label/My_Files_Label/my_file

   For HTTPS:

   # curl -O --cert ./_My-Organization-key-cert.pem_ --cacert katello-server-ca.crt https://satellite.example.com/pulp/content/My_Organization_Label/Library/custom/My_File_Product_Label/My_Files_Label/my_file