New with Satellite 6.2 - Virtual Instances Guide
The Virtual Instances Guide has been added to the documentation suite on release of Red Hat Satellite 6.2. It details how to connect Satellite 6 to all supported virtualization managers and hypervisors, including Red Hat Virtualization Manager.
It takes a modular approach to the necessary configuration steps, whether you have a single virtualization technology, or several. Example configurations are provided in each section, detailing the configuration of the virt-who agent.
Please look over the Virtual Instances Guide and provide feedback.
Responses
I configured virt-who correctly to connect to vcenter "virt-who -o" says "Sending update in hosts-to-guests mapping for config "***": x hypervisors and xx guests found"
But satellite 6.2.2 is not recognizing them as hypervisor => result => subscription problems
Do you have any advice
Red Hat
Active Contributor
324 points
When the client is provisioned for the first time, Satellite6 allocates a temporary subscription to it until the next time virt-who runs ( I think it runs once in sixty minutes). When virt-who runs and provides the hosts-to-guests mapping to Satellite, your client will automatically get the subscription from the unlimited pool corresponding to your hypervisor.
I just migrated to 6.2 for a customer.
He does have some KVM hypervisors running virtual machines in a pacemaker cluster.
I configured virt-who using the type "libvirt" as follow:
[kvm1]
server=kvm1
type=libvirt
username=virtwho
env=Library
hypervisor_id=hostname
owner=admin
[kvm2]
server=kvm2
type=libvirt
username=virtwho
env=Library
hypervisor_id=hostname
owner=admin
SSH keys have been deployed for user virtwho, and he has the "monitor" rules in polkit. The daemon seems to work as expected.
According this document, this configuration seems not to be supported by Red Hat. Am I correct?
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.