Managing Content Views

orcharhino uses Content Views to allow your hosts access to a deliberately curated subset of content. To do this, you must define which repositories to use and then apply certain filters to the content. These filters include package filters, package group filters, errata filters, module stream filters, and container image tag filters. You can use Content Views to define which software versions a particular environment uses. For example, a Production environment might use a Content View containing older package versions, while a Development environment might use a Content View containing newer package versions.

Alternatively, a Default Organization View is an application-controlled Content View for all content that is synchronized to orcharhino. This type is useful if you want to register a host to orcharhino and access content using a subscription, without manipulating content views and lifecycle environments.

Each Content View creates a set of repositories across each environment, which orcharhino Server stores and manages. When you promote a Content View from one environment to the next environment in the application life cycle, the respective repository on orcharhino Server updates and publishes the packages.

Development Testing Production

Content View Version and Contents

Version 2 – example_software-1.1-0.noarch.rpm

Version 1 – example_software-1.0-0.noarch.rpm

Version 1 – example_software-1.0-0.noarch.rpm

The repositories for Testing and Production contain the example_software-1.0-0.noarch.rpm package. If you promote Version 2 of the Content View from Development to Testing, the repository for Testing regenerates and then contains the example_software-1.1-0.noarch.rpm package:

Development Testing Production

Content View Version and Contents

Version 2 – example_software-1.1-0.noarch.rpm

Version 2 – example_software-1.1-0.noarch.rpm

Version 1 – example_software-1.0-0.noarch.rpm

This ensures systems are designated to a specific environment but receive updates when that environment uses a new version of the Content View.

The general workflow for creating Content Views for filtering and creating snapshots is as follows:

  1. Create a Content View.

  2. Add one or more repositories that you want to the Content View.

  3. Optional: Create one or more filters to refine the content of the Content View. For more information, see Content Filter Examples.

  4. Optional: Resolve any package dependencies for a Content View. For more information, see Resolving Package Dependencies.

  5. Publish the Content View.

  6. Optional: Promote the Content View to another environment. For more information, see Promoting a Content View.

  7. Attach the content host to the Content View.

If a repository is not associated with the Content View, the file /etc/yum.repos.d/redhat.repo remains empty and systems registered to it cannot receive updates.

Hosts can only be associated with a single Content View. To associate a host with multiple Content Views, create a composite Content View. For more information, see Creating a Composite Content View.

Creating a Content View

Use this procedure to create a simple Content View. To use the CLI instead of the orcharhino management UI, see the CLI procedure.

Prerequisites

While you can stipulate whether you want to resolve any package dependencies on a Content View by Content View basis, you might want to change the default orcharhino settings to enable or disable package resolution for all Content Views. For more information, see Resolving Package Dependencies.

Procedure

  1. In the orcharhino management UI, navigate to Content > Content Views and click Create content view.

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

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

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

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

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

  7. Click Create content view.

Content View Steps

  1. Click Create content view to create the Content View.

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

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

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

  5. Click Next.

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

  7. Click Finish.

    Remove and Delete are similar but the Delete option deletes an entire Content View and the versions associated with that lifecycle environment. The Remove option allows you to choose which version you want removed from the lifecycle environment.

You can view the Content View in the Content Views window. To view more information about the Content View, click the Content View name. To register a host to your Content View, see Registering Hosts in Managing Hosts.

CLI procedure

  1. Obtain a list of repository IDs:

    $ hammer repository list --organization "My_Organization"

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

    For the --repository-ids option, you can find the IDs in the output of the hammer repository list command.

  3. Publish the view:

    $ hammer content-view publish \
--description "My_Content_View" \
--name "My_Content_View" \
--organization "My_Organization"

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

orcharhino Server creates the new version of the view and publishes it to the Library environment.

