Content Management Guide

In the Foreman web UI, navigate to Administer > Organizations.

Click New Organization.

In the Name field, enter a name for the organization.

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.

Optional: in the Description field, enter a description for the organization.

Click Submit.

If you have hosts with no organization assigned, select the hosts that you want to add to the organization, then click Proceed to Edit.

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.

Click Submit.

To create an organization, enter the following command:

# hammer organization create \
--name "your_organization_name" \
--label "your_organization_label \
--description "your_organization_description"

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

In the Foreman web UI, navigate to Administer > Organizations.

Select an organization that you want to generate a debug certificate for.

Click Generate and Download.

Save the certificate file in a secure location.

Create and download an organization certificate as described in Creating an Organization Debug Certificate.

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

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

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

Copy the contents of the file from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE-----, into a cert.pem file.

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

In the Firefox browser, navigate to Edit > Preferences > Advanced Tab.

Select View Certificates, and click the Your Certificates tab.

Click Import and select the .pfx file to load.

In the address bar, enter a URL in the following format to browse for repositories:

http://foreman.example.com/pulp/content

In the Foreman web UI, navigate to Administer > Organizations.

From the list to the right of the name of the organization you want to delete, select Delete.

Click OK to delete the organization.

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

# hammer organization list

Enter the following command to delete an organization:

# hammer organization delete --id Organization_ID

In the Foreman web UI, navigate to Administer > Locations.

Click New Location.

Optional: from the Parent list, select a parent location. This creates a location hierarchy.

In the Name field, enter a name for the location.

Optional: in the Description field, enter a description for the location.

Click Submit.

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.

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.

Click Submit to save your changes.

In the Foreman web UI, navigate to Administer > Locations.

Select Delete from the list to the right of the name of the location you want to delete.

Click OK to delete the location.

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

# hammer location list

Enter the following command to delete the location:

# hammer location delete --id Location ID

In the Foreman web UI, ensure the context is set to the organization you want to use.

Navigate to Content > Subscriptions and click Manage Manifest.

In the Manage Manifest window, click Browse.

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.

Copy the Subscription Manifest file from your client to Foreman server:

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

Log in to Foreman server as the root user and import the Subscription Manifest file:

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

In the Foreman web UI, ensure the context is set to the organization you want to use.

Navigate to Content > Subscriptions.

In the Subscriptions window, click the Search field to view the list of search criteria for building your search query.

Select search criteria to display further options.

When you have built your search query, click the search icon.

In the Foreman web UI, ensure the context is set to the organization you want to use.

Navigate to Content > Subscriptions.

In the Subscriptions window, click Add Subscriptions.

On the row of each subscription you want to add, enter the quantity in the Quantity to Allocate column.

Click Submit.

In the Foreman web UI, ensure the context is set to the organization you want to use.

Navigate to Content > Subscriptions.

On the row of each subscription you want to remove, select the corresponding check box.

Click Delete, and then confirm deletion.

In the Foreman web UI, ensure the context is set to the organization you want to use.

Navigate to Content > Subscriptions.

In the Subscriptions window, click Manage Manifest.

In the Manage Manifest window, click Refresh.

In the Foreman web UI, ensure the context is set to the organization you want to use.

Navigate to Hosts > Content Hosts.

On the row of each content host whose subscription you want to change, select the corresponding check box.

From the Select Action list, select Manage Subscriptions.

Optionally, enter a key and value in the Search field to filter the subscriptions displayed.

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.

Click Done to save the changes.

Connect to Foreman server as the root user, and then list the available subscriptions:

# hammer subscription list \
--organization-id 1

Attach a subscription to the host:

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

In the Foreman web UI, ensure the context is set to the organization you want to use.

Navigate to Hosts > Content Hosts.

On the row of each content host whose subscription you want to change, select the corresponding check box.

From the Select Action list, select Manage Subscriptions.

Optionally, enter a key and value in the Search field to filter the subscriptions displayed.

Select the check box to the left of the subscriptions to be added or removed and click Add Selected or Remove Selected as required.

Click Done to save the changes.

In the Foreman web UI, navigate to Content > Content Credentials. In the Content Credentials window, click Create Content Credential.

In the Name field, enter a name for your SSL certificate.

From the Type list, select SSL Certificate.

In the Content Credentials Content field, paste your SSL certificate, or click Browse to upload your SSL certificate.

