Content Management Guide

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.

For CLI Users

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

   # hammer organization create \
   --name "your_organization_name" \
   --label "your_organization_label \
   --description "your_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 "your_organization_name" \
   --compute-resource-ids 1

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 2.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 organization_label.pfx -name organization_name

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. In the address bar, enter a URL in the following format to browse for repositories:

   http://satellite.example.com/pulp/repos/organization_label

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

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.

For CLI Users

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

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.

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.

For CLI Users

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. Navigate to Content > Subscriptions and click Manage Manifest.
3. In the Manage Manifest window, click Browse.
4. Navigate to the location that contains the Subscription Manifest file, then click Open. If the Manage Manifest window does not close automatically, click Close to return to the Subscriptions window.

For CLI Users

1. Copy the 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 Subscription Manifest file:

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

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. 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.

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. 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.

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. Navigate to Content > Subscriptions.
3. On the row of each subscription you want to remove, select the corresponding check box.
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. Navigate to Content > Subscriptions.
3. In the Subscriptions window, click Manage Manifest.
4. In the Manage Manifest window, click Refresh.

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. Navigate to Hosts > Content Hosts.
3. On the row of each content host whose subscription you want to change, select the corresponding check box.
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 check box 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.

For CLI Users

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

1. In the Satellite web UI, ensure the context is set to the organization you want to use.
2. Navigate to Hosts > Content Hosts.
3. On the row of each content host whose subscription you want to change, select the corresponding check box.
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 check box 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.

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 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. Red Hat Satellite 6 automatically completes the Label field based on what you have entered for Name.
3. From the Type list, select the type of repository. You can select either a repository for RPM files (yum), Docker images (docker), Files (file) or other. Note that if the yum content type is selected, you can restrict whether the repository is available to a host based on the host’s architecture and OS version.
4. Optional: From the Restrict to Architecture list, select the architecture. Ensure that No restriction, which is the default value, is selected to make the repository available to all hosts regardless of the architecture.
5. Optional: From the Restrict to OS Version list, select the OS version. Ensure that No restriction, which is the default value, is selected to make the repository available to all hosts regardless of the OS version.
6. In the URL field, enter the URL of the external repository to use as a source.
7. From the Download Policy list, select the type of synchronization Satellite Server performs. See Section 5.3, “Download Policies Overview”
8. Ensure that the Mirror on Sync check box is selected. This ensures that the content that is no longer part of the upstream repository is removed during synchronization.
9. From the Checksum list, select the checksum type for the repository.
10. Optional: If you want, you can clear the Publish via HTTP check box to disable this repository from publishing through HTTP.
11. Optional: From the GPG Key list, select the GPG key for the product.
12. Click Save.

For CLI Users

1. List the repositories for an organization:

   # hammer repository create \
   --name "My_Repository" \
   --content-type "yum" \
   --os-version "My_OS_Version" \
   --arch "My_System_Architecture" \
   --publish-via-http true \
   --url http://yum.postgresql.org/9.5/redhat/rhel-7-x86_64/ \
   --gpg-key "My_Repository" \
   --product "My_Product" \
   --organization "My_Organization"

2. Change the download policy for a repository to one of immediate, on_demand, background:

   # hammer repository update \
   --organization-label organization-label  \
   --product "Red Hat Enterprise Linux Server" \
   --name "Red Hat Enterprise Linux 7 Server Kickstart x86_64 7.5"  \
   --download-policy immediate

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.

For CLI Users

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"

For Web UI Users

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.

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. From the Select Action menu, select Advanced Sync.
5. Select the option and click Sync.

For CLI users

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 --incremental true --id 1

   • For the complete synchronization:

     # hammer repository synchronize --skip-metadata-check true --id 1

   • For the validate content synchronization:

     # hammer repository synchronize --validate-contents true --id 1

Procedure

1. In the Satellite web UI, navigate to Content > Products and select the check box 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 5.12, “Adding a New 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 5.12, “Adding a New HTTP Proxy”.
5. Click Save.

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. The following host names are available:

   Host name	Port	Protocol
   subscription.rhsm.redhat.com	443	HTTPS
   subscription.rhn.redhat.com	443	HTTPS
   cdn.redhat.com	443	HTTPS
   api.access.redhat.com (if using Red Hat Insights)	443	HTTPS
   cert-api.access.redhat.com (if using Red Hat Insights)	443	HTTPS

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.

