Note that only Activation Key Administrators can see this list. At this point, you may associate child channels and groups with the key so that systems registered with it automatically subscribe to them. To change information about a key, such as the channels or groups, click its description in the key list, make your modifications in the appropriate tab, and click the Update Key button. To disassociate channels and groups from a key, deselect them in their respective menus by Ctrl -clicking their highlighted names.
To remove a key entirely, click the delete key link in the top-right corner of the edit page. A system may be set to subscribe to a base channel during registration with an activation key. However, if the activation key specifies a base channel that is not compatible with the operating system of the systems, the registration fails.
A system is always allowed to subscribe to a custom base channel. To disable system activations with a key, unselect the corresponding checkbox under the Enabled column in the key list. The key can be re-enabled by selecting the checkbox. User management Certification Central. Register now Not registered yet? Here are a few reasons why you should be: Browse Knowledgebase articles, manage support cases and subscriptions, download updates, and more from one place.
View users in your organization, and edit their account information, preferences, and permissions. Manage your Red Hat certifications, view exam history, and download certification-related logos and documents. Edit your profile and preferences Your Red Hat account gives you access to your member profile, preferences, and other services depending on your customer status. Log out. Contact us. January 17, Rich Jerrido. This article was originally published on the Red Hat Customer Portal.
The information may no longer be current. Overview Activation keys are one of the more important features in the workflow of provisioning and registering hosts. Prerequisites It is important that you have read or understand the concepts as presented in: Subscription-manager for the former Red Hat Network User: Part 3 - Understanding virt-who Subscription-manager for the former Red Hat Network User: Part 4 - Understanding Subscription Manifests Subscription-manager for the former Red Hat Network User: Part 5 - working with subscriptions that require virt-who What is an activation key?
In the scope of this document, we'll discuss activation keys in Satellite 6. What properties can be set on an activation key? Release Version Release version 7. Environment Which Lifecycle Environment to subscribe the host to. Content View Which Content View will the host use.
Subscriptions Which subscriptions Red Hat or Custom to attach to the hosts. Auto attach Whether or not the auto attach process runs. Using multiple activation keys, ordering and precedence Given the number of options above and the variety of hosts that you may be deploying, a single activation key may not be sufficient to get the host registered and configured the way you like. These include: Subscriptions Host Collections Settings that influence the behavior of the key itself and these operate independently : Host Limit auto attach Auto attach behavior with Red Hat Subscriptions on activation keys When configuring a key with the intent of getting a Red Hat subscription attached, the presence or absence of Red Hat Subscriptions and the auto attach property will change how an activation key behaves.
This activation key type is VERY useful when provisioning virtual guests as it allows you to take advantage of the following behavior: If the hypervisor is known to the Subscription Management Platform, the virtual machine has been reported via virt-who, and an unlimited guest subscription is already attached to the hypervisor , the guest will consume the virtual guest pool that already exists for the hypervisor.
If the hypervisor is known to the Subscription Management Platform and the virtual machine has been reported via virt-who, but the hypervisor does not have a valid subscription, an unlimited guest subscription will get attached to the hypervisor which will cover itself and the virtual machine. If the hypervisor is known to the Subscription Management Platform, but the guest has NOT been reported via virt-who yet, the guest will consume a 24 hour temporary guest subscription. Use Case 3: Use ANY of a subset of subscriptions You can associate n subscriptions to a key, set the key to auto attach, and then auto attach will apply only to the listed subscriptions.
The table below illustrates these use cases: Auto attach? Has Red Hat Subscriptions? Lastly, by having activation keys that do one thing well and combining them, activation key sprawl is prevented, or at least reduced Since subscriptions grant access to content, it is recommended to create keys with the following workflow: - attach a valid subscription.
Case Study Example Corp. For example, a Red Hat Enterprise Linux 2. A key may specify either zero or one base channel. If specified, it must be a custom base channel. If not, the base channel corresponding to the system's Red Hat distribution is chosen. For instance, you may not subscribe a Red Hat Enterprise Linux 2. A key may specify any number of child channels. For each child channel, subscription is attempted. If the child channel matches the system's base channel, subscription succeeds.
If it does not, the subscription fails silently.
0コメント