Importing Content

In the orcharhino management 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 orcharhino Server:

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

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

Upload the SSL Certificate to orcharhino:

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

In the orcharhino management UI, navigate to Content > Products, click Create Product.

In the Name field, enter a name for the product. orcharhino 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.

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 orcharhino management 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. orcharhino 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: In the Errata URL field, enter the URL of an errata service.

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 orcharhino Server performs. For more information, see Download Policies Overview.

From the Mirroring Policy list, select the type of content synchronization orcharhino 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 orcharhino

In the orcharhino management UI, navigate to Content > Products.

Click Create Product to create a product named Debian 11. For more information, see Creating a Custom 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 Custom Product.

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

Create a product named orcharhino Clients for Debian. For more information, see Creating a Custom Product.

Create a repository for Debian 12. You can find the upstream URL of all orcharhino Clients in the ATIX Service Portal. For more information, see Adding Custom deb Repositories.

Synchronize the orcharhino Clients for Debian to your orcharhino. For more information, see Synchronizing Repositories.

Create a content view to make the .deb packages consumable by content hosts. For more information, see Creating an Activation Key.

Create an activation key to register content hosts to orcharhino. For more information, see Creating an Activation Key.

Optional: Create a host group to simplify the process of creating hosts. For more information, see Creating a Host Group.

In the orcharhino management 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 orcharhino management UI, navigate to Content > Sync Status and expand the corresponding Product or repository tree.

In the orcharhino management UI, navigate to Administer > Settings.

Click the Content tab.

Change the default download policy depending on your requirements:

In the orcharhino management 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 orcharhino management 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

On orcharhino, 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 orcharhino management 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 orcharhino management 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 orcharhino.

Click the Locations tab and add a location.

Click the Organization tab and add an organization.

Click Submit.

In the orcharhino management 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 orcharhino management 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 orcharhino management 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 orcharhino management 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

In the orcharhino management 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 orcharhino Server:

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

Upload the GPG key to orcharhino:

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