1. To control the number of synchronization jobs that run in parallel, configure the PULP_CONCURRENCY parameter in the /etc/default/pulp_workers file. For example, to set the number of jobs that run in parallel to 1, change PULP_CONCURRENCY to 1:

   PULP_CONCURRENCY=1

   By default, on a system with less than 8 CPUs, PULP_CONCURRENCY is set to the number of CPUs. On a system with more than 8 CPUs, it is set to 8.

2. To set the maximum network speed for synchronizing in bytes per second, configure the max_speed parameter. This parameter must be configured separately for each importer in the /etc/pulp/server/plugins.conf.d/ directory. For example, to set the maximum speed for synchronizing RPM content to 10 bytes per second, set the "max_speed" parameter in the /etc/pulp/server/plugins.conf.d/yum_importer.json file to 10:

   # cat /etc/pulp/server/plugins.conf.d/yum_importer.json
   {
       "proxy_host": null,
       "proxy_port": null,
       "proxy_username": null,
       "proxy_password": null,
       "max_speed": 10
   }

3. Verify the syntax of the file after editing:

   # json_verify < /etc/pulp/server/plugins.conf.d/yum_importer.json
   JSON is valid

4. Restart the satellite-maintain services to apply the changes:

   # satellite-maintain service restart

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. 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.
7. Click the Products tab, then click Add. Select the Red Hat Enterprise Linux Server product and click Add Selected.

For CLI Users

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. Assign the Red Hat Enterprise Linux Server product to it:

   # hammer product set-sync-plan \
   --name "Red Hat Enterprise Linux Server" \
   --sync-plan "Red Hat Products" \
   --organization "My_Organization"

3. View the available synchronization plans for an organization to verify that the synchronization plan is created:

   # hammer sync-plan list --organization "Default Organization"

1. Run the following Bash script:

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

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

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

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.

Prerequisites

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

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.

For CLI Users

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 gpg create \
   --key ~/RPM-GPG-KEY-EXAMPLE-95 \
   --name "My_Repository" \
   --organization "My_Organization"

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 Create Repository.
2. In the Name field, enter a name for the repository. Red Hat Satellite 6 automatically completes the Label field based on what you have entered for Name.
3. From the Type list, select the type of repository. You can select either a repository for RPM files (yum), Puppet modules (puppet), or Docker images (docker).
4. In the URL field, enter the URL of the external repository to use as a source.
5. From the Download Policy list, select the type of synchronization Satellite Server performs.
6. Ensure that the Mirror on Sync check box is selected. This ensures that the content that is no longer part of the upstream repository is removed during synchronization.
7. From the Checksum list, select the checksum type for the repository.
8. Optional: If you want, you can clear the Publish via HTTP check box to disable this repository from publishing through HTTP.
9. Optional: From the GPG Key list, select the GPG key for the product.
10. Click Save.

For CLI Users

1. Enter the following command to create the repository:

   # hammer repository create \
   --name "My_Repository" \
   --content-type "yum" \
   --publish-via-http true \
   --url http://yum.postgresql.org/9.5/redhat/rhel-7-x86_64/ \
   --gpg-key "My_Repository" \
   --product "My_Product" \
   --organization "My_Organization"

2. Synchronize the repository:

   # hammer repository synchronize \
   --name "My_Repository" \
   --product "My Product" \
   --organization "My_Organization"

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

For CLI Users

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"

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.

For CLI Users

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 "your_environment" \
   --organization "My_Organization"

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.

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

   # hammer capsule list

2. To verify the 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 the 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

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 Section 5.9, “Recovering a Repository”.

For CLI Users

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

1. In the Satellite web UI, navigate to Content > Content Views and click Create New 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. 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.
5. Click Save to create the Content View.
6. In the Repository Selection area, select the repositories that you want to add to your Content View, then click Add Repositories.
7. Click Publish New Version and in the Description field, enter information about the version to log changes.
8. Click Save.
9. Optional: to force metadata regeneration on Yum repositories, from the Actions list for your Content View versions, select Regenerate Repository Metadata.

