Managing Custom File Type Content

In orcharhino, you might require methods of managing and distributing SSH keys and source code files or larger files such as virtual machine images and ISO files. To achieve this, custom products in orcharhino include repositories for custom file types. This provides a generic method to incorporate arbitrary files in a product.

You can upload files to the repository and synchronize files from an upstream orcharhino Server. When you add files to a custom file type repository, you can use the normal orcharhino management functions such as adding a specific version to a Content View to provide version control and making the repository of files available on various orcharhino Proxys. Clients must download the files over HTTP or HTTPS using curl -O.

You can create a file type repository in orcharhino Server only in a custom product, but there is flexibility in how you create the file type repository. You can create an independent file type repository in a directory on the system where orcharhino is installed, or on a remote HTTP server, and then synchronize the contents of that directory into orcharhino. This method is useful when you have multiple files to add to a orcharhino repository.

Creating a Custom File Type Repository

The procedure for creating a custom file type repository is the same as the procedure for creating any custom content, except that when you create the repository, you select the file type. You must create a product and then add a custom repository.

To use the CLI instead of the orcharhino management UI, see the CLI procedure.

Procedure

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

  2. Select a product that you want to create a repository for.

  3. On the Repositories tab, click New Repository.

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

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

  6. From the Type list, select file as type of repository.

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

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

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

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

  11. Optional: In the Upstream Authentication Token field, provide the token of the upstream repository user for authentication. Leave this field empty if the repository does not require authentication.

  12. From the Mirroring Policy list, select the type of content synchronization orcharhino Server performs. For more information, see Mirroring Policies Overview.

  13. Optional: In the HTTP Proxy Policy field, select or unselect using a HTTP proxy. By default, it uses the Global Default HTTP proxy.

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

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

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

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

  18. Click Save to create the repository.

CLI procedure

  1. Create a custom product:

    # hammer product create \
--description "My_Files" \
--name "My_File_Product" \
--organization "My_Organization" \
--sync-plan "My_Sync_Plan"
    Table 1. Optional Parameters for the hammer product create Command
    Option Description

    --gpg-key-id gpg_key_id

    GPG key numeric identifier

    --sync-plan sync_plan_name

    Sync plan name to search by

    --sync-plan-id sync_plan_id

    Sync plan numeric identifier

  2. Create a file type repository:

    # hammer repository create \
--content-type "file" \
--name "My_Files" \
--organization "My_Organization" \
--product "My_File_Product"
    Table 2. Optional Parameters for the hammer repository create Command
    Option Description

    --checksum-type sha_version

    Repository checksum, currently 'sha1' & 'sha256' are supported

    --download-policy policy_name

    Download policy for yum repos (either 'immediate' or 'on_demand').

    --gpg-key gpg_key_name

    Key name to search by

    --gpg-key-id gpg_key_id

    GPG key numeric identifier

    --mirror-on-sync boolean

    Must this repo be mirrored from the source, and stale RPMs removed, when synced? Set to true or false, yes or no, 1 or 0.

    --publish-via-http boolean

    Must this also be published using HTTP? Set to true or false, yes or no, 1 or 0.

    --upstream-username repository_username

    Upstream repository user, if required for authentication

    --upstream-password repository_password

    Password for the upstream repository user

    --url source_repo_url

    URL of the Source repository

    --verify-ssl-on-sync boolean

    Must Katello verify that the upstream URL’s SSL certificates are signed by a trusted CA? Set to true or false, yes or no, 1 or 0.

Creating a Custom File Type Repository in a Local Directory

You can create a custom file type repository, from a directory of files, on the base system where orcharhino is installed using the pulp-manifest command. You can then synchronize the files into orcharhino Server. When you add files to a file type repository, you can work with the files as with any other repository.

Use this procedure to configure a repository in a directory on the base system where orcharhino is installed. To create a file type repository in a directory on a remote server, see Creating a Remote File Type Repository.

Procedure

To create a file type repository in a local directory, complete the following procedure:

  1. Ensure the Server and orcharhino Client for Amazon Linux repositories are enabled.

  2. Install the Pulp Manifest package:

    # yum install python3-pulp_manifest

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

    # mkdir my_file_repo

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

    # touch my_file_repo/test.txt

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

    # pulp-manifest my_file_repo

  6. Verify the manifest was created:

    # ls my_file_repo
