Chapter 7. Managing content views

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Click Create content view.
3. In the Name field, enter a name for the view. Satellite automatically completes the Label field from the name you enter.
4. In the Description field, enter a description of the view.
5. In the Type field, select a Content view or a Composite content view.
6. 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.
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.

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

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Select the content view you want to copy.
3. Click the vertical ellipsis icon and click Copy.
4. In the Name field, enter a name for the new content view and click Copy content view.

Procedure

1. In the Satellite 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.
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

1. promote_or_remove_content_views
2. promote_or_remove_content_views_to_environment.

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Select the content view that you want to promote.
3. Select the version that you want to promote, click the vertical ellipsis icon, and click Promote.
4. Select the environment where you want to promote the content view and click Promote.

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Click Create content view.
3. In the Create content view window, enter a name for the view in the Name field. Red Hat Satellite automatically completes the Label field from the name you enter.
4. Optional: In the Description field, enter a description of the view.
5. On the Type tab, select Composite content view.
6. 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.
7. Click Create content view.
8. 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.
9. In the Add content views window, select the version of each content view.
10. Optional: If you want to automatically update the content view to the latest version, select the Always update to latest version checkbox.
11. Click Add, then click Publish new version.
12. Optional: In the Description field, enter a description of the content view.
13. In the Publish window, set the Promote switch, then select the lifecycle environment.
14. 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"

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. From the list of content views, select the required content view.
3. On the Details tab, toggle Solve dependencies.

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Select a content view.
3. On the Filters tab, click Create filter.
4. Enter a name.
5. From the Content type list, select a content type.
6. From the Inclusion Type list, select either Include filter or Exclude filter.
7. Optional: In the Description field, enter a description for the filter.
8. Click Create filter to create your content filter.
9. Depending on what you enter for Content Type, add rules to create the filter that you want.
10. Select if you want the filter to Apply to subset of repositories or Apply to all repositories.
11. Click Publish New Version to publish the filtered repository.
12. Optional: In the Description field, enter a description of the changes.

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

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > 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.

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > 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.

Procedure

1. In the Satellite web 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 satellite.example.com/pulp/content/My_Organization/content_views/My_Content_View/My_Content_View_Version/.

   Note

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