Creating a Content View with Hammer CLI

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 \
   --name "Example_Content_View" \
   --description "Example Content View" \
   --repository-ids 1,2 \
   --organization "My_Organization"

   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 \
   --name "Example_Content_View" \
   --description "Example 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 "Example_Content_View" \
   --organization "My_Organization" \
   --repository-id repository_ID

1. In the Satellite web UI, navigate to Content > Content Views, and select the Content View that contains the modules you want to view.
2. Click the Versions tab and select the Content View version that you want to view.
3. Click the Module Streams tab to view the module streams that are available for the Content View.
4. Use the Filter field to refine the list of modules.
5. To view the information about the module, click the module.

1. In the Satellite web UI, navigate to Content > Content Views and click Create New View.
2. In the Name field, enter a name for the view. Red Hat Satellite 6 automatically completes the Label field from the name you enter.
3. In the Description field, enter a description of the view.
4. Click Save to complete.
5. In the Repository Selection area, select the repositories that you want to add to your Content View, then click Add Repositories.
6. Click the Puppet Modules tab, then click Add New Module.
7. Search for the module that you want to add and click Select a Version.
8. Navigate to the entry for Use Latest and click Select Version in the Actions column.
9. To publish, click the Versions tab and click Publish New Version. In the Description field, enter a description to log the changes and click Save.

1. promote_or_remove_content_views
2. promote_or_remove_content_views_to_environment.

1. In the Satellite web UI, navigate to Content > Content Views and select the Content View that you want to promote.
2. Click the Versions tab for the Content View.
3. Select the version that you want to promote and in the Actions column, click Promote.
4. Select the environment where you want to promote the Content View, and click Promote Version.
5. Click the Promote button again. This time select the Testing environment and click Promote Version.
6. Finally click on the Promote button again. Select the Production environment and click Promote Version.

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

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

1. In the Satellite web UI, navigate to Content > Content Views and click Create New View.
2. In the Name field, enter a name for the view. Red Hat Satellite 6 automatically completes the Label field from the name you enter.
3. In the Description field, enter a description of the view.
4. Select the Composite View? check box to create a Composite Content View.
5. Optional: select the Auto Publish check box if you want the Composite Content View to be republished automatically when a Content View is republished.
6. Click Save.
7. In the Add Content Views area, select the Content Views that you want to add to the Composite Content View, and then click Add Content Views.
8. Click Publish New Version to publish the Composite Content View. In the Description field, enter a description and click Save.
9. Click Promote and select the lifecycle environments to promote the Composite Content View to, enter a description, and then click Promote Version.

For CLI Users

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 component Content View to the Composite Content View. You must include the Content View Version ID and use the --latest option. To include multiple component Content Views to the Composite Content View, repeat this step for every Content View you want to include:

   # hammer content-view component add \
   --component-content-view-id Content_View_Version_ID \
   --latest \
   --composite-content-view "Example_Composite_Content_View"

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"

1. In the Satellite web UI, navigate to Administer > Settings and click the Content tab.
2. Locate the Content View Dependency Solving Default, and select Yes.

1. In the Satellite web UI, navigate to Administer > Settings and click the Content tab.

2. Locate the Content View Dependency Solving Algorithm and select one of the following options:

   • To add the package that resolves the dependency only if it does not exist in the repository, select Conservative.
   • To add the package that resolves the dependency regardless of whether or not it exists in the repository, select Greedy.

1. In the Satellite web UI, navigate to Content > Content Views and select a Content View.
2. Navigate to Yum Content > Filters and click New Filter.
3. In the Name field, enter a name for your filter.
4. From the Content Type list, select the content type that you want to filter. Depending on what you select for the new filter’s content type, different options appear.
5. From the Inclusion Type list, select either Include or Exclude.
6. In the Description field, enter a description for the filter, and click Save.
7. Depending on what you enter for Content Type, add rules to create the filter that you want.
8. Click the Affected repositories tab to select which specific repositories use this filter.
9. Click Publish New Version to publish the filtered repository. In the Description field, enter a description of the changes, and click Save.

For CLI Users

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"

To Export a Content View Version:

1. List Content Views to determine the ID of a Content View version you want to export:

   # hammer content-view version list \
   --organization "Default Organization"

2. Export the version of a Content View. Specify the directory where to store the export with the --export-dir option and the ID of the Content View version that you export with the --id option. The pulp_export_destination setting does not work for this procedure.

   # hammer content-view version export --export-dir export_directory \
   --id content_view_version_ID

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

   # ls export_directory
   export-1.tar

Procedure

1. Copy the archived file with the exported Content View version to the /var/lib/pulp/katello-export directory on the Satellite Server where you want to import.
2. On the Satellite Server where you want to import, create a Content View with the same name and label as the exported Content View. For more information, see Creating a Content View with Hammer CLI.
3. Ensure that you enable the repositories that the Products in the exported Content View version include. For more information, see Section 5.6, “Enabling Red Hat Repositories”.
4. In the Satellite web UI, navigate to Content > Products, click the Yum content tab and add the same Yum content that the exported Content View version includes.

5. Until BZ#1745081 is resolved, navigate to the /var/lib/pulp/katello-export directory:

   # cd /var/lib/pulp/katello-export

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

   # hammer content-view version import \
   --export-tar /var/lib/pulp/katello-export/exported_CV_archive.tar \
   --organization-id Your_Organization_ID

   Note that until BZ#1745081 is resolved, you must enter the full path /var/lib/pulp/katello-export/. Relative paths do not work.

7. To verify that you import the Content View version successfully, list Content Views for your organization:

   # hammer content-view version list --organization "Your_Organization"

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.

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 check box, 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 check box is selected.
4. 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 want to use this activation key to register hosts, the Content View must contain the Satellite Tools 6.9 repository because it is required to install the katello-agent.
7. Click Save.
8. 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.

For CLI Users

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 ff808181533518d50152354246e901aa \
   --organization "My_Organization"

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

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

6. Override the default auto-enable status for the Satellite Tools 6.9 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-tools-6.9-rpms \
   --value 1 \
   --organization "My_Organization"

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 check boxes to the left of the subscriptions to be removed and then click Remove Selected.
4. To add subscriptions, select Add, and then select the check boxes 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 check box 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.

For CLI Users

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.

1. Download the consumer RPM for your Satellite Server. This is located in the pub directory on the host’s web server. For example, for a Satellite Server with the host name satellite.example.com, enter the following command on the host to register:

   # rpm -Uvh http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm

   This RPM installs the necessary certificates for accessing repositories on Satellite Server and configures Red Hat Subscription Manager to use the server’s URL.

2. On the host, enter the following command to register the host to Satellite using the activation key:

   # subscription-manager register --activationkey="My_Activation_Key" \
   --org="My_Organization"

3. To view a list of hosts for an organization, on Satellite Server, enter the following command:

   # hammer host list --organization "My_Organization"

4. After registering a host to Satellite Server, install the katello-agent package on the host so that it can report back to Satellite Server:

   # yum install katello-agent

   The Satellite Tools 6.9 repository provides this package.

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 check box to enable or disable auto-attach.
6. Click Save.

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.

1. 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 check box is selected by default to view only errata applicable to the selected repository. Select the Installable check box 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 Table 11.1, “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.7, “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.

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. Navigate to 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 check boxes of errata types you want to exclude. For example, select the Enhancement and Bugfix check boxes and clear the Security check box to exclude enhancement and bugfix errata after certain date, but include all the security errata.

9. For Date Type, select one of two check boxes:

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

For CLI Users

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"

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 check box.

   Note

   Until BZ#1459807 is resolved, if you apply non-installable errata to hosts registered to Capsule Servers, do not select the Apply errata to Content Hosts immediately after publishing check box.

   Instead, after clicking Confirm, wait for the errata Content View to be promoted and for the Capsule synchronization task to finish. Then, the errata will be marked as Installable and you can use the procedure again to apply it.

5. Click Confirm to apply the errata.

For CLI Users

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

1. On Satellite, list all errata for the host:

   # hammer host errata list \
   --host client.example.com

2. Find the module stream an erratum belongs to:

   # hammer erratum info --id ERRATUM_ID

3. On the host, update the module stream:

   # yum update Module_Stream_Name

