Managing Content

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

Click Repo Discovery.

In the Repository Type field, select Yum Repositories.

In the URL to Discover field, enter the CentOS Stream URL http://mirror.centos.org/centos/8-stream.

Click Discover.

Select /AppStream/x86_64/os/ and /BaseOS/x86_64/os/ repositories.

Click Create Selected.

In the Product field select New Product.

In the Name field enter CentOS Stream or desired product name.

Click Run Repository Creation.

In the Foreman web UI, navigate to Content > Products

Select your new CentOS Stream product from the previous procedure.

Locate the AppStream x86_64 os and BaseOS x86_64 os repositories.

Select both repositories

Click Sync Now

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.

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

From the Environment list, select the Library.

From the Content View list, select Default Organization View.

Click Save.

Click on the Subscriptions tab on the Activation Key’s details page.

Click on the Add tab.

Select all the product subscriptions in the table.

Click Add Selected to save.

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

Click Generate to create the registration command.

Click on the files icon to copy the command to your clipboard.

Log in to the host you want register and run the previously generated command.

Ensure that the appropriate repositories have been enabled:

Generate the host registration command using the Hammer CLI:

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

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

Log in to the host you want register and run the previously generated command.

Ensure that the appropriate repositories have been enabled:

Generate the host registration command using the Foreman API:

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

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

Log in to the host you want register and run the previously generated command.

Ensure that the appropriate repositories have been enabled:

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

In the Name field, enter CentOS Content View.

In the Description field, enter a description for the content view.

In the Type field, select a Content View or a Composite Content View.

Click Create Content View.

In the Foreman web UI, navigate to Content > Content Views > Select CentOS Content View > Repositories > Select repository(ies).

Click Add Repositories.

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

Click on Publish New Version button on the top right of page.

Click Save

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

In the Name field, enter CentOS or the name of your new activation key.

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

From the Environment list, select the Library.

From the Content View list, select Centos Content View.

Click Save.

Click the Subscriptions tab on the Activation Key’s details page.

Click the Add tab.

Select your new CentOS Stream product in the table.

Click Add Selected to save.

In the Foreman web UI, navigate to Content > Lifecycle Environments and click Create Environment Path.

In the Name field, enter Production or the name of your new environment to add to the end of Library environment.

In the Description field, add an optional description for your new lifecycle environment.

Click Save.

In the Foreman web UI, navigate to Content > Content Views > Select your Content View.

On the Versions tab, click Promote for desired version under the Actions column.

Select Production lifecycle environment from the available promotion paths.

Add an optional Description.

Click Promote Version.

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

In the Foreman web UI, navigate to Content > Subscriptions and click Manage Manifest.

In the Manage Manifest window, click Browse.

Navigate to the location that contains the Red Hat subscription manifest file, then click Open. If the Manage Manifest window does not close automatically, click Close to return to the Subscriptions window.

Copy the Red Hat 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 Red Hat subscription manifest file:

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

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

In the Foreman web UI, 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.

In the Foreman web UI, 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.

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

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

Click Delete, and then confirm deletion.

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

In the Foreman web UI, 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.

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

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

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

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

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

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

Copy the SSL certificate to your Foreman server:

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

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

Upload the SSL Certificate to Foreman:

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

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.

Optional: In the Description field, enter a description for the repository.

From the Type list, select yum as type of repository.

Optional: From the Restrict to Architecture list, select an architecture. If you want to make the repository available to all hosts regardless of the architecture, ensure to select No restriction.

Optional: From the Restrict to OS Version list, select the OS version. If you want to make the repository available to all hosts regardless of the OS version, ensure to select No restriction.

Optional: In the Upstream 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.

Optional: Check the Ignore SRPMs checkbox to exclude source RPM packages from being synchronized to Foreman.

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

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

Optional: In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.

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.

From the Download Policy list, select the type of synchronization Foreman server performs. For more information, see Download Policies Overview.