Best Practices for Content Views

  • There are two basic approaches to content views: Either create content views that contain everything needed for a certain type of host, for example a WebServer content view, which includes repositories for Red Hat Enterprise Linux-9, Apache-2.0, and PostgreSQL-7.1. Alternatively, create a content view each for Red Hat Enterprise Linux-9, Apache-2.0, and PostgreSQL-7.1 along with a composite content view WebServer, which includes all of these content views.

  • If you require daily updated content, use the content view Default Organization View. This contains the latest synchronized content from all repositories and is available in lifecycle environment Library.

  • Use content views and composite content views to assemble and structure lists of repositories. You can match different versions of content views or update specific content views when bundling them to a composite content view.

  • We recommend using composite content views only if you require more flexibility.

  • Making content management too small scale results in more manual work.

  • When using composite content views, publish the content views first, then the composite content views second. The more content views you bundle, the more work it becomes when making changes or updating content. We recommend making it as simple as possible and as complex as necessary.

  • Setting a lifecycle environment for content views is unnecessary if they are solely bundled to a composite content view.

  • Automate creating and publishing composite content views and lifecycle environments using Hammer scripts or Ansible Playbooks. Use cron jobs or recurring logics for more visibility. Recurring logics require SSH based access to orcharhino and the remote execution plugin.

  • We recommend adding the changes and date to the description of each published content view or composite content view version. The date shown in the management UI shows the latest action, for example promoting content to a different lifecycle environment, which is independent from the latest change to the actual content.

  • Publishing a new content view or composite content view creates a new major version. Incremental errata updates increment the minor version. Note that you cannot change or reset this counter.

Providing Content to Hosts

  • A content host receives content from your orcharhino Server or your orcharhino Proxies. It must be subscribed to orcharhino and is always associated to exactly one content view and exactly one lifecycle environment.

  • A subscription key consist of three parts: a lifecycle environment, a content view, and subscriptions. When you register a host using a given key, content is made available to the host.

  • Lifecycle environments describe the stage in which certain versions of content are available to hosts.

  • Content views are named and versioned collections of repositories.

For more information, see glossary.

Using Host Groups

  • A host group is a blueprint for both deploying hosts and managing existing hosts.

    • If you deploy a host using synced content as installation source, the lifecycle environment and content view are relevant for the content of the host.

    • For all other hosts, the content for the host depends on its activation key.

  • If you want to change the content a host is subscribed to, you need to resubscribe the host with a different activation key. Alternatively, you can change the lifecycle environment, content view, and subscriptions under Hosts > Content Hosts.

  • The information for an individual hosts displayed on Hosts > All Hosts is relevant if you want to re-build a host.

Viewing Module Streams

In orcharhino, you can view the module streams of the repositories in your Content Views.

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

Procedure

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

  2. Use the Search field to search for specific modules.

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

CLI procedure

  1. List all organizations:

    $ hammer organization list

  2. View all module streams for your organization:

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

Promoting a Content View

Use this procedure to promote Content Views across different lifecycle environments. To use the CLI instead of the orcharhino management UI, see the CLI procedure.

Permission Requirements for Content View Promotion

Non-administrator users require two permissions to promote a Content View to an environment:

  1. promote_or_remove_content_views

  2. promote_or_remove_content_views_to_environment.

The promote_or_remove_content_views permission restricts which Content Views a user can promote.

The promote_or_remove_content_views_to_environment permission restricts the environments to which a user can promote Content Views.

With these permissions you can assign users permissions to promote certain Content Views to certain environments, but not to other environments. For example, you can limit a user so that they are permitted to promote to test environments, but not to production environments.

You must assign both permissions to a user to allow them to promote Content Views.

Procedure

  1. In the orcharhino management UI, navigate to Content > Content Views and select the Content View that you want to promote.

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

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

Now the repository for the Content View appears in all environments.

CLI procedure

  • Promote the Content View using Hammer for each lifecycle environment:

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

    Now the database content is available in all environments.

  • Alternatively, you can promote Content Views across all lifecycle environments within an organization using the following Bash script:

    ORG="My_Organization"
CVV_ID=My_Content_View_Version_ID

for i in $(hammer --no-headers --csv lifecycle-environment list --organization $ORG | awk -F, {'print $1'} | sort -n)
do
   hammer content-view version promote --organization $ORG --to-lifecycle-environment-id $i --id $CVV_ID