1. In the Satellite web UI, navigate to Hosts > Content Hosts and select the host you want to apply errata to.
2. Navigate to the Errata tab to see the list of errata.
3. Select the errata to apply and click Apply Selected. In the confirmation window, click Apply.
4. After the task to update all packages associated with the selected errata completes, click the Details tab to view the updated packages.

1. List all errata for the host:

   # hammer host errata list \
   --host client.example.com

2. Apply the most recent erratum to the host. Identify the erratum to apply using the erratum ID:

   # hammer host errata apply --host "Host Name" \
   --errata-ids ERRATUM_ID1,ERRATUM_ID2...

Procedure

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

1. List all installable errata:

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

2. Select 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"

3. Apply the errata to a single host:

   # hammer host errata apply \
   --host client.example.com \
   --organization "Default Organization" \
   --errata-ids ERRATUM_ID1,ERRATUM_ID2...

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

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

   # hammer task list

6. View the state of a selected task:

   # hammer task progress --id task_ID

1. In the Satellite web UI, navigate to Content > Red Hat Repositories.
2. From the list, select the OSTree content type.
3. In the Available Repositories pane, locate the OSTree repisotry set you want to use, for example, the Red Hat Enterprise Linux Atomic Host Trees set from the Red Hat Enterprise Linux Atomic Host product group.
4. Click the Enable icon to enable the repository you want to use.
5. Navigate to Content > Products and click the product that you want to use, for example Red Hat Enterprise Linux Atomic Host.

6. Select the upstream synchronization policy for this repository. By default, Satellite synchronizes only the latest OSTree branch.

   1. Click the repository you want to synchronize.

   2. From the Upstream Sync Policy menu, select one of the following policies to synchronize OSTree branches for this repository:

      • Latest Only - synchronize only the latest OSTree branch.
      • All History - synchronize all OSTree branches.
      • Custom - synchronize a custom number of OSTree branches. Enter the required number into the field below.
   3. Click Save.
7. From the Select Action menu, select Sync Now.

For CLI Users

1. Search the Red Hat Enterprise Linux Server product for ostree repositories:

   # hammer repository-set list \
   --product "Red Hat Enterprise Linux Atomic Host" \
   --organization "My_Organization" | grep "ostree"

2. Enable the ostree repository for Red Hat Enterprise Linux Atomic Host or any product that you want to use:

   # hammer repository-set enable \
   --product "Red Hat Enterprise Linux Atomic Host" \
   --name "Red Hat Enterprise Linux Atomic Host (Trees)" \
   --organization "My_Organization"

3. Locate and synchronize the repository for the product:

   # hammer repository list \
   --product "Red Hat Enterprise Linux Atomic Host" \
   --organization "My_Organization"
   # hammer repository synchronize \
   --name "Red Hat Enterprise Linux Atomic Host Trees" \
   --product "Red Hat Enterprise Linux Atomic Host" \
   --organization "My_Organization"

1. In the Satellite web UI, navigate to Content > Products and click Create Product.
2. In the Name field, enter a name for your OSTree content. This automatically populates the Label field.
3. Optional: In the GPG Key field, enter a GPG Key for the entire product.
4. From the Sync Plan menu, select a synchronization plan to associate with the product.
5. In the Description field, enter a description of the product and click Save.
6. When the product creation completes, click Create Repository.
7. In the Name field, enter a name for the repository. This automatically populates the Label field.
8. From the Type list, select ostree.
9. In the URL field, enter the URL of the registry to use as a source. For example http://www.example.com/rpm-ostree/.

10. From the Upstream Sync Policy menu, select one of the following policies to synchronize OSTree branches for this repository:

    • Latest Only - synchronize only the latest OSTree branch.
    • All History - synchronize all OSTree branches.
    • Custom - synchronize a custom number of OSTree branches. Enter the required number into the field below.
11. Click Save.
12. When the repository creation completes, select the new repository and click Sync Now to start the synchronization process.

For CLI Users

1. Create a product for your custom OSTree content:

   # hammer product create \
   --name "Custom OSTree Content" \
   --sync-plan "Example_Plan" \
   --description "OSTree Content" \
   --organization "My_Organization"

