Procedure

1. In the Satellite web UI, navigate to Content > Activation keys and click Create Activation Key.
2. In the Name field, enter the name of the activation key.
3. Ensure the Unlimited Hosts check box is selected. Alternatively, if you want to set a limit, clear the Unlimited hosts check box, and in the Limit field, enter the maximum number of virtual machines you can register with the activation key.
4. In the Description field, enter a description for the activation key.
5. From the Environment list, select the environment to use.
6. From the Content View list, select a Content View to use.
7. Click Save.
8. When the new activation key appears in the Activation Keys window, click the name of the key.
9. Click the Subscriptions tab.
10. Ensure that Auto-Attach is set to Yes. If it is not, click the edit icon, select the check box, and click Save.

For CLI Users

1. Create the activation key:

   # hammer activation-key create \
   --name "VM_Activation_Key" \
   --unlimited-hosts \
   --description "For VMs to inherit a VDC Subscription" \
   --lifecycle-environment "Environment_Name" \
   --content-view "CV_Name" \
   --organization "My_Organization"

2. Enable auto-attach on the activation key:

   # hammer activation-key update --name "VM_Activation_Key" \
   --organization "My_Organization" --auto-attach true

Procedure

1. In the Satellite web UI, navigate to Hosts > Content Hosts.
2. In the Content Hosts list, select the check box next to the name of each hypervisor you want to attach the subscription to.
3. From the Select Action list, select Manage Subscriptions.
4. In the Content Host Bulk Subscriptions window, select a host-based subscription, then click Add Selected.

For CLI Users

1. On Satellite Server, list the available subscriptions to find the host-based subscription’s ID:

   # hammer subscription list \
   --organization-id organization_id

2. Attach the host-based subscription to a hypervisor:

   # hammer host subscription attach \
   --host host_name \
   --subscription-id subscription_id

   Repeat these steps for each hypervisor you plan to use.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Virt-who configurations.
2. Click Create Config. In the New Virt-who Config window, you can click the help icons for more information about each field.
3. Enter a Name for the configuration.

4. From the Hypervisor Type list, select your virtualization platform:

   • Red Hat Enterprise Linux Virtualization (KVM), Red Hat Virtualization, or Red Hat OpenStack Platform: libvirt
   • VMware vSphere: esx
   • Microsoft Hyper-V: hyperv
   • Note that the rhevm and xen hypervisor types are not supported, and the kubevirt hypervisor type is provided as a Technology Preview only.
5. In the Hypervisor Server field, enter the FQDN or IP address of the server this configuration applies to. For VMware vSphere, use the vCenter Server’s FQDN or IP address. For all other products, use the hypervisor’s FQDN or IP address.
6. In the Hypervisor Username field, enter the name of the virt-who user that you created on the hypervisor or virtualization manager.
7. In the Hypervisor Password field, enter the password for the virt-who user. This password is encrypted when you deploy the configuration. This field is not required when using the libvirt type.
8. From the Interval list, select how often virt-who requests new or updated virtual machine information. Because the virtual machines are granted temporary subscriptions for up to seven days, frequent queries are not required; you can select an interval that suits the size of your environment. Every 24 hours is suitable for most environments.
9. Enter the Satellite server FQDN.
10. From the Hypervisor ID list, select whether to identify the hypervisors in Satellite Server by their host name or UUID.

11. Select a Filtering option:

    • The default is Unlimited. All hypervisors covered by this configuration are queried by virt-who. Use this option if you do not have to limit which hypervisors are queried.
    • You can Whitelist or Blacklist hypervisors. For example, if some hypervisors only run Microsoft Windows Server virtual machines, those hypervisors do not need to be reported by virt-who.
12. If you selected Whitelist or Blacklist: In the Filter hosts or Exclude hosts field, enter a comma-separated list of hypervisors according to the selected Hypervisor ID. For example, if hypervisors are identified by their host name, they must be included or excluded by their host name. If a hypervisor’s name contains special characters, enclose it in quotation marks. Wildcards and regular expressions are supported. Note that when using regular expressions, backslashes must be escaped.
13. If you selected the esx type and Whitelist or Blacklist: In the Filter host parents or Exclude host parents field, enter a comma-separated list of clusters. Hypervisors in a whitelisted cluster are reported by virt-who. Hypervisors in a blacklisted cluster are not reported by virt-who. If a cluster name contains special characters, enclose it in quotation marks. Wildcards and regular expressions are supported. Note that when using regular expressions, backslashes must be escaped.
14. Optional: Select the Enable debugging output check box if you require debugging output for troubleshooting.

15. Optional: Enter an HTTP Proxy to use for communication between the server where virt-who is deployed and the hypervisors or virtualization managers. For example, http://proxy.example.com:3128.

    To use no proxy, leave this field blank; this has the same result as entering * in the Ignore Proxy field.

16. Optional: In the Ignore Proxy field, enter a comma-separated list of host names, IP addresses, or domains to bypass existing proxy settings.
17. Click Submit.

Procedure

1. Configure the virtual machine to register with Satellite Server:

   # yum install http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm

2. Register the virtual machine using the auto-attach activation key:

   # subscription-manager register --org=organization_label \
   --activationkey=activation_key_name