From the Mirroring Policy list, select the type of content synchronization Foreman server performs. For more information, see Mirroring Policies Overview.

Optional: In the Retain package versions field, enter the number of versions you want to retain per package.

Optional: In the HTTP Proxy Policy field, select an HTTP proxy.

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

Optional: You can clear the Unprotected checkbox to require a subscription entitlement certificate for accessing this repository. By default, the repository is published through HTTP.

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

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 create the repository.

Enter the following command to create the repository:

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

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

Click Create Product to create a product named AlmaLinux 9. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type yum as follows:

Click Create Product to create a product named AlmaLinux 9 client.

On the Repositories tab, click New Repository to create a repository of type yum as follows:

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

Click Create Product to create a product named AlmaLinux 8. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type yum as follows:

Click Create Product to create a product named AlmaLinux 8 client.

On the Repositories tab, click New Repository to create a repository of type yum as follows:

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

Click Create Product to create a product named CentOS Stream 9. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type yum as follows:

Click Create Product to create a product named CentOS Stream 9 client.

On the Repositories tab, click New Repository to create a repository of type yum as follows:

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

Click Create Product to create a product named Oracle Linux 9. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type yum as follows:

Click Create Product to create a product named Oracle Linux 9 client.

On the Repositories tab, click New Repository to create a repository of type yum as follows:

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

Click Create Product to create a product named Oracle Linux 8. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type yum as follows:

Click Create Product to create a product named Oracle Linux 8 client.

On the Repositories tab, click New Repository to create a repository of type yum as follows:

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

Click Create Product to create a product named Rocky Linux 9. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type yum as follows:

Click Create Product to create a product named Rocky Linux 9 client.

On the Repositories tab, click New Repository to create a repository of type yum as follows:

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

Click Create Product to create a product named Rocky Linux 8. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type yum as follows:

Click Create Product to create a product named Rocky Linux 8 client.

On the Repositories tab, click New Repository to create a repository of type yum as follows:

Download the Release and Release.gpg files:

$ wget https://deb.debian.org/debian/dists/bullseye/Release
$ wget https://deb.debian.org/debian/dists/bullseye/Release.gpg

Verify the signature:

$ gpg --verify Release.gpg Release

If you cannot verify the signature, import the missing GPG public keys based on the output of the command above:

$ gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 0146DC6D4A0B2914BDED34DB648ACFD622F3D138
$ gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys A7236886F3CCCAAD148A27F80E98404D386FA1D9
$ gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys A4285295FC7B1A81600062A9605C66F00D6C9793

Optional: Verify the signature again:

$ gpg --verify Release.gpg Release

Export the ASCII-armored GPG public keys to a file:

$ gpg --armor --export 0146DC6D4A0B2914BDED34DB648ACFD622F3D138 A7236886F3CCCAAD148A27F80E98404D386FA1D9 A4285295FC7B1A81600062A9605C66F00D6C9793 > debian_11.txt

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.

Optional: In the Description field, enter a description for the repository.

From the Type list, select deb as type of repository.

Optional: In the Upstream URL field, enter the URL of the external repository to use as a source. You can find the upstream URLs on Debian-based systems in /etc/apt/sources.list.

In the Releases/Distributions field, set one or multiple releases separated by whitespace. The distributions specify the path from the repository root to the Release file. Repositories that omit the dists directory are using the deprecated flat repository structure. To synchronize a flat repository, you must specify exactly one distribution that ends with a /.

Optional: In the Components field, enter a component. This indicates the licensing terms of the software packages.

Optional: In the Architectures field, enter one or multiple architectures. If you want to make the repository available to all hosts regardless of the architecture, ensure to select No restriction.

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

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

Optional: In the Upstream Password field, enter the corresponding password for the upstream repository. Clear this field if the repository does not require authentication.

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.

From the Download Policy list, select the type of synchronization Foreman server performs. For more information, see Download Policies Overview.