2. Create the repository for the OSTree:

   # hammer repository create \
   --name "OSTree" \
   --content-type "ostree" \
   --url "http://www.example.com/rpm-ostree/" \
   --product "OSTree Content" \
   --organization "My_Organization"

3. Synchronize the repository:

   # hammer repository synchronize \
   --name "OSTree" \
   --product "OSTree Content" \
   --organization "My_Organization"

1. In the Satellite web UI, navigate to Content > Content Views and click Create New View.
2. In the Name field, enter a plain text name for the view. This automatically populates the Label field.
3. In the Description field, enter a description of the OSTree Content View.
4. If you want to use a Composite Content View, select the Composite View check box.
5. Click Save to complete.
6. Navigate to the OSTree Content tab, then click Add.
7. Select the OSTree repository for that you want to use. Click Add Repository to add the OSTree content from this repository to the Content View.
8. Navigate to Versions and click Publish New Version.
9. In the Description field, enter a description for the version, and click Save.

For CLI Users

1. Obtain a list of repository IDs:

   # hammer repository list --organization "_My_Organization_"

2. Create the Content View and add the repository:

   # hammer content-view create \
   --name "OSTree" \
   --description "OSTree for Red Hat Enterprise Linux Atomic Host" \
   --repository-ids 5 \
   --organization "My_Organization"

3. Publish the view:

   # hammer content-view publish \
   --name "OSTree" \
   --description "Example Content View for the OSTree" \
   --organization "My_Organization"

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: If you want to create a product, from the Product list, select New Product.
10. In the Name field, enter a product name.
11. Optional: In the Repository Name and Repository Label columns, you can edit the repository names and labels.
12. Click Run Repository Creation.
13. When repository creation is complete, you can click each new repository to view more information.
14. 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.
15. Navigate to Content > Products and select the name of your product.
16. Select the new repositories and then click Sync Now to start the synchronization process.

For CLI Users

1. Create the custom Red Hat Container Catalog product:

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

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.

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

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

For CLI Users

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 and synchronize the repository in the product:

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

1. Create a custom product.
2. Add a repository for files to the product.
3. Upload a file to the repository.

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. In the GPG Key field, enter a GPG Key for the product.
4. From the Sync Plan list, select a synchronization plan for the product.
5. 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. Click the new repository.
13. Navigate to the Upload File and click Browse.
14. Select the .iso file and click Upload.

For CLI Users

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"

1. In the Satellite web UI, navigate to Content > Products, click Create Product and enter the following details:
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 Sync Plan list, select a synchronization plan for the product.
5. In the Description field, enter a description of the product, and then click Save.

1. In the Products window, select the name of a product that you want to create a repository for.
2. Click the Repositories tab, and then click New Repository.
3. In the Name field, enter a name for the repository. Satellite automatically completes the Label field based on the name.
4. From the Type list, select file.
5. In the Upstream URL field, enter the URL of the upstream repository to use as a source.
6. Select the Verify SSL check box if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.
7. 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.
8. In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.
9. Click Save.

For CLI Users

1. Create a custom product

   # hammer product create \
   --name "My File Product" \
   --sync-plan "Example Plan" \
   --description "My files" \
   --organization "My_Organization"

   Table 15.1. Optional Parameters for the hammer product create Command

   Option	Description
   --gpg-key gpg_key_name	Key name to search by
   --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 \
   --name "My Files" \
   --content-type "file" \
   --product "My File Product" \
   --organization "My_Organization"

   Table 15.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', 'on_demand', or 'background').
   --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 Server and Satellite Tools 6.9 repositories are enabled.

2. Install the Pulp Manifest package:

   # satellite-maintain packages install python-pulp-manifest

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

   # mkdir my_file_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

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 check box to check the SSL certificate for the repository or clear the Verify SSL check box.
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. 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 remote server, ensure that the Server and Satellite Tools 6.9 repositories are enabled.

2. Install the Pulp Manifest package:

   # yum install python-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 15.1, “Creating a Custom File Type Repository in Red Hat Satellite”
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 6 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 check box if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.
9. 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. In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.
11. Click Save.
12. 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.
13. In the product’s window, select the name of the repository you want to update.
14. From the Select Action menu, select Sync Now.

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.

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. Check to see if Publish via HTTP is enabled. If it is not, you require the certificates to use HTTPS.
5. Copy the URL where the repository is published.