Click Save.

In the Foreman web UI, navigate to Content > Products, click Create Product.

In the Name field, enter a name for the product. Foreman automatically completes the Label field based on what you have entered for Name.

Optional: From the GPG Key list, select the GPG key for the product.

Optional: From the SSL CA Cert list, select the SSL CA certificate for the product.

Optional: From the SSL Client Cert list, select the SSL client certificate for the product.

Optional: From the SSL Client Key list, select the SSL client key for the product.

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.

In the Description field, enter a description of the product.

Click Save.

In the Foreman web UI, navigate to Content > Products and select the product that you want to use, and then click New Repository.

In the Name field, enter a name for the repository. Foreman automatically completes the Label field based on what you have entered for Name.

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.

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.

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.

In the URL field, enter the URL of the external repository to use as a source. Foreman 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.

From the Download Policy list, select the type of synchronization Foreman server performs. See Download Policies Overview

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.

From the Checksum list, select the checksum type for the repository.

Optional: If you want, you can clear the Publish via HTTP check box to disable this repository from publishing through HTTP.

Optional: From the GPG Key list, select the GPG key for the product.

Click Save.

Enter the following command to create the repository:

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

In the Foreman web UI, navigate to Content > Red Hat Repositories.

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.

In the Available Repositories pane, click a repository to expand the repository set.

Click the Enable icon next to the base architecture and release version that you want.

To search for your product, enter the following command:

# hammer product list --organization "My_Organization"

List the repository set for the product:

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

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"

In the Foreman web UI, navigate to Content > Products and select the product that contains the repositories that you want to synchronize.

Select the repositories that you want to synchronize and click Sync Now.

In the Foreman web UI, navigate to Administer > Settings.

Click the Content tab.

Change the default download policy depending on your requirements:

In the web UI, navigate to Content > Products, and click the required product name.

On the Repositories tab, click the required repository name, locate the Download Policy field, and click the edit icon.

From the list, select the required download policy and then click Save.

List the repositories for an organization:

# hammer repository list \
--organization-label organization-label

Change the download policy for a repository to one of immediate or on_demand:

# 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

In the Foreman web UI, click Content > Products.

Click the name of the product.

In the Repositories tab, click the name of the RPM repository.

Under Upload Package, click Browse…​ and select the RPM you want to upload.

Click Upload.

In the Foreman web UI, navigate to Content > Products.

Select the product containing the corrupted repository.

Select the name of a repository you want to synchronize.

To perform optimized sync or complete sync, select Advanced Sync from the Select Action menu.

Select the required option and click Sync.

To verify the checksum, click Verify Content Checksum from the Select Action menu. (optional)

Obtain a list of repository IDs:

# hammer repository list --organization "My_Organization"

Synchronize a corrupted repository using the necessary option:

In the Foreman web UI, navigate to Infrastructure > HTTP Proxies and select New HTTP Proxy.

In the Name field, enter a name for the HTTP proxy.

In the URL field, enter the URL for the HTTP proxy, including the port number. The following host names are available:

If your HTTP proxy requires authentication, enter a Username and Password.

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

Click the Locations tab and add a location.

Click the Organization tab and add an organization.

Click Submit.

In the Foreman web UI, navigate to Content > Products and select the check box next to each of the Products that you want to change.

From the Select Action list, select Manage HTTP Proxy.

Select an HTTP Proxy Policy from the list:

Click Update.

In the Foreman web UI, navigate to Content > Products and click the name of the Product that contains the repository.

In the Repositories tab, click the name of the repository.

Locate the HTTP Proxy field and click the edit icon.

Select an HTTP Proxy Policy from the list:

Click Save.

In the Foreman web UI, navigate to Content > Sync Plans and click New Sync Plan.

In the Name field, enter a name for the plan.

In the Description field, enter a description of the plan.

From the Interval list, select the interval at which you want the plan to run.

From the Start Date and Start Time lists, select when to start running the synchronization plan.

Click Save.

Click the Products tab, then click Add. Select the Red Hat Enterprise Linux Server product and click Add Selected.

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"

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"

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

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

Run the following Bash script:

ORG="My_Organization"
SYNC_PLAN="daily_sync_at_3_a.m"

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

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

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

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

Extract the RPM file without installing it:

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

