Prevent content hosts from obtaining subscription from virt-who

Latest response

Hello All,

I'm working on building out a 6.7 satellite instance with VDC subscriptions and a virt-who config. My concern is that we have several RHEL servers that are not attached to our satellite instance as they are vendor-provided and we do not manage them, if one of these RHEL servers were to get placed on one of our vmware esxi hypervisors that has the VDC entitlement will it auto-subscribe that server somehow? I feel like this is not possible but can't find supporting documentation. What is required for vitrt-who to actually subscribe a system, does it have to be subscribed to satellite for all of this to work as well as the activation key with auto attached?

Also, bonus question if anybody knows, what happens if that vmware exsi hypervisor goes down, how long do we have to remove and re-add a VDC entitlement to a new hypervisor? or is there some grace period for the RHEL servers to stay entitled although there is no virt-who process reporting back say in 2-5 days?

Thanks all in advance.

Responses

" if one of these RHEL servers were to get placed on one of our vmware esxi hypervisors that has the VDC entitlement will it auto-subscribe that server somehow? "

Subscriptions are only attached to hosts known by the Satellite that require them. That is, if you report a hypervisor via virt-who and that hypervisor runs a RHEL system that isn't registered to that Satellite, neither the host nor the guest will get a subscription attached.

" What is required for vitrt-who to actually subscribe a system, does it have to be subscribed to satellite for all of this to work as well as the activation key with auto attached? "

To subscribe a system, it has to be

  • registered to the Satellite
  • have Red Hat products installed (usually RHEL).
  • If virtual AND you are using subscriptions which are sold per-hypervisor (such as 'RHEL for Virtual Datacenters'), reported via the virt-who process.

virt-who doesn't subscribe the system. It merely gathers the host/guest mapping (on which host does this guest reside) and reports it to Satellite (so that Satellite can do the subscription attachment).

" bonus question if anybody knows, what happens if that vmware exsi hypervisor goes down, how long do we have to remove and re-add a VDC entitlement to a new hypervisor? or is there some grace period for the RHEL servers to stay entitled although there is no virt-who process reporting back say in 2-5 days? "

As a general rule, once a system has a valid sub, it will continue to be able to use that sub until it expires or is no longer eligible to use it. If the virt-who process is offline, systems already built will continue to maintain their attached entitlements (and access to content) until those subscriptions expire. This is true, even for systems which are migrated to a new unsubscribed hypervisor. Once virt-who is back online, the virtual machines (which are using hypervisor level subs) will reconcile their subscriptions. New systems (systems that are being registered for the first time) are issued a 7-day 'temporary subscription' at registration time if the hypervisor they reside on is not known at registration.

Awesome, thank you so much for explaining this! Very insightful.

Also, I would take a look at Simple Content Access, the new subscription tool experience which is available in Satellite.