From the Mirroring Policy list, select the type of content synchronization Foreman server performs. For more information, see Mirroring Policies Overview.

Optional: In the HTTP Proxy Policy field, select an HTTP proxy.

Optional: You can clear the Unprotected checkbox to require a subscription entitlement certificate for accessing this repository. By default, the repository is published through HTTP.

Optional: From the GPG Key list, select the GPG key if you want to verify the signatures of the Release files associated with the Debian 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 create the repository.

Enter the following command to create the repository:

# hammer repository create \
--content-type "deb" \
--deb-architectures "My_DEB_Architectures" \
--deb-components "_My_DEB_Components" \
--deb-releases "My_DEB_Releases" \
--gpg-key-id "My_GPG_Key_ID" \
--name "_My_Repository" \
--organization "My_Organization" \
--product "My_Product" \
--publish-via-http true \
--url My_Upstream_URL

Extract the GPG public keys from the Release file

Import the content credentials into Foreman

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

Click Create Product to create a product named Debian 11. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create three repositories of type deb as follows:

Click Create Product to create a product named Debian 11 client. For more information, see Creating a Product.

On the Repositories tab, click New Repository to create a repository of type deb as follows:

In the Foreman web UI, navigate to Hosts > All Hosts and select a host.

Select the Content tab, then select the Repository sets subtab. On the tab, there is a set of repositories available to each host with a status of Enabled or Disabled.

You can override the default status by using the action menus on each table row by changing the status to Override to disabled, Override to enabled, or Reset to default.

You can also bulk select the checkboxes on each table row, and use the vertical ellipsis icon at the top.

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, such as 7Server, and base architecture, such as x86_64.

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

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.

Optional: To view the progress of the synchronization in the Foreman web UI, navigate to Content > Sync Status and expand the corresponding Product or repository tree.

Log in to your Foreman server using SSH.

Run the following Bash script:

ORG="My_Organization"

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

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

Click the Content tab.

Change the default download policy depending on your requirements:

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

Select the required product name.

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

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

List the repositories for an organization:

# hammer repository list \
--organization-label My_Organization_Label

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

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

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

Select the product name.

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

From the list, select a mirroring policy and click Save.

List the repositories for an organization:

# hammer repository list \
--organization-label My_Organization_Label

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

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

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.

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

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

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

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

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.

Optional: To verify the checksum, click Verify Content Checksum from the Select Action menu.

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.

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

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

To create the synchronization plan, enter the following command:

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

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

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

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

Select a product.

On the Details tab, select a Sync Plan from the drop down menu.

Assign a sync plan to a product:

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

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 to the sync 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 content-credentials create \
--content-type gpg_key \
--name "My_GPG_Key" \
--organization "My_Organization" \
--path ~/RPM-GPG-KEY-EXAMPLE-95

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

Select the product that contains the repository sets that you want to restrict.

In the Repositories tab, click the repository that you want to restrict.

From the Restrict to OS list, select the operating system to include Red Hat Enterprise Linux operating systems for their corresponding Red Hat Enterprise Linux repositories.

Click Save to submit your change.

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 "My_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 proxy list

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

# hammer proxy info \
--id MySmart Proxy_ID_

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

# hammer proxy content lifecycle-environments \
--id MySmart Proxy_ID_

Remove the life cycle environment from Smart Proxy server:

# hammer proxy content remove-lifecycle-environment \
--id MySmart Proxy_ID_
--lifecycle-environment-id My_Lifecycle_Environment_ID

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

# hammer proxy content synchronize \
--id Mysmart-proxy_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 proxy list

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

# hammer proxy info \
--id Mysmart-proxy_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 proxy content available-lifecycle-environments \
--id Mysmart-proxy_ID_

Add the life cycle environment to your Smart Proxy server:

# hammer proxy content add-lifecycle-environment \
--id Mysmart-proxy_ID_ \
--lifecycle-environment-id My_Lifecycle_Environment_ID
--organization "My_Organization"