In the Foreman web UI, navigate to Content > Content Credentials and in the upper-right of the window, click Create Content Credential.

Enter the name of your repository and select GPG Key from the Type list.

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.

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

Click Save.

Copy the GPG key to your Foreman server:

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

Upload the GPG key to Foreman:

# hammer gpg create \
--key ~/RPM-GPG-KEY-EXAMPLE-95 \
--name "My_Repository" \
--organization "My_Organization"

In the Foreman web UI, navigate to Content > Lifecycle Environments.

Click New Environment Path to start a new application life cycle.

In the Name field, enter a name for your environment.

In the Description field, enter a description for your environment.

Click Save.

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.

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"

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"

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

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

In the Foreman web UI, navigate to Content > Life Cycle Environments.

Click the name of the life cycle environment that you want to remove, and then click Remove Environment.

Click Remove to remove the environment.

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"

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

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

In the Foreman web UI, navigate to Infrastructure > Smart Proxies, and select the Smart Proxy that you want to remove a life cycle from.

Click Edit and click the Life Cycle Environments tab.

From the right menu, select the life cycle environments that you want to remove from Smart Proxy, and then click Submit.

To synchronize Smart Proxy’s content, click the Overview tab, and then click Synchronize.

Select either Optimized Sync or Complete Sync.

Select Smart Proxy server that you want from the list and take note of its id:

# hammer capsule list

To verify Smart Proxy server’s details, enter the following command:

# hammer capsule info --id capsule_id

Verify the list of life cycle environments currently attached to Smart Proxy server and take note of the environment id:

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

Remove the life cycle environment from Smart Proxy server:

# hammer capsule content remove-lifecycle-environment \
--id capsule_id \
--lifecycle-environment-id lifecycle_environment_id

Synchronize the content from Foreman server’s environment to Smart Proxy server:

# hammer capsule content synchronize \
--id capsule_id

In the Foreman web UI, navigate to Infrastructure > Smart Proxies, and select the Smart Proxy that you want to add a life cycle to.

Click Edit and click the Life Cycle Environments tab.

From the left menu, select the life cycle environments that you want to add to Smart Proxy and click Submit.

To synchronize the content on the Smart Proxy, click the Overview tab and click Synchronize.

Select either Optimized Sync or Complete Sync.

To display a list of all Smart Proxy servers, on Foreman server, enter the following command:

# hammer capsule list

Using the ID, verify the details of your Smart Proxy:

# hammer capsule info --id capsule_id

To view the life cycle environments available for your Smart Proxy server, enter the following command and note the ID and the organization name:

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

Add the life cycle environment to your Smart Proxy server:

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

Synchronize the content from Foreman to Smart Proxy.

In the Foreman web UI, navigate to Content > Content Views and click Create New View.

In the Name field, enter a name for the view. Foreman automatically completes the Label field from the name you enter.

In the Description field, enter a description of the view.

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.

Click Save to create the Content View.

In the Repository Selection area, select the repositories that you want to add to your Content View, then click Add Repositories.

Click Publish New Version and in the Description field, enter information about the version to log changes.

Click Save.

Optional: to force metadata regeneration on Yum repositories, from the Actions list for your Content View versions, select Regenerate Repository Metadata.

Obtain a list of repository IDs:

# hammer repository list --organization "My_Organization"

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"

Publish the view:

# hammer content-view publish \
--name "Example_Content_View" \
--description "Example Content View" \
--organization "My_Organization"

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

In the Foreman web UI, navigate to Content > Content Views, and select the Content View that contains the modules you want to view.

Click the Versions tab and select the Content View version that you want to view.

Click the Module Streams tab to view the module streams that are available for the Content View.

Use the Filter field to refine the list of modules.

To view the information about the module, click the module.

promote_or_remove_content_views

promote_or_remove_content_views_to_environment.

In the Foreman web UI, navigate to Content > Content Views and select the Content View that you want to promote.

Click the Versions tab for the Content View.

Select the version that you want to promote and in the Actions column, click Promote.

Select the environment where you want to promote the Content View, and click Promote Version.

Click the Promote button again. This time select the Testing environment and click Promote Version.

Finally click on the Promote button again. Select the Production environment and click Promote Version.

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

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

In the Foreman web UI, navigate to Content > Content Views and click Create New View.

