Bug 1387800

Summary: virt-who should report for every hypervisor detected its clusters name
Product: Red Hat Enterprise Linux 7 Reporter: Andrea Perotti <aperotti>
Component: virt-whoAssignee: Jiri Hnidek <jhnidek>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: medium Docs Contact:
Priority: low    
Version: 7.3CC: aperotti, csnyder, hsun, jhnidek, jsefler, khowell, lmiksik, mowens, ovasik, rjerrido, vanhoof, wpoteat, yuefliu
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1387341 Environment:
Last Closed: 2018-10-30 10:47:13 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:
Bug Depends On:    
Bug Blocks: 1353215, 1387341, 1420851, 1544891, 1546815, 1622133, 1635187    

Description Andrea Perotti 2016-10-21 23:12:35 UTC 
1. Proposed title of this feature request
Add cluster name into virt-who output.

3. What is the nature and description of the request? 
We need to know the cluster name of one hypervisor host.

4. Why does the customer need this? (List the business requirements here)
We assign the cluster name with a naming convention to understand if the cluster is a PROD or QA one.
We need therefore the cluster name because based on this information we assign the correct subscription based on the SLA.

5. How would the customer like to achieve this? (List the functional requirements here)
We would like to have the cluster name associated to the vmware guest.
In VMWare any host may be applied only to one cluster, therefore is acceptable also to have the cluster name associated with the host.
As we are planning to implement also RHEV, we would like to have a similar feature also for that Hypervisor.

6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
virt-who --print, and check in the output for the cluster name of the associated hypervisor host.

8. Does the customer have any specific timeline dependencies?
End of 2016

9. Is the sales team involved in this request and do they have any additional input?
no 

11. Would the customer be able to assist in testing this functionality if implemented?
Yes, sure
Comment 4 Chris Snyder 2017-08-03 14:59:36 UTC 
Andrea,

Is the request to add the cluster name for each hypervisor detected as a fact on the hypervisor consumer? As consumer facts are displayed in the Satellite web UI you should be able to then differentiate between clusters.
Comment 5 Andrea Perotti 2017-08-04 10:03:24 UTC 
Customer need this at virt-who level because it parse the output of if and work on assigning subscriptions via API based on the name of the cluster using external tools, like katello-attach-subscription [1] .

[1] https://github.com/RedHatSatellite/katello-attach-subscription
Comment 6 Chris Snyder 2017-08-07 14:39:09 UTC 
Andrea,

We'll use this RFE bug to represent the work done on virt-who to gather the cluster name for each hypervisor.

We'll also see what changes can/need to be made to the katello-attach-subscription tool.

Cheers,
Chris
Comment 29 errata-xmlrpc 2018-10-30 10:47:13 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3169