Synchronize the content from Foreman to Smart Proxy.

In the Foreman web UI, navigate to Content > Content Views and click Create content 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.

In the Type field, select a Content view or a Composite content view.

Optional: If you want to solve dependencies automatically every time you publish this Content View, select the Solve dependencies checkbox. 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.

Optional: If you want to designate this Content View for importing from an upstream server, select the Import only checkbox. Import-only content views cannot be published directly.

Click Create content view.

Click Create content view to create the Content View.

In the Repositories tab, select the repository from the Type list that you want to add to your Content View, select the checkbox next to the available repositories you want to add, then click Add repositories.

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

Optional: You can enable a promotion path by clicking Promote to Select a lifecycle environment from the available promotion paths to promote new version.

Click Next.

On the Review page, you can review the environments you are trying to publish.

Click Finish.

Obtain a list of repository IDs:

# hammer repository list --organization "My_Organization"

Create the Content View and add repositories:

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

Publish the view:

# hammer content-view publish \
--description "My_Content_View" \
--name "My_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 "My_Content_View" \
--organization "My_Organization" \
--repository-id repository_ID

In the Foreman web UI, navigate to a published version of a Content View > Module Streams to view the module streams that are available for the Content Types.

Use the Search field to search for specific modules.

To view the information about the module, click the module and its corresponding tabs to include Details, Repositories, Profiles, and Artifacts.

List all organizations:

# hammer organization list

View all module streams for your organization:

# hammer module-stream list \
--organization-id My_Organization_ID

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.

Select the version that you want to promote, click the vertical ellipsis icon, and click Promote.

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

In the Foreman web UI, navigate to Content > Content Views and click Create content view.

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

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

On the Type tab, select Composite content view.

Optional: If you want to automatically publish a new version of the Composite Content View when a Content View is republished, select the Auto publish checkbox.

Click Create content view.

On the Content views tab, select the Content Views that you want to add to the Composite Content View, and then click Add content views.

In the Add content views window, select the version of each Content View.

Optional: If you want to automatically update the Content View to the latest version, select the Always update to latest version checkbox.

Click Add, then click Publish new version.

Optional: In the Description field, enter a description of the Content View.

In the Publish window, set the Promote switch, then select the lifecycle environment.

Click Next, then click Finish.

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 Content View to the Composite Content View. You can identify Content View, Content View version, and Organization in the commands by either their ID or their name. To add multiple Content Views to the Composite Content View, repeat this step for every Content View you want to include.

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

From the list of content views, select the required Content View.

On the Details tab, toggle Solve dependencies.

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

On the Filters tab, click Create filter.

Enter a name.

From the Content type list, select a content type.

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

Optional: In the Description field, enter a description for the filter.

Click Create filter to create your content filter.

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

Select if you want the filter to Apply to subset of repositories or Apply to all repositories.

Click Publish New Version to publish the filtered repository.

Optional: In the Description field, enter a description of the changes.

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

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"

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

On the Filters tab, click Create filter.

Enter a name.

From the Content type list, select a content type.

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

Optional: In the Description field, enter a description for the filter.

Click Create filter to create your content filter.

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

Select if you want the filter to Apply to subset of repositories or Apply to all repositories.

Click Publish New Version to publish the filtered repository.

Optional: In the Description field, enter a description of the changes.

Click Save to publish a new version of the Content View.

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 \
--content-view "Example_Content_View" \
--description "My_Content_View_Filter_Description" \
--inclusion false \
--name "Errata Filter" \
--organization "My_Organization" \
--type erratum

Add a rule to the filter:

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

Publish the Content View:

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

Promote the view across all environments:

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

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

Click on the custom product.

Click on the custom repository.

Copy the Published At: URL.

Continue with the procedure on disconnected Foreman server.

Download the katello-server-ca.crt file from the connected Foreman server:

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

