Bug 1387341

1. Proposed title of this feature request
Skip reporting whole clusters and all hypervisors in it, if there's no RHEL servers hoster in that cluster.

3. What is the nature and description of the request? 
We need to register only the needed physical hosts in a virtual infrastructure, not hypervisors hosts that are not containing any RHEL server.

4. Why does the customer need this? (List the business requirements here)
We have a mixed environment in which RHEL server may or may not be present in a specific cluster.
The cluster name and VM hosted number can change on a daily basis.
Our goal is to register all the hosts in the cluster if even just one RHEL server is present in the cluster.

5. How would the customer like to achieve this? (List the functional requirements here)
We need this information in virt-who output to have this information ready for candlepin (see case #01657273).
virt-who --print should show this information too.
We would like to have a way to also get the number of RHEL VM currently present in a cluster.

For vmware we have written this little snippet, published in:
https://github.com/peppos/vmware-list-vm:

if($cluster_view) {
     my $vm_list = Vim::find_entity_views(  view_type => 'VirtualMachine',
                                                                 begin_entity => $cluster_view,
                                                                 # modify this filter if you want print another VMs type
                                                                 filter => { 'config.guestFullName' => qr/Linux/ },
                                                                 properties => [ 'name' ] );

A better filter for obtain Red Hat Server could be obtained filtering per "Red Hat".


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 should show cluster name, vm name and numbers by cluster name

There are several possibilities in our opinion to have this information:
a) have the information cluster "aside" the host one (keep great compatibility, we need to glue the information outside)
b) add cluster information into each host (need to glue anyway the information, similar to the previous one)
c) rewrite the virt-who output in order to have the host contained within the cluster (there may be compatibility problems)

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