In the Name field, enter a name for the view. Foreman automatically completes the Label field from the name you enter.

In the Description field, enter a description of the view.

Select the Composite View? check box to create a Composite Content View.

Optional: select the Auto Publish check box if you want the Composite Content View to be republished automatically when a Content View is republished.

Click Save.

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.

Click Publish New Version to publish the Composite Content View. In the Description field, enter a description and click Save.

Click Promote and select the lifecycle environments to promote the Composite Content View to, enter a description, and then click Promote Version.

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

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

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"

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"

Publish the Composite Content View:

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

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"

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

Locate the Content View Dependency Solving Default, and select Yes.

It is possible to use filters in such a way that the resulting Content View has broken dependencies, and dependency resolution is not always guaranteed to solve this. This is because the package dependency resolution feature does not consider packages that are installed on your system independently of the Content View.

Packages in a Content View can have conflicting dependencies.

If a package in a repository has a dependency on a package outside the repository which has not been synced or added to the Content View, dependency solving will not solve dependencies for that package.

If you are using exclude filters on your Content View with dependency solving turned on, dependency solving takes precedence and brings in any required packages even if they were filtered out.

Dependency solving and filters can increase publishing times considerably.

In the Foreman web UI, navigate to Content > Content Views and select a Content View.

Navigate to Yum Content > Filters and click New Filter.

In the Name field, enter a name for your filter.

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.

From the Inclusion Type list, select either Include or Exclude.

In the Description field, enter a description for the filter, and click Save.

Depending on what you enter for Content Type, add rules to create the filter that you want.

Click the Affected repositories tab to select which specific repositories use this filter.

Click Publish New Version to publish the filtered repository. In the Description field, enter a description of the changes, and click Save.

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"

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"

Publish the Content View:

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

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"

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

# hammer content-view version list \
--organization=export-org \
 --content-view=view

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

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

# ls -lh /var/lib/pulp/exports/export-21527/view/1.0/2021-02-25T18-59-26-00-00/

You require all three files, for example, the tar.gz archive file, the toc.json and metadata.json to import the content successfully.

The exported archive must be in a directory under /var/lib/pulp/imports.

The directory must have pulp:pulp permissions so that Pulp can read and write the .json files in that directory.

If there are any Red Hat repositories in the export archive, the importing organization’s manifest must contain subscriptions for the products contained within the export.

The user importing the content view version must have the 'Content Importer' Role.

Copy the archived file with the exported Content View version to the /var/lib/pulp/imports directory on Foreman server where you want to import.

Set the user:group permission of the archive files to pulp:pulp.

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

Verify that the permission change occurs:

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

To import the Content View version to Foreman server, enter the following command:

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

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

# hammer content-view version list --content-view=view \
                                   --organization=import-20639
---|----------|---------|-------------|-----------------------
ID | NAME     | VERSION | DESCRIPTION | LIFECYCLE ENVIRONMENTS
---|----------|---------|-------------|-----------------------
7  | view 1.0 | 1.0     |             | Library
---|----------|---------|-------------|-----------------------

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

# ls -lh /var/lib/pulp/exports/export-21527/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 root root 443 Mar  2 03:35 metadata.json

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

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.

Since nothing changed between the previous export and now in the Organization’s library environment the change files are really small.

The exported archive must be in a directory under /var/lib/pulp/imports.

The directory must have pulp:pulp permissions so that Pulp can read and write the .json files in that directory.

If there are any Red Hat repositories in the export archive, the importing organization’s manifest must contain subscriptions for the products contained within the export.

The user importing the content must have the 'Content Importer' Role.

Copy the archived file with the exported Content View version to the /var/lib/pulp/imports directory on Foreman server where you want to import.

Set the permission of the archive files 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

On Foreman server where you want to import, create/enable repositories the same name and label as the exported content.

In the Foreman web UI, navigate to Content > Products, click the Yum content tab and add the same Yum content that the exported Content View version includes.

Identify the Organization that you wish to import into.

To import the Library content to Foreman server, enter the following command:

# hammer content-import library --organization=import-32158 \
                                --path=/var/lib/pulp/imports/2021-03-02T03-35-24-00-00
[............................................................................................................................................................................................................] [100%]

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.

Use the repository name or ID to export.

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

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

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

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/

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

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

Copy the export files to the /var/lib/pulp/imports directory on Foreman server where you want to import.