Create an SSL Content Credential with the contents of katello-server-ca.crt. For more information on creating an SSL Content Credential, see Importing SSL Certificates.

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

Create your custom product with the following:

Use the organization name or ID to export.

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

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

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

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.

Use the organization name or ID to export:

# hammer content-export complete library \
--organization="My_Organization" \
--format=syncable

Optional: Verify that the exported content is located in the export directory:

# du -sh /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 library --organization="My_Organization"

Generated /var/lib/pulp/exports/My_Organization/Export-Library/3.0/2021-03-02T04-22-14-00-00/metadata.json

Optional: View the exported data:

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

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

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

---|----------|---------|-------------|-----------------------
ID | NAME     | VERSION | DESCRIPTION | LIFECYCLE ENVIRONMENTS
---|----------|---------|-------------|-----------------------
5  | view 3.0 | 3.0     |             | Library
4  | view 2.0 | 2.0     |             |
3  | view 1.0 | 1.0     |             |
---|----------|---------|-------------|----------------------

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

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

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

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

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

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

Optional: Verify that the exported content is located in the export directory:

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

Create an incremental export:

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

Optional: View the exported Content View:

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

Export a repository using the product name and repository name:

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

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/2022-09-02T03-35-24-00-00/

Export a repository using the repository name or ID:

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

Optional: Verify that the exported content is located in the export directory:

# du -sh /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 exported files to a subdirectory of /var/lib/pulp/imports on Foreman server where you want to import.

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

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

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="My_Organization" \
--path=/var/lib/pulp/imports/2021-03-02T03-35-24-00-00

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.

Copy the exported files to a subdirectory of /var/lib/pulp/imports on Foreman server where you want to import.

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

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

Verify that the ownership is set correctly:

# 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-id=My_Organization_ID \
--path=/var/lib/pulp/imports/2021-02-25T21-15-22-00-00/

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

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

Copy the exported files to a subdirectory of /var/lib/pulp/imports on Foreman server where you want to import.

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

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

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 checkbox, and in the Limit field, enter the maximum number of systems you can register with the activation key. If you want unlimited hosts to register with the activation key, ensure the Unlimited Hosts checkbox is selected.

Optional: 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/3.3/ repository because it contains the katello-agent package.

If Simple Content Access (SCA) is enabled:

If SCA is not enabled:

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

List the product content associated with the activation key:

Override the default auto-enable status for the https://yum.theforeman.org/client/3.3/ 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/3.3/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 checkboxes to the left of the subscriptions to be removed and then click Remove Selected.

To add subscriptions, select Add, and then select the checkboxes 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 checkbox 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"

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

Click Generate to create the registration command.

Click on the files icon to copy the command to your clipboard.

Log in to the host you want register and run the previously generated command.

Ensure that the appropriate repositories have been enabled:

Generate the host registration command using the Hammer CLI:

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

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

Log in to the host you want register and run the previously generated command.

Ensure that the appropriate repositories have been enabled:

Generate the host registration command using the Foreman API:

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

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

Log in to the host you want register and run the previously generated command.

Ensure that the appropriate repositories have been enabled:

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

Download the SLES 15 SP3 installation medium from suse.com/download/sles.

Download the signature and checksum from suse.com.

Transfer the .iso image, the signature, and the checksum from your local machine to Foreman server using scp:

# scp SLE-15-SP3-Full-x86_64-GM-Media1.iso root@foreman.example.com:/tmp/
# scp SLE-15-SP3-Full-x86_64-GM-Media1.iso.sha256 root@foreman.example.com:/tmp/
# scp sles_15_sp3.signature root@foreman.example.com:/tmp/

On your Foreman server, verify the integrity and authenticity of the .iso image using GPG public keys:

# cd /tmp
# gpg --verify sles_15_sp3.signature SLE-15-SP3-Full-x86_64-GM-Media1.iso.sha256
# echo '2a6259fc849fef6ce6701b8505f64f89de0d2882857def1c9e4379d26e74fa56 SLE-15-SP3-Full-x86_64-GM-Media1.iso' | sha256sum --check

Mount the .iso image:

# mount SLE-15-SP3-Full-x86_64-GM-Media1.iso /mnt

Copy the content of the mounted installation medium to the pub directory:

# mkdir -p /var/www/html/pub/installation_media/sles/15sp3
# cp -a /mnt/* /var/www/html/pub/installation_media/sles/15sp3/

Unmount and delete the .iso image:

# cd
# umount /mnt
# rm -f /tmp/SLE-15-SP3-Full-x86_64-GM-Media1.iso
# rm -f /tmp/SLE-15-SP3-Full-x86_64-GM-Media1.iso.sha256
# rm -f /tmp/sles_15_sp3.signature

In the Foreman web UI, navigate to Hosts > Installation Media and click Create Medium.

Set a Name for the installation medium for SLES 15 SP3. Add local to the name because the path of the extracted .iso image points to your Foreman.

Set the Path of the extracted .iso image. The content of /var/www/html/pub/ is publicly available on http://foreman.example.com/pub/. If you extract the .iso image to /var/www/html/pub/installation_media/sles/15sp3/, the path is http://foreman.example.com/pub/installation_media/sles/15sp3/.

Set the Operating System Family to SUSE for all SLES systems.

Set a location and organization context for the installation media.

On the Parameters tab, add the sle-module-basesystem-url parameter, select the string type, and enter the value http://foreman.example.com/pub/installation_media/sles/15sp3/. Note that the value depends on the path of the extracted .iso image.

Click Submit to save the installation media entry for SLES 15 SP3.

In the Foreman web UI, navigate to Hosts > Operating Systems and click Create Operating System.

Set the Name of the operating system. Choose a name as reported by Ansible, Puppet, or Salt as fact.

Set the Major Version of SLES, for example 15.

Set the Minor Version of SLES, for example 3 for SLES 15 SP3.

Optional: Add an arbitrary Description.

Set the Family to SUSE for all SLES systems.

Set the Root Password Hash to SHA256 for SLES 15 SP3.

Assign the Architectures to SLES 15 SP3.

Click Submit to save the operating system entry.

In the Foreman web UI, navigate to Hosts > Partition Tables and click Create Partition Table. The partition tables are stored in the /usr/share/foreman/app/views/unattended/partition_tables_templates/ directory on your Foreman server.

In the Foreman web UI, navigate to Hosts > Provisioning Templates and click Create Template. The provisioning templates are stored in the /usr/share/foreman/app/views/unattended/provisioning_templates/ directory on your Foreman server.

In the Foreman web UI, navigate to Hosts > Operating Systems.

Select the previously created operating system.

On the Partition Table tab, select the previously created partition table.

On the Templates tab, select the previously created provisioning template.

Click Submit to save the operating system entry.

Connect to your Foreman server using SSH:

# ssh root@foreman.example.com

Install the SCC Manager plug-in on your Foreman:

# yum install -y tfm-rubygem-foreman_scc_manager

Run database migrations on your Foreman:

# foreman-rake db:migrate
# foreman-rake db:seed

Restart Foreman services:

# foreman-maintain service restart

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

In the Foreman web UI, navigate to Content > SUSE Subscriptions.

Click Add SCC Account.

Enter your account name and password.

Optional: Set a Sync interval to periodically update the SCC authentication tokens. Note that this does not refer to synchronizing content to Foreman.

Assign a GPG key for SUSE products to the SCC products. zypper automatically verifies the signatures of each software package to ensure their authenticity.

Click Test connection to verify your account information. Note that you have to re-enter your password if you have already saved your SCC account to Foreman.

Click Submit to save your SCC account to Foreman.

In the Foreman web UI, navigate to Content > SUSE Subscriptions, select your SCC account, and click Sync to fetch a list of products associated to your SCC account.

