Chapter 9. Managing content views and content view environments

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.
8. On 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.
9. Click Publish new version and in the Description field, enter information about the version to log changes.
10. Optional: Enable a promotion path by clicking Promote and select one or more lifecycle environments to promote the new version to.
11. Click Next.
12. On the Review details page, review the environments you are trying to publish.
13. Click Finish.

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 My_Repository_ID_1,My_Repository_ID_2

3. Optional: Add another repository to your content view:

   $ hammer content-view add-repository \
   --name "My_Content_View" \
   --organization "My_Organization" \
   --repository-id My_Repository_ID_3

4. Publish the content view:

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

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

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Select the content view you want to copy.
3. Open the options menu 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, Content > Lifecycle > Content Views.
2. Select your content view.
3. Click on a published version.
4. Click Module Streams to view the module streams that are available for the Content Types.
5. Use the Search field to search for specific modules.
6. To view the information about the module, click the module and its corresponding tabs to include Details, Repositories, Profiles, and Artifacts.

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

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 options icon, and click Promote.
4. Select the environment where you want to promote the content view and click Promote.

Procedure

1. Allow the MCP server to trigger content view publish and promote actions:

   $ podman run --interactive --tty --publish 127.0.0.1:8080:8080 \
     --volume Path_to_My_CA_Bundle:/app/ca.pem:ro,Z \
     registry.redhat.io/satellite/foreman-mcp-server-rhel9:6.18 \
     --foreman-url https://satellite.example.com \
     --allowed-cv-actions "publish,promote"

   For more information, see Deploying the MCP server for Satellite in Managing hosts.

2. Type a prompt in your AI application to list content views:

   Show a list of content views on my Satellite.

3. The MCP server will return a list of content views to the AI application. Review the information.
4. Type a prompt in your AI application to publish a new version of the content view or to promote the content view to an environment. Review all the steps that the AI application performs.

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. Click Add RPM rule.
10. Enter a name, architecture, and version.
11. Click Add rule.
12. Select if you want the filter to Apply to subset of repositories or Apply to all repositories in the CV.
13. Click Publish new version to publish the filtered content view.
14. Optional: In the Description field, enter a description of the changes.
15. Optional: Select Promote to promote your filtered content view to a lifecycle environment.
16. Click Finish to publish a new version of the content view.

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

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. Open the options menu 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. List versions of your content view:

   $ hammer content-view info \
   --name "My_Content_View_Name" \
   --organization-id My_Organization_ID

2. Delete content view versions:

   $ hammer content-view remove \
   --content-view-version-ids My_Content_View_Version_ID_1,My_Content_View_Version_ID_2 \
   --id My_Content_View_ID

Procedure

1. Optional: View your content view versions:

   $ hammer content-view info \
   --name "My_Content_View_Name" \
   --organization-id My_Organization_ID

2. Clean up content view versions:

   $ hammer content-view purge \
   --name "My_Content_View_Name" \
   --organization-id My_Organization_ID \
   --versions-to-keep My_Number_Of_Versions_To_Keep

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.

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. Click Create content view.
3. In the Create content view window, enter a name for the content view in the Name field. Satellite automatically completes the Label field from the name you enter.
4. Optional: In the Description field, enter a description of the content view.
5. On the Type tab, select Rolling content view.
6. Optional: In the Lifecycle Environments field, assign your rolling content view to your lifecycle environments.
7. Click Create content view.
8. Click Show repositories.
9. Select the repositories that you want to add to your rolling content view.
10. Click Add repositories to add all selected repositories to your rolling content view.

Procedure

1. List all available lifecycle environments:

   $ hammer lifecycle-environment list \
   --fields id,name \
   --organization "My_Organization"

2. List all available repositories to identify IDs of repositories to add to your rolling content view:

   $ hammer repository list \
   --fields id,name,product \
   --organization "My_Organization"

3. Create your rolling content view:

   $ hammer content-view create \
   --lifecycle-environment-ids My_List_Of_Lifecycle_Environment_IDs \
   --name "My_Rolling_Content_View" \
   --organization "My_Organization" \
   --repository-ids My_List_Of_Repository_IDs \
   --rolling

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Select your rolling content view.
3. Select the Details tab.
4. In the Lifecycle Environments field, assign your rolling content view to your lifecycle environments.
5. Click Save Environments to submit your changes to Satellite.

Procedure

1. List all content views:

   $ hammer content-view list \
   --fields "content view id,name" \
   --organization "My_Organization"

2. Assign your rolling content view to lifecycle environments:

   $ hammer content-view update \
   --id My_Rolling_Content_View_ID \
   --lifecycle-environment-ids My_List_Of_Lifecycle_Environment_IDs \
   --organization "My_Organization"

   If you want to remove your rolling content view from all lifecycle environments, pass an empty list.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Select the hosts to which you want to assign content view environments.
3. Click the hosts table menu icon and select Manage content > Content view environments.

4. Edit the content view environments as needed.

   • Click Remove to remove a content view environment.
   • Click Add content view environment to assign an additional content view environment.
   • Drag and drop the content view environments to change their order.
5. Click Save.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host to which you want to assign content view environments.
3. On the the Content view environments card, click Assign content view environments.

4. Edit the content view environments as needed.

   • Click Remove to remove a content view environment.
   • Click Assign another content view environment to assign another content view environment.
   • Drag and drop the content view environments to change their order.
5. Optional: Select Update the host immediately via remote execution to update the host immediately.
6. Click Save.

Procedure

1. List available content view environments in your organization:

   $ hammer content-view-environment list --organization "My_Organization"

   Record the labels of the environments you want to assign to the host.

2. Assign the content view environments to the host:

   $ hammer host update \
   --content-view-environments="Library/along_cv,LCE_XYZ/CV1" \
   --name "server.example.com" \
   --organization-id My_Organization_ID

Procedure

1. List available content view environments:

   # subscription-manager environments --list

   Record the names of the environments you want to assign to the host.

2. Assign the content view environments to the host:

   # subscription-manager environments --set My_Content_View_Environment_1,My_Content_View_Environment_2