Set the ownership of the export files 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

Identify the Organization that you wish to import into.

To import the Library content to Foreman server, enter the following command:

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

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

Activation key that attaches subscriptions automatically.

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

Activation key with the exact set of subscriptions.

In the Foreman web UI, navigate to Content > Activation keys and click Create Activation Key.

In the Name field, enter the name of the activation key.

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.

In the Description field, enter a description for the activation key.

From the Environment list, select the environment to use.

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 https://yum.theforeman.org/client/2.5/ repository because it contains the katello-agent package.

Click Save.

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.

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"

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"

Obtain a list of your subscription IDs:

# hammer subscription list --organization "My_Organization"

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"

List the product content associated with the activation key:

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

Override the default auto-enable status for the https://yum.theforeman.org/client/2.5/ 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 https://yum.theforeman.org/client/2.5/el7/x86_64/foreman-client-release.rpm \
--value 1 \
--organization "My_Organization"

In the Foreman web UI, navigate to Content > Activation keys and click the name of the activation key.

Click the Subscriptions tab.

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.

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.

Click the Repository Sets tab and review the repositories' status settings.

To enable or disable a repository, select the check box for a repository and then change the status using the Select Action list.

Click the Details tab, select a Content View for this activation key, and then click Save.

List the subscriptions that the activation key currently contains:

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

Remove the required subscription from the activation key:

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

Attach new subscription to the activation key:

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

List the product content associated with the activation key:

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

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"

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

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

On the host, enter the following command to register the host to Foreman using the activation key:

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

To view a list of hosts for an organization, on Foreman server, enter the following command:

# hammer host list --organization "My_Organization"

In the Foreman web UI, navigate to Content > Activation Keys.

Click the activation key name that you want to edit.

Click the Subscriptions tab.

Click the edit icon next to Auto-Attach.

Select or clear the check box to enable or disable auto-attach.

Click Save.

In the Foreman web UI, navigate to Content > Activation Keys.

Click the activation key name you want to edit.

Click the edit icon next to Service Level.

Select the required service level from the list. The list only contains service levels available to the activation key.

Click Save.

In the Foreman web UI, navigate to Content > Products and click Create Product.

In the Name field, enter the name of the product. Foreman automatically completes the Label field based on your entry for Name.

Optional: From the GPG Key list, select the GPG key for the product.

Optional: From the SSL CA Cert list, select the SSL CA certificate for the product.

You do not need to complete SSL Client Cert or SSL Client Key.

Optional: From the Sync Plan list, select an existing sync plan or click Create Sync Plan to create a sync plan for your product requirements.

In the Description field, enter a description of the product.

Click Save.

Click the Repositories tab.

To add a repository, click New Repository.

In the Name field, enter the name of the repository.

From the Type list, set the content type to Yum.

Do not restrict the architecture or the OS version.

Use https://cdn.redhat.com/content/public/convert2rhel/7/x86_64/os/ as the upstream URL.

Disable the Verify SSL checkbox.

Optional: From the GPG Key list, select the GPG key for the product.

Optional: From the SSL CA Cert list, select the SSL CA certificate for the product.

Click Save.

Click the checkbox next to the new repository, then click Sync Now.

In the Foreman web UI, navigate to Content > Foreman developers Repositories.

Enable the Red Hat Enterprise Linux 7 Server repository.

In the Foreman web UI, navigate to Content > Activation keys and click Create Activation Key.

In the Name field, enter the name of the host activation key.

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.

In the Description field, enter a description for the activation key.

From the Environment list, select the environment to use.

From the Content View list, select a Content View to use.

Click Save.

If SCA is not enabled:

If SCA is enabled:

In the Foreman web UI, navigate to Configure > Host groups and click Create Host Group.

In the Name field, enter a name for the host group.

In the Description field, enter a description of the host group.

In the Lifecycle Environment field, select Library.

Optional: In the Content view field enter a value for the Content view.

For Steps 7 - 10, Foreman developers does not recommend setting values for this scenario as they might modify the host in ways that are not intended.

Optional: In the Puppet Environment field, select value the Puppet Environment.

The Deploy on field can be safely ignored.

Optional: In the Puppet Capsule field, select the name of the Puppet server configured for this smart-proxy.

Optional: In the Puppet CA Capsule field, select the Puppet Server CA configured for this smart-proxy.

