Chapter 8. Managing Content Views

1. In the Satellite web UI, navigate to Content > Content Views and click Create New View.
2. In the Name field, enter a name for the view. Satellite automatically completes the Label field from the name you enter.
3. In the Description field, enter a description of the view.
4. Optional: if you want to solve dependencies automatically every time you publish this Content View, select the Solve Dependencies check box. 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.
5. Click Save to create the Content View.
6. In the Repository Selection area, select the repositories that you want to add to your Content View, then click Add Repositories.
7. Click Publish New Version and in the Description field, enter information about the version to log changes.
8. Click Save.
9. Optional: to force metadata regeneration on Yum repositories, from the Actions list for your Content View versions, select Regenerate Repository Metadata.

Creating a Content View with Hammer CLI

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 \
   --name "Example_Content_View" \
   --description "Example Content View" \
   --repository-ids 1,2 \
   --organization "My_Organization"

   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 \
   --name "Example_Content_View" \
   --description "Example 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 "Example_Content_View" \
   --organization "My_Organization" \
   --repository-id repository_ID

1. In the Satellite web UI, navigate to Content > Content Views, and select the Content View that contains the modules you want to view.
2. Click the Versions tab and select the Content View version that you want to view.
3. Click the Module Streams tab to view the module streams that are available for the Content View.
4. Use the Filter field to refine the list of modules.
5. To view the information about the module, click the module.

1. In the Satellite web UI, navigate to Content > Content Views and click Create New View.
2. In the Name field, enter a name for the view. Red Hat Satellite 6 automatically completes the Label field from the name you enter.
3. In the Description field, enter a description of the view.
4. Click Save to complete.
5. In the Repository Selection area, select the repositories that you want to add to your Content View, then click Add Repositories.
6. Click the Puppet Modules tab, then click Add New Module.
7. Search for the module that you want to add and click Select a Version.
8. Navigate to the entry for Use Latest and click Select Version in the Actions column.
9. To publish, click the Versions tab and click Publish New Version. In the Description field, enter a description to log the changes and click Save.

1. promote_or_remove_content_views
2. promote_or_remove_content_views_to_environment.

1. In the Satellite web UI, navigate to Content > Content Views and select the Content View that you want to promote.
2. Click the Versions tab for the Content View.
3. Select the version that you want to promote and in the Actions column, click Promote.
4. Select the environment where you want to promote the Content View, and click Promote Version.
5. Click the Promote button again. This time select the Testing environment and click Promote Version.
6. Finally click on the Promote button again. Select the Production environment and click Promote Version.

1. To promote a selected Content View version from Library across all life cycle environments within an organization, run the following Bash script:

   ORG="Your_Organization"
   CVV_ID=3
   
   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

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

   # hammer content-view version info --id 3

1. In the Satellite web UI, navigate to Content > Content Views and click Create New View.
2. In the Name field, enter a name for the view. Red Hat Satellite 6 automatically completes the Label field from the name you enter.
3. In the Description field, enter a description of the view.
4. Select the Composite View? check box to create a Composite Content View.
5. Optional: select the Auto Publish check box if you want the Composite Content View to be republished automatically when a Content View is republished.
6. Click Save.
7. In the Add Content Views area, select the Content Views that you want to add to the Composite Content View, and then click Add Content Views.
8. Click Publish New Version to publish the Composite Content View. In the Description field, enter a description and click Save.
9. Click Promote and select the lifecycle environments to promote the Composite Content View to, enter a description, and then click Promote Version.

For CLI Users

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 component Content View to the Composite Content View. You must include the Content View Version ID and use the --latest option. To include multiple component Content Views to the Composite Content View, repeat this step for every Content View you want to include:

   # hammer content-view component add \
   --component-content-view-id Content_View_Version_ID \
   --latest \
   --composite-content-view "Example_Composite_Content_View"

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"

1. In the Satellite web UI, navigate to Administer > Settings and click the Content tab.
2. Locate the Content View Dependency Solving Default, and select Yes.

1. In the Satellite web UI, navigate to Administer > Settings and click the Content tab.

2. Locate the Content View Dependency Solving Algorithm and select one of the following options:

   • To add the package that resolves the dependency only if it does not exist in the repository, select Conservative.
   • To add the package that resolves the dependency regardless of whether or not it exists in the repository, select Greedy.

1. In the Satellite web UI, navigate to Content > Content Views and select a Content View.
2. Navigate to Yum Content > Filters and click New Filter.
3. In the Name field, enter a name for your filter.
4. From the Content Type list, select the content type that you want to filter. Depending on what you select for the new filter’s content type, different options appear.
5. From the Inclusion Type list, select either Include or Exclude.
6. In the Description field, enter a description for the filter, and click Save.
7. Depending on what you enter for Content Type, add rules to create the filter that you want.
8. Click the Affected repositories tab to select which specific repositories use this filter.
9. Click Publish New Version to publish the filtered repository. In the Description field, enter a description of the changes, and click Save.

For CLI Users

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"