PULP_MANIFEST test.txt
Importing Files from a File Type Repository

To import files from a file type repository in a local directory, complete the following procedure:

  1. Ensure a custom product exists in orcharhino Server.

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

  3. Select the name of a product.

  4. Click the Repositories tab and select New Repository.

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

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

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

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

  9. Optional: In the Upstream Username field, enter the upstream user name that you require.

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

  11. Optional: In the Upstream Authentication Token field, provide the token of the upstream repository user for authentication. Leave this field empty if the repository does not require authentication.

  12. From the Mirroring Policy list, select the type of content synchronization orcharhino Server performs. For more information, see Mirroring Policies Overview.

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

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

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

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

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

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

  19. Select Save to save this repository entry.

Updating a File Type Repository

To update the file type repository, complete the following steps:

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

  2. Select the name of a product.

  3. Select the name of the repository you want to update.

  4. From the Select Action menu, select Sync Now.

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

Creating a Remote File Type Repository

You can create a custom file type repository from a directory of files that is external to orcharhino Server using the pulp-manifest command. You can then synchronize the files into orcharhino Server over HTTP or HTTPS. When you add files to a file type repository, you can work with the files as with any other repository.

Use this procedure to configure a repository in a directory on a remote server. To create a file type repository in a directory on the base system where orcharhino Server is installed, see Creating a Custom File Type Repository in a Local Directory.

Prerequisites

Before you create a remote file type repository, ensure the following conditions exist:

  • You have a Amazon Linux 7 server registered to your orcharhino or the Red Hat CDN.

  • You have installed an HTTP server.

Procedure

To create a file type repository in a remote directory, complete the following procedure:

  1. On your remote server, ensure that the Server and orcharhino Client for Amazon Linux repositories are enabled.

  2. Install the Pulp Manifest package:

    # yum install python3-pulp_manifest

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

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

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

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

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

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

  6. Verify the manifest was created:

    # ls /var/www/html/pub/my_file_repo
PULP_MANIFEST test.txt
Importing Files from a Remote a File Type Repository

To import files from a remote file type repository, complete the following procedure:

  1. Ensure a custom product exists in orcharhino Server, or create a custom product. For more information see Creating a Custom File Type Repository

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

  3. Select the name of a product.

  4. Click the Repositories tab and select New Repository.

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

  6. From the Type list, select file.

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

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

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

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

  11. Optional: In the Upstream Authentication Token field, provide the token of the upstream repository user for authentication. Leave this field empty if the repository does not require authentication.

  12. From the Mirroring Policy list, select the type of content synchronization orcharhino Server performs. For more information, see Mirroring Policies Overview.

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

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

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

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

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

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

  19. Click Save.

  20. To update the file type repository, navigate to Content > Products. Select the name of a product that contains the repository that you want to update.

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

  22. From the Select Action menu, select Sync Now.

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

Uploading Files To a Custom File Type Repository

Use this procedure to upload files to a custom file type repository.

Procedure

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

  2. Select a custom product by name.

  3. Select a file type repository by name.

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

  5. Click Upload to upload the selected file to orcharhino Server.

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

CLI procedure
# hammer repository upload-content \
--id repo_ID \
--organization "My_Organization" \
--path example_file

The --path option can indicate a file, a directory of files, or a glob expression of files. Globs must be escaped by single or double quotes.

Downloading Files to a Host From a Custom File Type Repository

You can download files to a client over HTTPS using curl -O, and optionally over HTTP if the Unprotected option for repositories is selected.

Prerequisites
Procedure

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

  2. Select a custom product by name.

  3. Select a file type repository by name.

  4. Ensure to select the Unprotected check box to access the repository is published through HTTP.

  5. Copy the URL where the repository is published.

CLI procedure

  1. List the file type repositories.

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

  2. Display the repository information.

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

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

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

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

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

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

    For HTTP:

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

    For HTTPS:

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

Importing Kickstart Repositories for Amazon Linux 7

To import Kickstart repositories for Amazon Linux 7, complete the following steps on orcharhino.