Switch to the Activation Keys tab.

Optional: In the OpenSCAP Capsule field, select the OpenSCAP capsule to use for fetching SCAP content and uploading ARF reports.

Click Submit.

Switch to the Activation Keys tab.

In the Activation Keys field, enter the name of the product activation key.

Click Submit.

In the Foreman web UI, navigate to Hosts > All Hosts and click Register Host.

In the Host Group field, select the Host Group you want to use as a template for the conversion.

Optional, In the Operating System field, select the Operating System you are converting from.

Optional: In the Capsule field, select the required capsule.

Optional: Use the Setup Insights field to select whether to install Foreman developers Insights on converted hosts.

Optional: Use the Remote execution field to select whether to install SSH on converted hosts.

Optional: In the Token lifetime (hours) field, set the lifetime. The default value is four hours. If you require more time to run the command on your hosts, increase the value of the Token Lifetime.

Optional: Check the Insecure box if the hosts might not trust the Foreman CA.

Optional: In the Remote Execution Interface field, if the host has multiple interfaces and remote execution must use a single one, select the appropriate network interface.

In the Activation Key(s) field, enter the name of the content activation key.

Click Generate Command.

In the Foreman web UI, navigate to Hosts > All Hosts and select the target hosts you want to convert. You can use the Search field to filter the host list.

From the Select Action list, select Schedule Remote Job.

In the Job category field, select Convert to RHEL.

In the Job template field, verify that the Job Template is set to Convert to RHEL.

On the Job Invocation page, define the main job settings.

In the Activation Key field, enter the host activation key.

Optional: Click Show Advanced Fields if you want to configure further aspects.

Click Submit.

Note that:

Navigate to Content > Errata to view the list of available errata.

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

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

In the Foreman web UI, navigate to Content > Content Views and select a Content View that you want to use for applying errata.

Navigate to Yum Content > Filters and click New Filter.

In the Name field, enter Errata Filter.

From the Content Type list, select Erratum - Date and Type.

From the Inclusion Type list, select Exclude.

In the Description field, enter Exclude errata items from YYYY-MM-DD.

Click Save.

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.

For Date Type, select one of two check boxes:

Select the Start Date to exclude all errata on or after the selected date.

Leave the End Date field blank.

Click Save.

Click Publish New Version to publish the resulting repository.

Enter Adding errata filter in the Description field.

Click Save.

Click the Versions tab.

Click Promote to the right of the published version.

Select the environments you want to promote the Content View version to.

In the Description field, enter the description for promoting.

Click Promote Version to promote this Content View version across the required environments.

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"

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

Publish the Content View:

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

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"

In the Foreman web UI, navigate to Content > Errata.

From the Errata list, click the name of the errata that you want to apply.

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.

If you want to apply the errata to the content host, select the Apply Errata to Content Hosts immediately after publishing check box.

Click Confirm to apply the errata.

List the errata and its corresponding IDs:

# hammer erratum list

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

# hammer content-view version list

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

On Foreman, list all errata for the host:

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

Find the module stream an erratum belongs to:

# hammer erratum info --id ERRATUM_ID

On the host, update the module stream:

# yum update Module_Stream_Name

In the Foreman web UI, navigate to Hosts > Content Hosts and select the host you want to apply errata to.

Navigate to the Errata tab to see the list of errata.

Select the errata to apply and click Apply Selected. In the confirmation window, click Apply.

After the task to update all packages associated with the selected errata completes, click the Details tab to view the updated packages.

List all errata for the host:

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

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

# hammer job-invocation create \
--feature katello_errata_install \
--inputs errata=ERRATUM_ID1,ERRATUM_ID2 \
--search-query "name = client.example.com"

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

Navigate to Content > Errata.

Click the name of an erratum you want to apply.

Click to Content Hosts tab.

Select the hosts you want to apply errata to and click Apply to Hosts.

Click Confirm.

List all installable errata:

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

Apply one of the errata to multiple hosts:

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

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

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

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

# hammer task list

View the state of a selected task:

# hammer task progress --id task_ID

In the Foreman web UI, navigate to Content > Products and click Repo Discovery.

From the Repository Type list, select Container Images.

In the Registry to Discover field, enter the URL of the registry to import images from.

In the Registry Username field, enter the name that corresponds with your user name for the container image registry.