done
Verification

  • Display information about your Content View version to verify that it is promoted to the required lifecycle environments:

    $ hammer content-view version info --id My_Content_View_Version_ID
Next steps

Composite Content Views Overview

A Composite Content View combines the content from several Content Views. For example, you might have separate Content Views to manage an operating system and an application individually. You can use a Composite Content View to merge the contents of both Content Views into a new repository. The repositories for the original Content Views still exist but a new repository also exists for the combined content.

If you want to develop an application that supports different database servers. The example_application appears as:

example_software

Application

Database

Operating System

Example of four separate Content Views:

  • Red Hat Enterprise Linux (Operating System)

  • PostgreSQL (Database)

  • MariaDB (Database)

  • example_software (Application)

From the previous Content Views, you can create two Composite Content Views.

Example Composite Content View for a PostgreSQL database:

Composite Content View 1 – example_software on PostgreSQL

example_software (Application)

PostgreSQL (Database)

Red Hat Enterprise Linux (Operating System)

Example Composite Content View for a MariaDB:

Composite Content View 2 – example_software on MariaDB

example_software (Application)

MariaDB (Database)

Red Hat Enterprise Linux (Operating System)

Each Content View is then managed and published separately. When you create a version of the application, you publish a new version of the Composite Content Views. You can also select the Auto Publish option when creating a Composite Content View, and then the Composite Content View is automatically republished when a Content View it includes is republished.

Repository restrictions

Docker repositories cannot be included more than once in a Composite Content View. For example, if you attempt to include two Content Views using the same docker repository in a Composite Content View, orcharhino Server reports an error.

Creating a Composite Content View

Use this procedure to create a composite Content View. To use the CLI instead of the orcharhino management UI, see the CLI procedure.

Procedure

  1. In the orcharhino management UI, navigate to Content > Content Views and click Create content view.

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

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

  4. On the Type tab, select Composite content view.

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

  6. Click Create content view.

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

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

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

  10. Click Add, then click Publish new version.

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

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

  13. Click Next, then click Finish.

CLI procedure

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

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

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

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

    • If you have the Always update to latest version option enabled for the Content View:

      $ hammer content-view component add \
--component-content-view-id Content_View_ID \
--composite-content-view "Example_Composite_Content_View" \
--latest \
--organization "My_Organization"

    • If you have the Always update to latest version option disabled for the Content View:

      $ hammer content-view component add \
--component-content-view-id Content_View_ID \
--composite-content-view "Example_Composite_Content_View" \
--component-content-view-version-id Content_View_Version_ID \
--organization "My_Organization"

  4. Publish the Composite Content View:

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

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

Content Filter Overview

Content Views also use filters to include or restrict certain RPM and DEB content. Without these filters, a Content View includes everything from the selected repositories.

There are two types of content filters:

Table 1. Filter Types
Filter Type Description

Include

You start with no content, then select which content to add from the selected repositories. Use this filter to combine multiple content items.

Exclude

You start with all content from selected repositories, then select which content to remove. Use this filter when you want to use most of a particular content repository but exclude certain packages, such as blacklisted packages. The filter uses all content in the repository except for the content you select.
Include and Exclude Filter Combinations

If using a combination of Include and Exclude filters, publishing a Content View triggers the include filters first, then the exclude filters. In this situation, select which content to include, then which content to exclude from the inclusive subset.

Content Types

There are also five types of content to filter:

Table 2. Content Types
Content Type Description

RPM

Filter packages based on their name and version number. The RPM option filters non-modular RPM packages and errata. Source RPMs are not affected by this filter and will still be available in the Content View.

Package Group

Filter packages based on package groups. The list of package groups is based on the repositories added to the Content View.

Erratum (by ID)

Select which specific errata to add to the filter. The list of Errata is based on the repositories added to the Content View.

Erratum (by Date and Type)

Select a issued or updated date range and errata type (Bugfix, Enhancement, or Security) to add to the filter.

