Establish consistent patch baselines

You can filter the errata with content templates and apply them to registered systems in the Hybrid Cloud Console. The templates provide filtering and control on the systems. You also can use the same set of content templates to build custom images in Red Hat Lightspeed.

Content templates include product and architecture attributes. These attributes, and a date that you select, create a defined set of packages and errata. You can use these sets to build images, report on patching status, and control the content delivered to your registered systems. All content templates include base RHEL repositories, and you can choose to include additional Red Hat and custom repositories.

Repository snapshots capture the state of your repository at a point in time. Repositories are collections of Red Hat Package Manager files (RPMs) and metadata.

A content template consists of a set of repository snapshots that have the same version of Red Hat Enterprise Linux and the same system architecture. You select the snapshots to ensure that your systems have access only to specific package versions. Using the content templates, you can establish date-based patch baselines for your systems, and then use yum or dnf to perform updates to the systems.