Este conteúdo não está disponível no idioma selecionado.
Chapter 5. Content access control for Satellite hosts
Satellite provides a robust set of strategies for controlling what content is accessible to your hosts. You can restrict content access by using core mechanisms, such as content views, lifecycle environments, and content overrides. You can use activation keys to apply these content access controls during host registration.
5.1. Content access strategies Copiar o linkLink copiado para a área de transferência!
To give hosts access to a specific subset of the content managed by Satellite, you can use the following strategies.
Red Hat recommends considering implementing the strategies in the order as listed here:
- Content views and lifecycle environments
Use content views and lifecycle environments, incorporating content view filters as needed.
For more information about content views, see Chapter 7, Managing content views.
For more information about lifecycle environments, see Chapter 6, Managing application lifecycles.
- Content overrides
By default, content hosted by Satellite can be either enabled or disabled. In custom products, repositories are always disabled by default, while Red Hat products can be either enabled or disabled by default depending on the specific repository. Enabling a repository gives the host access to the repository packages or other content, allowing hosts to download and install the available content.
If a repository is disabled, the host is not able to access the repository content. A content override provides you with the option to override the default enablement value of either Enabled or Disabled for any repository. You can add content overrides to hosts or activation keys.
For more information about adding content overrides to hosts, see Enabling and Disabling Repositories on Hosts in Managing hosts.
For more information about adding content overrides to activation keys, see Section 10.7, “Enabling and disabling repositories on activation key”.
- Content view environments
- Assign hosts to multiple content view environments to provide access to content from more than one content view. For more information about multiple content view environments, see Chapter 8, Managing content view environments.
- Composite content views
- You can use composite content views to combine and give hosts access to the content from multiple content views. For more information about composite content views, see Section 7.18, “Creating a composite content view by using Satellite web UI”.
- Architecture and operating system version restrictions
-
In custom products, you can set restrictions on the architecture and operating system versions for
yumrepositories on which the product will be available. For example, if you restrict a custom repository to Red Hat Enterprise Linux 9, it is only available on hosts running Red Hat Enterprise Linux 9. Architecture and operating system version restrictions hold the highest priority among all other strategies. They cannot be overridden or invalidated by content overrides, changes to content views, or changes to lifecycle environments. For this reason, Red Hat recommends considering the other strategies mentioned before that use architecture or operating system version restrictions. Red Hat repositories set architecture and operating system version restrictions automatically. - Release version
- Certain Red Hat repositories, such as the Red Hat Enterprise Linux dot release repositories, include a Release version in their repository metadata. The release version is then compared with the release version specified in the System purpose properties of the host. Access to content may be limited or restricted based on this comparison. For more information about setting system purpose attributes, see Editing the system purpose of a host in Managing hosts.
5.2. Conditions for content availability Copiar o linkLink copiado para a área de transferência!
A host can access a package or repository only when all of the following conditions are true.
- The repository is included in the content view environments of the host.
- The content view of the host has been published after the repository was added to it.
- The repository has not been filtered out by a content view filter.
- The repository is enabled by default or overridden to Enabled by using a content override.
- The repository has no architecture or operating system version restrictions or it has architecture or operating system version restrictions that match the host.
- For certain Red Hat repositories either no release version is set or the release version matches that of the host.
5.3. Activation keys and content access Copiar o linkLink copiado para a área de transferência!
Activation keys simplify the workflow for some of the content access strategies.
You can use activation keys to perform the following actions:
- Assign hosts to content view environments.
- Add content overrides to hosts.
- Set system purpose attributes on hosts, including a release version.
Activation keys only affect hosts during registration. If a host is already registered, you can change the content access individually for each host or through content host bulk actions.
Additional resources