Module Streams

Select whether to include or exclude specific module streams. The Module Streams option filters modular RPMs and errata, but does not filter non-modular content that is associated with the selected module stream.

Container Image Tag

Select whether to include or exclude specific container image tags.

Resolving Package Dependencies

orcharhino can add dependencies of packages in a Content View to the dependent repository when publishing the Content View. To configure this, you can enable dependency solving.

For example, dependency solving is useful when you incrementally add a single package to a Content View version. You might need to enable dependency solving to install that package.

However, dependency solving is unnecessary in most situations. For example:

  • When incrementally adding a security errata to a Content View, dependency solving can cause significant delays to Content View publication without major benefits.

  • Packages from a newer erratum might have dependencies that are incompatible with packages from an older Content View version. Incrementally adding the erratum using dependency solving might include unwanted packages. As an alternative, consider updating the Content View.

Dependency solving only considers packages within the repositories of the Content View. It does not consider packages installed on clients. For example, if a Content View includes only AppStream, dependency solving does not include dependent BaseOS content at publish time.

For more information, see Limitations to Repository Dependency Resolution in Managing Content.

Dependency solving can lead to the following problems:

Significant delay in Content View publication

orcharhino examines every repository in a Content View for dependencies. Therefore, publish time increases with more repositories.

To mitigate this problem, use multiple Content Views with fewer repositories and combine them into composite Content Views.

Ignored Content View filters on dependent packages

orcharhino prioritizes resolving package dependencies over the rules in your filter.

For example, if you create a filter for security purposes but enable dependency solving, orcharhino can add packages that you might consider insecure.

To mitigate this problem, carefully test filtering rules to determine the required dependencies. If dependency solving includes unwanted packages, manually identify the core basic dependencies that the extra packages and errata need.

Example 1. Combining exclusion filters with dependency solving

You want to recreate Red Hat Enterprise Linux 8.3 using Content View filters and include selected errata from a later Red Hat Enterprise Linux 8 minor release. To achieve this, you create filters to exclude most of the errata after the Red Hat Enterprise Linux 8.3 release date, except a few that you need. Then, you enable dependency solving.

In this situation, dependency solving might include more packages than expected. As a result, the host diverges from being a Red Hat Enterprise Linux 8.3 machine.

If you do not need the extra errata and packages, do not configure Content View filtering. Instead, enable and use the Red Hat Enterprise Linux 8.3 repository on the Content > Red Hat Repositories page in the orcharhino management UI.

Example 2. Excluding packages sometimes makes dependency solving impossible for DNF

If you make a Red Hat Enterprise Linux 8.3 repository with a few excluded packages, dnf update can sometimes fail.

Do not enable dependency solving to resolve the problem. Instead, investigate the error from dnf and adjust the filters to stop excluding the missing dependency.

Else, dependency solving might cause the repository to diverge from Red Hat Enterprise Linux 8.3.

Enabling Dependency Solving for a Content View

Use this procedure to enable dependency solving for a Content View.

Prerequisite
Procedure

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

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

  3. On the Details tab, toggle Solve dependencies.

Content Filter Examples

Use any of the following examples with the procedure that follows to build custom content filters.

Example 1

Create a repository with the base Red Hat Enterprise Linux packages. This filter requires a Red Hat Enterprise Linux repository added to the Content View.

Filter:

  • Inclusion Type: Include

  • Content Type: Package Group

  • Filter: Select only the Base package group

Example 2

Create a repository that excludes all errata, except for security updates, after a certain date. This is useful if you want to perform system updates on a regular basis with the exception of critical security updates, which must be applied immediately. This filter requires a Red Hat Enterprise Linux repository added to the Content View.

Filter:

  • Inclusion Type: Exclude

  • Content Type: Erratum (by Date and Type)

  • Filter: Select only the Bugfix and Enhancement errata types, and clear the Security errata type. Set the Date Type to Updated On. Set the Start Date to the date you want to restrict errata. Leave the End Date blank to ensure any new non-security errata is filtered.

Example 3