In the Foreman web UI, navigate to Content > SUSE Subscriptions.

Select your SCC account.

Enter a new Login and Password.

Click Submit to change your SCC account.

In the Foreman web UI, navigate to Content > SUSE Subscriptions.

Click Select products on your previously synchronized SCC account.

Select all SUSE products you want to synchronize to Foreman. This guide assumes you have access to and select the SUSE Linux Enterprise Server 15 SP3 x86_64 product.

Click Submit to create the selected SUSE products in Foreman.

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

Select the SUSE Linux Enterprise Server 15 SP3 x86_64 product and click Sync Now to synchronize the SUSE repositories for SLES 15 SP3 to Foreman.

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

Create a Content View called SLES 15 SP3 comprising the SLES repositories created in the SLES 15 SP3 product and a Content View called SLES 15 SP3 Foreman client comprising the Foreman client repository created in the SLES 15 SP3 Foreman client product.

Publish a new version of both Content Views.

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

Click Create Content View to create a Composite Content View called Composite SLES 15 SP3 comprising the previously published SLES 15 SP3 Content View, the SLES 15 SP3 Foreman client Content View, and optionally further Content Views of your choice, for example a Content View containing Puppet. For more information, see creating a Composite Content View.

Publish a new version and promote this version to the Life Cycle Environment of your choice.

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

Click Create Activation Key to create an Activation Key called sles-15-sp3.

On the Details tab, select a Life Cycle Environment and Composite Content View.

On the Subscriptions tab, select the necessary subscriptions, for example SLES 15 SP3, SLES 15 SP3 Foreman client, and Puppet.

In the Foreman web UI, 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 Hosts > All Hosts and select the host you require.

If there are errata associated with the host, an Installable Errata card on the new Host page displays an interactive pie chart showing a breakdown of the security advisories, bugfixes, and enhancements.

On the new Host page, select the Content tab.

On the Content page select the Errata tab.

The page displays installable errata for the chosen host.

Click the checkbox for any errata you wish to install.

Using the vertical ellipsis icon next to the errata you want to add to the host, select Apply via Katello agent if you have no connectivity to the target host using SSH.

Select Apply via Remote Execution to use Remote Execution, or Apply via customized remote execution if you want to customize the remote execution.

Click Submit.

In the Foreman web UI, navigate to Hosts > All Hosts and select the host you require.

If there are errata associated with the host, they are displayed in an Installable Errata card on the new Host page.

On the Content tab, Errata displays installable errata for the chosen host.

Click the checkbox for any errata you wish to install.

Using the vertical ellipsis icon next to the errata you want to add to the host, select Apply via Remote Execution to use Remote Execution. Select Apply via customized remote execution if you want to customize the remote execution, or select Apply via Katello agent if you have no connectivity to the target host using SSH.

Click Submit.

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

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

For Date Type, select one of two checkboxes:

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

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

In the Foreman web UI, 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 Create Product.

In the Name field, enter a name for your OSTree content. This automatically populates the Label field.

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.

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

Click Save.

When the product creation completes, click New Repository.

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

From the Type list, select ostree.

In the Upstream URL field, enter the URL of the external repository to use as a source. For example http://www.example.com/rpm-ostree/.

Optional: Select the Verify SSL checkbox 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.

In the Upstream Authentication Token field, enter the corresponding token for the upstream repository.

From the Mirroring Policy menu, select one of the following policies to mirror OSTree content for this repository:

Optional: In the HTTP Proxy Policy field, select an HTTP proxy.

Optional: Disable the Unprotected checkbox to require a subscription entitlement certificate for accessing the published 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.

When the repository creation completes, select the new repository and click Sync Now to start the synchronization process.

To view the synchronization status, navigate to Content > Sync Status and expand the entry that you want to view.

Create a product for your OSTree content:

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

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"

Synchronize the repository:

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