Introduction to Content Management

In the context of orcharhino, content is defined as the software installed on systems. This includes, but is not limited to, the base operating system, middleware services, and end-user applications. With orcharhino, you can manage the various types of content at every stage of the software life cycle.

orcharhino manages the following content:

Content management: This provides organizations with a method to store APT and YUM content and organize it in various ways.

Content Management Types Overview

With orcharhino, you can manage the following content types:

RPM Packages: Import RPM packages from any repository, for example from Red Hat, SUSE, and custom repositories. orcharhino Server downloads the RPM files and stores them locally. You can use these repositories and their RPM files in Content Views.
DEB Packages: Import DEB packages from repositories, for example for Debian or Ubuntu. You can also import single DEB packages or synchronize custom repositories. You can use these repositories and their DEB files in Content Views.
Provisioning Templates: You can provision hosts running EL based on synchronized content and Debian, Ubuntu, or SUSE Linux Enterprise Server based on local installation media. orcharhino contains predefined AutoYaST, kickstart, and Preseed templates as well as the ability to create your own, which are used to provision systems and customize the installation.

You can also manage other types of custom content in orcharhino. For example:

ISO and KVM Images: Download and manage media for installation and provisioning. For example, orcharhino downloads, stores, and manages ISO images and guest images for specific Alma Linux and non-Red Hat operating systems.
OSTree: You can import OSTree branches and publish this content to an HTTP location for consumption by OSTree clients.

You can use the procedure to add custom content for any type of content you require, for example, SSL certificates and OVAL files.

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