For CLI Users

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" --product "My File Product" --organization-id 1

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

   Publish Via HTTP:   yes
   Published At:       http://satellite.example.com/pulp/isos/uuid/

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

   Publish Via HTTP:   no
   Published At:       https://satellite.example.com/pulp/isos/uuid/

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

   For HTTP:

   # curl -O satellite.example.com/pulp/isos/uuid/my_file

   For HTTPS:

   # curl -O --cert ./Default\ Organization-key-cert.pem --cacert katello-server-ca.crt satellite.example.com/pulp/isos/uuid/my_file

Procedure

1. In the Satellite web UI, navigate to Content > Products, and click the product that you want to use.
2. Click Create Repository.
3. In the Name field, enter a name for the repository. Red Hat Satellite 6 automatically completes the Label field based on what you have entered for Name.
4. From the Type list, select puppet.
5. In the URL field, enter the URL of the external repository to use as a source. You can use a repository source to synchronize your own Puppet modules.
6. Click Save.

For CLI Users

1. Enter the following command to create a Puppet module repository:

   # hammer repository create \
   --name "PostgreSQL Puppet Modules" \
   --content-type "puppet" \
   --product "PostgreSQL" \
   --organization "My_Organization"

Prerequisites

1. From the Puppet Forge website, download the module that you want to use, for example, https://forge.puppetlabs.com/puppetlabs/postgresql.
2. In your web browser, click download latest tar.gz to save to your local file system.

Procedure

1. In the Satellite web UI, navigate to Content > Products and select the product that contains the Puppet repository that you want to manage.
2. In the repository window, click the new Puppet repository, which displays the details page for that repository.
3. Navigate to the Upload Puppet Module area, click Browse, select the newly downloaded and extracted Puppet module, and click Upload.

1. In the window for your Puppet Modules repository, navigate to the upper right of the window to the Content Counts area. In the Puppet Modules row, click the numerical value that is displayed for the Puppet Modules.
2. In the Manage Puppet Modules for your Puppet Module repository window, select the modules that you want to manage and then click Select Action and perform an action, or select Remove Puppet Modules.

For CLI Users

1. Copy the Puppet module to your Satellite Server’s file system:

   $ scp ~/puppet_module.tar.gz root@satellite.example.com:~/.

2. Import the Puppet module to the Puppet Modules repository:

   # hammer repository upload-content \
   --path ~/puppet_module.tar.gz \
   --id repo_ID \
   --organization "My_Organization"

Procedure

1. In the Satellite web UI, navigate to Content > Products and 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 Sync Plan list, select a synchronization plan for the product.
5. In the Description field, enter a description of the product.
6. Click Save.
7. Click Create Repository, which displays a form for a new repository.
8. In the Name field, enter a name for the repository. Red Hat Satellite 6 automatically completes this field based on what you have entered for Name.
9. From the Type list, select puppet.
10. In the URL field, enter http://forge.puppetlabs.com/.
11. Click Save.
12. Select the new Puppet repository and click Sync Now to import all modules from Puppet Forge into Satellite Server. This can take a long time.

For CLI Users

1. Create the product:

   # hammer product create \
   --name "Puppet Forge" \
   --sync-plan "Example Plan" \
   --description "All modules from Puppet Forge" \
   --organization "My_Organization"

2. Create the Puppet Forge repository:

   # hammer repository create \
   --name "Puppet Forge Modules" \
   --content-type "puppet" \
   --product "Puppet Forge" \
   --organization "My_Organization" \
   --url http://forge.puppetlabs.com/

3. Synchronize the repository:

   # hammer repository synchronize \
   --name "Puppet Forge Modules" \
   --product "Puppet Forge" \
   --organization "My_Organization"

Procedure

1. Create a custom product and click Create Repository.
2. From the Type list, select puppet.
3. In the URL field, enter the URL of the external Git repository to use as a source in the following format: file:///modules.

For CLI Users

1. Create the Puppet Forge repository:

   # hammer repository create \
   --name "Modules from Git" \
   --content-type "puppet" \
   --product "MyProduct" \
   --organization "My_Organization" \
   --url file:///modules