A combination of Example 1 and Example 2 where you only require the operating system packages and want to exclude recent bug fix and enhancement errata. This requires two filters attached to the same Content View. The Content View processes the Include filter first, then the Exclude filter.

Filter 1:

  • Inclusion Type: Include

  • Content Type: Package Group

  • Filter: Select only the Base package group

Filter 2:

  • Inclusion Type: Exclude

  • Content Type: Erratum (by Date and Type)

  • Filter: Select only the Bugfix and Enhancement errata types, and clear the Security errata type. Set the Date Type to Updated On. Set the Start Date to the date you want to restrict errata. Leave the End Date blank to ensure any new non-security errata is filtered.

Example 4

Filter a specific module stream in a Content View.

Filter 1:

  • Inclusion Type: Include

  • Content Type: Module Stream

  • Filter: Select only the specific module stream that you want for the Content View, for example ant, and click Add Module Stream.

Filter 2:

  • Inclusion Type: Exclude

  • Content Type: Package

  • Filter: Add a rule to filter any non-modular packages that you want to exclude from the Content View. If you do not filter the packages, the Content View filter includes all non-modular packages associated with the module stream ant. Add a rule to exclude all * packages, or specify the package names that you want to exclude.

Creating a Content Filter for Yum Content

You can filter Content Views containing Yum content to include or exclude specific packages, package groups, errata, or module streams. Filters are based on a combination of the name, version, and architecture.

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

For examples of how to build a filter, see Content Filter Examples.

Procedure

  1. In the orcharhino management UI, navigate to Content > Content Views and select a Content View.

  2. On the Filters tab, click Create filter.

  3. Enter a name.

  4. From the Content type list, select a content type.

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

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

  7. Click Create filter to create your content filter.

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

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

  10. Click Publish New Version to publish the filtered repository.

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

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

    You can promote this Content View across all environments.

CLI procedure

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

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

  3. Publish the Content View:

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

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

Deleting Multiple Content View Versions

You can delete multiple Content View versions simultaneously.

Procedure

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

  2. Select the Content View you want to delete versions of.

  3. On the Versions tab, select the checkbox of the version or versions you want to delete.

  4. Click the vertical ellipsis icon at the top of the list of Content Views.

  5. Click Delete to open the deletion wizard that shows any affected environments.

  6. If there are no affected environments, review the details and click Delete.

  7. If there are any affected environments, reassign any hosts or activation keys before deletion.

  8. Review the details of the actions.

  9. Click Delete.

Clearing the Search Filter

If you search for specific content types using keywords in the Search text box and the search returns no results, click Clear search to clear all the search queries and reset the Search text box.

If you use a filter to search for specific repositories in the Type text box and the search returns no results, click Clear filters to clear all active filters and reset the Type text box.

Standardizing Content View Empty States

If there are no filters listed for a content view, click Create filter. A modal opens to show you the next steps to create a filter. Follow these steps to add a new filter to create new content types.

Comparing Content View Versions

Use this procedure to compare Content View Version functionality for orcharhino.

Procedure

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

  2. Select a Content View whose versions you want to compare.

  3. On the Versions tab, select the checkbox next to any two versions you want to compare.

  4. Click Compare.

    The Compare screen has the pre-selected versions in the version dropdown menus and tabs for all content types found in either version. You can filter the results to show only the same, different, or all content types. You can compare different Content View versions by selecting them from the dropdown menus.

Distributing Archived Content View Versions

The setting Distribute archived content view versions enables hosting of non-promoted Content View version repositories in the orcharhino content web application along with other repositories. This is useful while debugging to see what content is present in your Content View versions.

Procedure

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

  2. Click the Content tab.

  3. Set the Distribute archived content view versions parameter to Yes.

  4. Click Submit.

    This enables the repositories of Content View versions without lifecycle environments to be distributed at orcharhino.example.com/pulp/content/My_Organization/content_views/My_Content_View/My_Content_View_Version/.

    Older non-promoted Content View versions are not distributed once the setting is enabled. Only new Content View versions become distributed.

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