In the Registry Password field, enter the password that corresponds with the user name that you enter.

In the Registry Search Parameter field, enter any search criteria that you want to use to filter your search, and then click Discover.

Optional: To further refine the Discovered Repository list, in the Filter field, enter any additional search criteria that you want to use.

From the Discovered Repository list, select any repositories that you want to import, and then click Create Selected.

Optional: If you want to create a product, from the Product list, select New Product.

In the Name field, enter a product name.

Optional: In the Repository Name and Repository Label columns, you can edit the repository names and labels.

Click Run Repository Creation.

When repository creation is complete, you can click each new repository to view more information.

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

Navigate to Content > Products and select the name of your product.

Select the new repositories and then click Sync Now to start the synchronization process.

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"

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"

Synchronize the repository:

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

In the Foreman web UI, navigate to Content > Lifecycle Environments, and either create a lifecycle environment or select a lifecycle environment to edit.

In the Container Image Registry area, click the edit icon to the right of Registry Name Pattern area.

Use the list of variables and examples to determine which registry name pattern you require.

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

Click Save.

In the Foreman web UI, navigate to Content > Lifecycle Environments and select the lifecycle environment that you want to manage authentication for.

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.

Click Save.

In the Foreman web UI, navigate to Content > Red Hat Repositories.

In the Search field, enter an image name, for example, Red Hat Enterprise Linux 7 Server (ISOs).

In the Available Repositories window, expand Red Hat Enterprise Linux 7 Server (ISOs).

For the x86_64 7.2 entry, click the Enable icon to enable the repositories for the image.

Navigate to Content > Products and click Red Hat Enterprise Linux Server.

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.

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.

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"

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"

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"

In the Foreman web UI, navigate to Content > Products, and in the Products window, click Create Product.

In the Name field, enter a name to identify the product. This name populates the Label field.

In the GPG Key field, enter a GPG Key for the product.

From the Sync Plan list, select a synchronization plan for the product.

In the Description field, enter a description of the product.

Click Save.

In the Products window, click the new product and then click Create Repository.

In the Name field, enter a name for the repository. This automatically populates the Label field.

From the Type list, select file.

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.

Click Save.

Click the new repository.

Navigate to the Upload File and click Browse.

Select the .iso file and click Upload.

Create the product:

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

Create the repository:

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

Upload the ISO file to the repository:

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

In the Foreman web UI, navigate to Content > Products, click Create Product and enter the following details:

In the Name field, enter a name for the product. Foreman automatically completes the Label field based on what you have entered for Name.

Optional: From the GPG Key list, select the GPG key for the product.

Optional: From the Sync Plan list, select a synchronization plan for the product.

In the Description field, enter a description of the product, and then click Save.

In the Products window, select the name of a product that you want to create a repository for.

Click the Repositories tab, and then click New Repository.

In the Name field, enter a name for the repository. Foreman automatically completes the Label field based on the name.

From the Type list, select file.

In the Upstream URL field, enter the URL of the upstream repository to use as a source.

Select the Verify SSL check box if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.

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.

In the Upstream Password field, enter the corresponding password for the upstream repository.

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.

Optional: Check the Mirror on Sync check box to have this repository mirror the source repository during synchronization. It defaults to true (checked).

Optional: In the HTTP Proxy Policy field, select the desired HHTP proxy. The default value is Global Default.

Optional: Check the Publish via HTTP to have this repository published using HTTP during synchronization. It defaults to true (checked).

Optional: In the GPG Key field, select the GPG key for the repository.

Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.

Optional: In the SSL Client cert field, select the SSL Client Certificate for the repository.

Optional: In the SSL Client Key field, select the SSL Client Key for the repository.

Click Save.

Create a product

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

Create a File Type Repository

# hammer repository create \
--name "My Files" \
--content-type "file" \
--product "My File Product" \
--organization "My_Organization"

Ensure the Server and https://yum.theforeman.org/client/2.5/ repositories are enabled.

Install the Pulp Manifest package:

# yum install python3-pulp_manifest

# subscription-manager repos --enable rhel-7-server-satellite-capsule-6.10-rpms
# foreman-maintain packages unlock
# yum install install python-pulp-manifest -y
# foreman-maintain packages lock
# subscription-manager repos --disable rhel-7-server-satellite-capsule-6.10-rpms

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