Procedure

  1. Navigate to the Red Hat Customer Portal at access.redhat.com and log in.

  2. In the upper left of the window, click Downloads.

  3. To the right of Amazon Linux 7, click Versions 7 and below.

  4. From the Version list, select the required version of the Amazon Linux 7, for example 7.7.

  5. In the Download Amazon Linux window, locate the binary DVD version of the ISO image, for example, Amazon Linux 7.7 Binary DVD, and click Download Now.

  6. When the download completes, copy the ISO image to orcharhino Server.

  7. On orcharhino Server, create a mount point and temporarily mount the ISO image at that location:

    # mkdir /mnt/iso
# mount -o loop rhel-binary-dvd.iso /mnt/iso

  8. Create Kickstart directories:

    # mkdir --parents /var/www/html/pub/sat-import/content/dist/rhel/server/7/7.7/x86_64/kickstart/

  9. Copy the kickstart files from the ISO image:

    # cp -a /mnt/iso/* /var/www/html/pub/sat-import/content/dist/rhel/server/7/7.7/x86_64/kickstart/

  10. Add the following entries to the listing files:

    To the /var/www/html/pub/sat-import/content/dist/rhel/server/7/listing file, append the version number with a new line. For example, for the RHEL 7.7 ISO, append 7.7.

    To the /var/www/html/pub/sat-import/content/dist/rhel/server/7/7.7/listing file, append the architecture with a new line. For example, x86_64.

    To the /var/www/html/pub/sat-import/content/dist/rhel/server/7/7.7/x86_64/listing file, append kickstart with a new line.

  11. Copy the .treeinfo files from the ISO image:

    # cp /mnt/iso/.treeinfo /var/www/html/pub/sat-import/content/dist/rhel/server/7/7.7/x86_64/kickstart/treeinfo

  12. If you do not plan to use the mounted binary DVD ISO image, unmount and remove the directory:

    # umount /mnt/iso
# rmdir /mnt/iso

  13. In the orcharhino management UI, enable the Kickstart repositories.

Importing Kickstart Repositories for Amazon Linux 8

To import Kickstart repositories for Amazon Linux 8, complete the following steps on orcharhino.

Procedure

  1. Navigate to the Red Hat Customer Portal at access.redhat.com and log in.

  2. In the upper left of the window, click Downloads.

  3. Click Amazon Linux 8*.

  4. In the Download Amazon Linux window, locate the binary DVD version of the ISO image, for example, Amazon Linux 8.1 Binary DVD, and click Download Now.

  5. When the download completes, copy the ISO image to orcharhino Server.

  6. On orcharhino Server, create a mount point and temporarily mount the ISO image at that location:

    # mkdir /mnt/iso
# mount -o loop rhel-binary-dvd.iso /mnt/iso

  7. Create directories for Amazon LinuxLinux 8 AppStream and BaseOS Kickstart repositories:

    # mkdir --parents /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/appstream/kickstart
# mkdir --parents /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/baseos/kickstart

  8. Copy the kickstart files from the ISO image:

    # cp -a /mnt/iso/AppStream/* /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/appstream/kickstart

# cp -a /mnt/iso/BaseOS/* /mnt/iso/images/ /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/baseos/kickstart

    Note that for BaseOS, you must also copy the contents of the /mnt/iso/images/ directory.

  9. Add the following entries to the listing files:

    To the /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/appstream/listing file, append kickstart with a new line.

    To the /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/baseos/listing file, append kickstart with a new line:

    To the /var/www/html/pub/sat-import/content/dist/rhel8/listing file, append the version number with a new line. For example, for the RHEL 8.1 binary ISO, append 8.1.

  10. Copy the .treeinfo files from the ISO image:

    # cp /mnt/iso/.treeinfo /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/appstream/kickstart/treeinfo

# cp /mnt/iso/.treeinfo /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/baseos/kickstart/treeinfo

  11. Open the /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/baseos/kickstart/treeinfo file for editing.

  12. In the [general] section, make the following changes:

    • Change packagedir = AppStream/Packages to packagedir = Packages

    • Change repository = AppStream to repository = .

    • Change variant = AppStream to variant = BaseOS

    • Change variants = AppStream,BaseOS to variants = BaseOS

  13. In the [tree] section, change variants = AppStream,BaseOS to variants = BaseOS.

  14. In the [variant-BaseOS] section, make the following changes:

    • Change packages = BaseOS/Packages to packages = Packages

    • Change repository = BaseOS to repository = .

  15. Delete the [media] and [variant-AppStream] sections.

  16. Save and close the file.

  17. Verify that the /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/baseos/kickstart/treeinfo file has the following format:

    [checksums]
