Show Table of Contents
Chapter 3. Using Content Views
Content views are managed selections of content, which contain one or more repositories (yum, puppet, or containers) with optional filtering. These filters can be either inclusive or exclusive, and tailor a system view of content for life cycle management. They are used to customize content to be made available to client systems.
Keeping repositories for yum, Puppet, and containers in separate Content Views has the advantage that any updates to one repository only requires republishing the relevant Content View. You can use Composite Content Views to combine published Content Views for ease of management.
Figure 3.1. This diagram details the creation of new versions of a Content View. These content view versions are promoted along an environment path during the application life cycle.
Published content views are used with life cycle environments.
3.1. Creating a Content View
A user with administrator privileges can create content views for use within the life cycle environments.
Procedure 3.1. To Create a Content View:
- Log in as a Satellite administrator.
- Click→ .
- Specify the Name of the content view. The Label field is automatically populated when the Name field is filled out. Optionally, provide a description of the content view.
- Select the Composite Content View check box to combine a series of published content views into one and choose which content view.
NoteIf you select Composite Content View it will override any filtering and allow you to choose a group of published content views and bundle those views into a composite one.