Bug 1415501

Summary:	Disambiguate RHEV section of the Virtual Instance Guide to make the configuration of virt-who more clear
Product:	Red Hat Satellite	Reporter:	Rich Jerrido <rjerrido>
Component:	Docs Virtual Instances Guide	Assignee:	Russell Dickenson <rdickens>
Status:	CLOSED CURRENTRELEASE	QA Contact:	csherrar
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2.6	CC:	adahms, egolov, fgarciad, kdixon, ktordeur, rdickens, rjerrido, swadeley
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-17 23:57:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rich Jerrido 2017-01-22 17:39:34 UTC

Description of problem:

The configuration of virt-who for RHEV is dependent on which type of hypervisor that is used:

- RHEV-H - As this hypervisor cannot be registered (to Satellite), rhevm mode is ideal here, as the hypervisor's Operating System never needs content (and thus won't need a subscription attached). This is effectively just like esx mode in virt-who. (One system polls the hypervisor management platform and gets host/guest mapping for ALL hypervisors)

- RVH-H and RHEL-Based Hypervisors - As these hypervisors can be registered (to Satellite) via subscription-manager, configuring virt-who in libvirt mode (on *each* hypervisor) makes the most sense here.

The virtual instance guide is unclear as to which configuration to use and why.

Comment 2 Andrew Dahms 2017-01-27 05:39:57 UTC

Assigning to Russell for review.