Activation Keys provide a mechanism to define properties that may be applied to Content Hosts during registration. This includes properties such as:
The following is a high-level summary of the Activation Key features:
To create a new key,
Name: This required option is used to identify the activation key to command line tools, such as subscription-manager.
Content Host Limit: This option will control how many Content Hosts may be registered using the key. An “unlimited” value will not place any limits on usage. Specifying a quantity will limit the number of registered content hosts. Registering with an activation key consumes one of the available limit quantity, while unregistering makes it available again. (i.e. this quantity is not a usage counter but a limit of actively registered content hosts)
Description: A free form text field that can be used to store a description of the key for later reference or for pseudo-tagging that can be used to search.
Environment and Content View: Although optional, at least one activation key used during registration must specify a content view. Activation keys are used in the order specified to subscription-manager meaning the last activation key with a content view takes precedence.
The following example would use CV_B’s content view:
subscription-manager register --org Default_Organization --activationkey NO_CV --activationkey CV_A --activationkey CV_B
subscription-manager register --org Default_Organization --activationkey NO_CV,CV_A,CV_B
For registration to succeed, at least one activation key must be successfully applied. For an activation key to succeed, at least one of the listed subscriptions must be successfully attached to the registering content host.
To add subscriptions to a key:
The Auto-Attach setting controls how the group of subscriptions are processed during registration.
When ‘Auto-Attach’ is enabled but no subscriptions are added to the activation key, subscriptions will be automatically added to cover the installed products. This is equivalent to passing the ‘–auto-attach’ flag to the subscription-manager command:
subscription-manager register --org=Default_Organization --auto-attach
When ‘Auto-Attach’ is enabled and subscriptions are listed for the activation key, two things will happen. First all subscriptions for custom products will be attached to the registering content host. Second, the group of Red Hat subscriptions will be attached as needed to cover the content host’s installed Red Hat products. This is most commonly used when there is a group of similar subscriptions (eg. several Red Hat Enterprise Linux from different contracts, or guest subscriptions from different hypervisors) and which one used is not important. Katello’s subscription tooling, Candlepin, will automatically choose the minimal proper subscriptions from the group.
Finally, when ‘Auto-Attach’ is disabled, all subscriptions on the activation key will attached to the registering content host, regardless of whether needed to cover an installed product or not. For example, adding an OpenStack Platform subscription would then allow that product to be installed after registration.
To change repository enablement settings using a key:
View current settings:
Change current settings:
To add Host Collections to a key:
The simplest form of registering a content host with an activation key is this:
subscription-manager register --org=Default_Organization --activationkey=$KEY_NAME
Note that modifying an activation key does not change anything on content hosts previously registered with the key.
Foreman 1.16.0 is now available, featuring Puppet 5 support, Netgroup LDAP authentication, a more performant Host API, VMWare SCSI controllers with per -disc configuration and many other enhancements. Read all about the changes in the release notes, and follow the quick start to install it.
A new bug fix release for Foreman 1.15 is available. See the Foreman 1.15.6 release notes for more details.