Getting Started with Simple Content Access
Abstract
Preface
This guide introduces simple content access, explains your requirements and responsibilities, and walks you through activating it.
Chapter 1. About simple content access
Introduction to simple content access including what it is, its benefits and limitations, and how it changes tools and workflows.
1.1. About simple content access
Simple content access is a set of capabilities that enables a change in the way Red Hat manages its subscription and entitlement enforcement model. This model of content access and consumption results in fewer barriers to content deployment.
The process of migrating Red Hat accounts and organizations that primarily use Red Hat Subscription Management for subscription management to use simple content access begins on October 25, 2024, and will be complete in November 2024.
For Red Hat accounts and organizations that primarily use Satellite, versions 6.15 and earlier can continue to support an entitlement-based workflow for the remainder of the supported lifecycle for those versions. However, Satellite version 6.16 and later versions will support only the simple content access workflow.
With simple content access, the enforcement model changes from a per-system requirement, where you must attach a subscription to a system before you can access content, to a per-organization and per-account requirement, where you can access content on a system without attaching a subscription to that system.
Because of the added freedom and flexibility to consume content that simple content access provides, and in the absence of strict entitlement enforcement from the classic entitlement-based subscription model, it becomes important for you to keep track of how you are using your subscriptions. With the subscriptions service, Red Hat provides additional tooling to help you with tracking and compliance. The subscriptions service is a reporting solution that provides account-wide visibility of both subscription usage and utilization and aids in self-governance of your entire subscription profile.
When simple content access and the subscriptions service are used together, they enable a different and more flexible subscription experience. Overall, this experience removes or improves many of the high-overhead and complicated business processes that are associated with the classic Red Hat entitlement-based enforcement subscription model:
- Time-consuming processes that require multiple Red Hat tools and many steps for content to be accessed and used.
- Overly complex and sometimes extremely manual processes that are needed to complete subscription reporting.
- Processes to resolve problems related to accessing content, under- and over-deployment, renewals, and so on, that resulted in significant business impact to Red Hat customers, including being blocked from content access.
You can choose to use neither, either, or both of these services. However, simple content access and the subscriptions service are designed as complementary services and function best when they are used in tandem.
Additional resources
1.2. Benefits and limitations of simple content access
The foundational benefit of simple content access is that it offers a less restrictive and more flexible way to consume your Red Hat subscriptions. However, this flexibility does include some limitations.
- Benefits
- Simple content access enables a better experience with the tools that help you manage subscriptions. By removing the need to attach subscriptions at the system level, simple content access streamlines the process of registering systems, enabling repositories, and consuming content so that you can more easily install the products that you want where you want them.
- Limitations
Although simple content access allows much more freedom in the consumption of your subscriptions, you should note the following limitations for content access:
Simple content access does not provide access to repositories that you have not previously purchased.
- For example, if you have subscriptions for RHEL only, simple content access does not provide access to any other Red Hat product subscription, such as a Red Hat JBoss Enterprise Application Platform subscription.
Simple content access does not provide access within Satellite to repositories that are not included in the subscription manifest. The subscription manifest contains the following information:
- A list of subscriptions and attached quantities.
- Metadata and certificates that Satellite uses to synchronize the repositories.
1.3. How simple content access changes subscription tools and workflows
Simple content access is designed to improve the overall customer subscription experience by eliminating cumbersome and confusing parts of the subscription management workflow. With simple content access enabled, that action changes not only the user workflows that manage your subscriptions and provide access to content, but it also changes the way that the various subscription tools themselves operate. These tools include Red Hat Satellite, Red Hat Subscription Management, the subscription-manager command line tool, activation keys, virt-who, and others.
For the most recent information that describes the differences between the old entitlement-based workflow and the simple content access workflow, see the information about operational changes in Additional resources.
Additional resources
Chapter 2. Requirements and your responsibilities
Review the hardware and software requirements and your responsibilities before you use the service.
2.1. Requirements
To begin using simple content access, you must meet the following software requirements.
For simple content access with Red Hat Subscription Management:
- Simple content access enabled within Red Hat Subscription Management.
For simple content access with Red Hat Satellite:
Satellite 6.14 or later (versions that are under full or maintenance support). Earlier versions of Satellite can be used with simple content access, but migration to a supported version of Satellite is recommended.
NoteFor Satellite version support information, see the Red Hat Satellite Product Life Cycle life cycle and update policy document.
Simple content access enabled, where required.
- Satellite version 6.16 supports only simple content access. Manual enablement of simple content access is not required for versions 6.16 and later.
- Satellite versions 6.15 and 6.14 (and 6.13, reaching end of life (EOL) in November 2024), simple content access enabled for each Satellite organization. Any simple content access setting on the manifest is ignored; the setting on the Satellite organization takes precedence.
- Satellite versions 6.12 and earlier (EOL versions that are not supported), simple content access enabled for each allocation and manifest. In addition, enabled manifests must be refreshed for simple content access to take effect.
2.2. Your responsibilities
As you use simple content access, note the following agreements and contractual responsibilities that remain in effect:
Simple content access does not eliminate any contractual requirements between you and Red Hat. You are still required to ensure that your deployments are in accordance with any Red Hat contracts.
Chapter 3. Activate simple content access
Enabling simple content access with Red Hat Subscription Management and with Red Hat Satellite.
3.1. Enable simple content access with Red Hat Subscription Management
The process of migrating Red Hat accounts and organizations that primarily use Red Hat Subscription Management for subscription management to use simple content access begins on October 25, 2024 and will be complete in November 2024.
3.1.1. Enable simple content access for your Red Hat Subscription Management managed systems
Manual activation of simple content access is no longer necessary.
3.1.2. Complete post-enablement steps for Red Hat Subscription Management
After the migration for your Red Hat account and organization is complete and simple content access is enabled, review the articles in the Additional resources section for more information about using the simple content access mode and configuring and working with the services in the Hybrid Cloud Console.
- Ensure that you understand how this change to the simple content access mode affects the workflow that your organization uses. If you had any customized processes that relied upon artifacts from the old entitlement-based mode, such as checking for valid subscriptions on a per-system basis, these processes will need to be discarded or redesigned to be compatible with the new simple content access workflow.
Find out more about additional services in the Hybrid Cloud Console that can improve your subscription and system management processes and determine if you are taking advantage of them. See the Hybrid Cloud Console at the console URL in Additional resources to explore these services.
- Authorize your Red Hat organization’s users to access the services of the Red Hat Hybrid Cloud Console by setting up user groups, assigning roles, and doing other tasks in the role-based user access control (RBAC) system.
- Authorize your Red Hat organization’s users to view system inventory data with appropriate filtering by creating workspaces that classify systems into logical groups.
- Configure Hybrid Cloud Console notifications so that alerts about specific events in Hybrid Cloud Console services can go to a named group of users or go to applications, APIs, or webhooks for additional custom actions.
- Activate the subscriptions service, if this service is not already active, to begin account-wide usage reporting of Red Hat products.
Explore the capabilities, including subscription and system management capabilities, of the Hybrid Cloud Console and how workflows for some of these capabilities might have changed from the workflows that were previously available in the Red Hat Customer Portal at access.redhat.com:
- Tracking usage reporting for Red Hat products and variants on the product platforms pages of the subscriptions service.
- Tracking and managing your system infrastructure in the inventory service.
- Using activation keys to help with system registration, setting system purpose, and enabling repositories.
- Creating and exporting manifests for use within your Red Hat Satellite environment to find, access, and download content from the Red Hat Content Delivery Network.
- Determining whether the additional capabilities of Red Hat Lightspeed, including the advisor, vulnerability, remediation, patch, and other services are right for your environment.
The following articles are actively being updated to address customer questions and concerns during and after the account migration process that began on October 25, 2024.
3.2. Enable simple content access with Red Hat Satellite
For Satellite, new allocations and manifests have used simple content access by default since the release of Satellite 6.9. New Satellite organizations have used simple content access by default since the release of Satellite 6.13, where the setting on the organization overrides any setting on the manifest.
For Red Hat accounts and organizations that primarily use Satellite, versions 6.15 and earlier can continue to support an entitlement-based workflow for the remainder of the supported lifecycle for those versions. However, Satellite version 6.16 and later versions support only the simple content access workflow.
For the most recent information about the interactions of simple content access and specific versions of Satellite, see the transition article in Additional resources.
3.2.1. Enable simple content access on an existing Satellite allocation and manifest
For Satellite version 6.16, manual activation of simple content access is no longer necessary.
3.2.2. Complete post-enablement steps for Satellite
After you enable simple content access, the way that you interact with some subscription management tools, including Satellite, differs. You must make some changes in Satellite to accommodate these different workflows and the individual behaviors within them.
Configuring activation keys and refreshing manifests
When you change from the entitlement mode to the simple content access mode, workflows that rely on existing activation keys and manifests are affected.
- You must create new activation keys that contain only content-related functions and do not contain the subscription-related functions that relied on attaching subscriptions to individual systems through entitlements.
If you are using Satellite 6.13 or later, you must add the renewed subscriptions to a manifest and refresh it at the time of subscription renewal. If you are using Satellite 6.12 or earlier, after you enable simple content access on the manifest you must refresh it. Note that Satellite versions 6.13 and earlier are out of support.
NoteFor Satellite version support information, see the Red Hat Satellite Product Life Cycle document in Additional resources.
Updating host groups
Use the following steps to update each relevant host group to use the new activation keys. You can also perform these steps from the hammer command line interface.
- From the Satellite web UI navigation, click Configure > Host Groups.
- Click the host group that you want to update. Then click the Activation Keys tab.
- On the Activation Keys page, enter the new activation key for the host group, replacing the old activation keys. Click Reload data to confirm the activation key change for the host group.
- Click Submit to save the host group changes.
Reconfiguring hosts
For Red Hat Satellite, the new activation keys that you create for simple content access apply only to newly provisioned hosts. For existing hosts, you must do some reconfiguration and re-enable repositories.
When simple content access is enabled, all repositories are disabled by default if a host does not have a subscription attached. This default setting prevents conflicting repositories from being enabled when a host has access to repositories that span multiple operating system versions.
To do these changes, you can use the following commands as a snippet in a remote job that runs with the remote execution function of Red Hat Satellite. Comments are included in the following snippet to help you understand the series of tasks. You can also run these commands locally on each host, but using the bulk host management and remote execution capabilities of Red Hat Satellite during a maintenance window is more efficient.
# Get a list of all the currently enabled repos REPOS=$(subscription-manager repos --list-enabled | grep "Repo ID" | cut -f 2 -d ':' ) # (Optional) dump that list to a file in case of errors echo $REPOS >> ENABLED_REPOS.txt # Construct a command line to pass to 'subscription-manager repos' # so that we call it once, instead of once per repo. This would lower # the number of API calls and load on the Satellite. CMDLINE=$(echo $REPOS | sed 's/ / --enable /g') # Disable all the repos & Remove any existing entitlements subscription-manager repos --disable '*' subscription-manager remove --all # Call subscription-manager fresh to ensure that we have a content access cert # (which is the authorization method when SCA is enabled) subscription-manager refresh # Finally (re) enable the correct repos. subscription-manager repos --enable $CMDLINE
Completing additional post-enablement steps
After the migration for your Red Hat account and organization is complete and simple content access is enabled, review the articles in the Additional resources section for more information about using the simple content access mode and configuring and working with the services in the Hybrid Cloud Console.
- Ensure that you understand how this change to the simple content access mode affects the workflow that your organization uses. If you had any customized processes that relied upon artifacts from the old entitlement-based mode, such as checking for valid subscriptions on a per-system basis, these processes will need to be discarded or redesigned to be compatible with the new simple content access workflow.
Find out more about additional services in the Hybrid Cloud Console that can improve your subscription and system management processes and determine if you are taking advantage of them. See the Hybrid Cloud Console at the console URL in Additional resources to explore these services.
- Authorize your Red Hat organization’s users to access the services of the Red Hat Hybrid Cloud Console by setting up user groups, assigning roles, and doing other tasks in the role-based user access control (RBAC) system.
- Authorize your Red Hat organization’s users to view system inventory data with appropriate filtering by creating workspaces that classify systems into logical groups.
- Configure Hybrid Cloud Console notifications so that alerts about specific events in Hybrid Cloud Console services can go to a named group of users or go to applications, APIs, or webhooks for additional custom actions.
- Activate the subscriptions service, if this service is not already active, to begin account-wide usage reporting of Red Hat products.
Explore the capabilities, including subscription and system management capabilities, of the Hybrid Cloud Console and how workflows for some of these capabilities might have changed from the workflows that were previously available in the Red Hat Customer Portal at access.redhat.com:
- Tracking usage reporting for Red Hat products and variants on the product platforms pages of the subscriptions service.
- Tracking and managing your system infrastructure in the inventory service.
- Using activation keys to help with system registration, setting system purpose, and enabling repositories.
- Creating and exporting manifests for use within your Red Hat Satellite environment to find, access, and download content from the Red Hat Content Delivery Network.
- Determining whether the additional capabilities of Red Hat Lightspeed, including the advisor, vulnerability, remediation, patch, and other services are right for your environment.
The following articles are actively being updated to address customer questions and concerns during and after the account migration process that began on October 25, 2024.
Additional resources
- Transition of Red Hat’s subscription services to the Red Hat Hybrid Cloud Console (console.redhat.com)
- This content is not included.Transitioning Red Hat Subscription Management to the Hybrid Cloud Console
- Simple Content Access
- Red Hat Satellite Product Life Cycle
- This content is not included.Hybrid Cloud Console
Provide feedback on Red Hat documentation
We appreciate your feedback on our documentation. To provide feedback, open a Jira issue that describes your concerns. Provide as much detail as possible so that your request can be addressed quickly.
Prerequisites
- You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one.
Procedure
- Click the following link: This content is not included.Create Issue
- In the Summary text box, enter a brief description of the issue.
- In the Description text box, provide more details about the issue. Include the URL where you found the issue.
- Provide information for any other required fields. Allow fields that contain default information to remain at the defaults.
- Click Create to create the Jira issue for the documentation team.
Result
A documentation issue will be created and routed to the appropriate documentation team. Thank you for taking the time to provide feedback.