# mkdir my_file_repo

Add files to the directory or create a test file:

# touch my_file_repo/test.txt

Enter the Pulp Manifest command to create the manifest:

# pulp-manifest my_file_repo

Verify the manifest was created:

# ls my_file_repo
PULP_MANIFEST test.txt

Ensure a product exists in Foreman server.

In the Foreman web UI, navigate to Content > Products.

Select the name of a product.

Click the Repositories tab and select New Repository.

In the Name field, enter a name for the repository. Foreman automatically completes this field based on what you enter for Name.

From the Type list, select the content type of the repository.

In the Upstream URL field, enter the local directory with the repository to use as the source, in the form file:///my_file_repo.

Select the Verify SSL check box to check the SSL certificate for the repository or clear the Verify SSL check box.

Optional: In the Upstream Username field, enter the upstream user name that you require. Clear this field if the repository does not require authentication.

Optional: In the Upstream Password field, enter the corresponding password for your upstream user name.

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.

Optional: Check the Mirror on Sync check box to have this repository mirror the source repository during synchronization. It defaults to true (checked).

Optional: In the HTTP Proxy Policy field, select the desired HHTP proxy. The default value is Global Default.

Optional: Check the Publish via HTTP to have this repository published using HTTP during synchronization. It defaults to true (checked).

Optional: In the GPG Key field, select the GPG key for the repository.

Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.

Optional: In the SSL Client cert field, select the SSL Client Certificate for the repository.

Optional: In the SSL Client Key field, select the SSL Client Key for the repository.

Select Save to save this repository entry.

In the Foreman web UI, navigate to Content > Products.

Select the name of a product.

Select the name of the repository you want to update.

From the Select Action menu, select Sync Now.

Visit the URL where the repository is published to see the files.

On your remote server, ensure that the Server and https://yum.theforeman.org/client/2.5/ repositories are enabled.

Install the Pulp Manifest package:

# yum install python3-pulp_manifest

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

Add files to the directory or create a test file:

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

Enter the Pulp Manifest command to create the manifest:

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

Verify the manifest was created:

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

Ensure a product exists in Foreman server, or create a product. For more information see Creating a File Type Repository in Foreman

In the Foreman web UI, navigate to Content > Products.

Select the name of a product.

Click the Repositories tab and select New Repository.

In the Name field, enter a name for the repository. Foreman automatically completes this field based on what you enter for Name.

From the Type list, select file.

In the Upstream URL field, enter the URL of the upstream repository to use as a source.

Select the Verify SSL check box if you want to verify that the upstream repository’s SSL certificates are signed by a trusted CA.

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.

In the Upstream Password field, enter the corresponding password for the upstream repository.

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.

Optional: Check the Mirror on Sync check box to have this repository mirror the source repository during synchronization. It defaults to true (checked).

Optional: In the HTTP Proxy Policy field, select the desired HHTP proxy. The default value is Global Default.

Optional: Check the Publish via HTTP to have this repository published using HTTP during synchronization. It defaults to true (checked).

Optional: In the GPG Key field, select the GPG key for the repository.

Optional: In the SSL CA Cert field, select the SSL CA Certificate for the repository.

Optional: In the SSL Client cert field, select the SSL Client Certificate for the repository.

Optional: In the SSL Client Key field, select the SSL Client Key for the repository.

Click Save.

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.

In the product’s window, select the name of the repository you want to update.

From the Select Action menu, select Sync Now.

In the Foreman web UI, navigate to Content > Products.

Select a product by name.

Select a file type repository by name.

Click Browse to search and select the file you want to upload.

Click Upload to upload the selected file to Foreman server.

Visit the URL where the repository is published to see the file.

In the Foreman web UI, navigate to Content > Products.

Select a product by name.

Select a file type repository by name.

Check to see if Publish via HTTP is enabled. If it is not, you require the certificates to use HTTPS.

Copy the URL where the repository is published.

List the file type repositories.

# hammer repository list --content-type file
---|----------|-----------------|--------------|----
ID | NAME     | PRODUCT         | CONTENT TYPE | URL
---|----------|-----------------|--------------|----
7  | My Files | My File Product | file         |
---|----------|-----------------|--------------|----

Display the repository information.

# hammer repository info --name "My Files" --product "My File Product" --organization-id 1

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

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

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

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

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