images/efiboot.img = sha256:9ad9beee4c906cd05d227a1be7a499c8d2f20b3891c79831325844c845262bb6
images/install.img = sha256:e246bf4aedfff3bb54ae9012f959597cdab7387aadb3a504f841bdc2c35fe75e
images/pxeboot/initrd.img = sha256:a66e3c158f02840b19c372136a522177a2ab4bd91cb7269fb5bfdaaf7452efef
images/pxeboot/vmlinuz = sha256:789028335b64ddad343f61f2abfdc9819ed8e9dfad4df43a2694c0a0ba780d16

[general]
; WARNING.0 = This section provides compatibility with pre-productmd treeinfos.
; WARNING.1 = Read productmd documentation for details about new format.
arch = x86_64
family = Red Hat Enterprise Linux
name = Red Hat Enterprise Linux 8.1.0
packagedir = Packages
platforms = x86_64,xen
repository = .
timestamp = 1571146127
variant = BaseOS
variants = BaseOS
version = 8.1.0

[header]
type = productmd.treeinfo
version = 1.2

[images-x86_64]
efiboot.img = images/efiboot.img
initrd = images/pxeboot/initrd.img
kernel = images/pxeboot/vmlinuz

[images-xen]
initrd = images/pxeboot/initrd.img
kernel = images/pxeboot/vmlinuz

[release]
name = Red Hat Enterprise Linux
short = RHEL
version = 8.1.0

[stage2]
mainimage = images/install.img

[tree]
arch = x86_64
build_timestamp = 1571146127
platforms = x86_64,xen
variants = BaseOS

[variant-BaseOS]
id = BaseOS
name = BaseOS
packages = Packages
repository = .
type = variant
uid = BaseOS

  18. Open the /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/appstream/kickstart/treeinfo file for editing.

  19. In the [general] section, make the following changes:

    • Change packagedir = AppStream/Packages to packagedir = Packages

    • Change repository = AppStream to repository = .

    • Change variants = AppStream,BaseOS to variants = AppStream

  20. In the [tree] section, change variants = AppStream,BaseOS to variants = AppStream

  21. In the [variant-AppStream] section, make the following changes:

    • Change packages = AppStream/Packages to packages = Packages

    • Change repository = AppStream to repository = .

  22. Delete the following sections from the file: [checksums], [images-x86_64], [images-xen], [media], [stage2], [variant-BaseOS].

  23. Save and close the file.

  24. Verify that the /var/www/html/pub/sat-import/content/dist/rhel8/8.1/x86_64/appstream/kickstart/treeinfo file has the following format:

    [general]
; WARNING.0 = This section provides compatibility with pre-productmd treeinfos.
; WARNING.1 = Read productmd documentation for details about new format.
arch = x86_64
family = Red Hat Enterprise Linux
name = Red Hat Enterprise Linux 8.1.0
packagedir = Packages
platforms = x86_64,xen
repository = .
timestamp = 1571146127
variant = AppStream
variants = AppStream
version = 8.1.0

[header]
type = productmd.treeinfo
version = 1.2

[release]
name = Red Hat Enterprise Linux
short = RHEL
version = 8.1.0

[tree]
arch = x86_64
build_timestamp = 1571146127
platforms = x86_64,xen
variants = AppStream

[variant-AppStream]
id = AppStream
name = AppStream
packages = Packages
repository = .
type = variant
uid = AppStream

  25. If you do not plan to use the mounted binary DVD ISO image, unmount and remove the directory:

    # umount /mnt/iso
# rmdir /mnt/iso

  26. In the orcharhino management UI, enable the Kickstart repositories.

The text and illustrations on this page are licensed by ATIX AG under a Creative Commons Attribution–Share Alike 3.0 Unported ("CC-BY-SA") license. This page also contains text from the official Foreman documentation which uses the same license ("CC-BY-SA").