2.4. Application Life Cycles

The application life cycle in Red Hat Satellite 5 follows stages in a path. For example, applications might move along a path from "Development" to "Testing" to "General Availability". Each stage in Red Hat Satellite 5 uses System Definitions to manage systems at a particular point in the life cycle. A System Definition in Red Hat Satellite 5 is a set of Software Channels and Configuration Channels that are used in Kickstart Profiles.
The application life cycle of Red Hat Satellite 5. System Definitions move along a path to General Availability. Note the new version (v2) of the System Definition for the Development stage. This version will eventually move along the application life cycle path, replacing the old version (v1).

Figure 2.6. The Application Life Cycle of Red Hat Satellite 5

The Red Hat Satellite 6 application life cycle is broken up into two key components: Life Cycle Environments and Content Views.
The application life cycle is divided into life cycle environments, which mimic each stage of the life cycle. These life cycle environments are linked in an environment path. You can promote content along the environment path to the next life cycle stage when required. For example, if development completes on a particular version of an application, you can promote this version to the testing environment and start development on the next version.
An environment path containing four environments, including the base Library environment. Each content view version can be promoted through each environment in the path.

Figure 2.7. An Environment Path Containing Four Environments.

Content views are managed selections of content, which contain one or more repositories (yum / puppet) with optional filtering. These filters can be either inclusive or exclusive, and tailor a system view of content for lifecycle management. They are used to customize content to be made available to client systems.
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.

Figure 2.8. Creating New Versions of a Content View

Published content views are used with life cycle environments.