Description of problem: Support for auto attach functionality for ESXi hypervisors in virt-who environment. The VDC subscription must be attached manually to each hypervisor reported by the virt-who. This is turning into very difficult task in environments with hundreds of hypervisors. Version-Release number of selected component (if applicable): Satellite 6.X Actual results: Each ESXi HV has to be subscribed manually. Expected results: VDC subscription will be attached automatically Additional info: Current workaround is using API which is very slow.
The following behavior is expected to work... 1. Don't assign a VDC to a hypervisor 2. Guest registers and then subscribes with --auto-attach 3. If the guest... a) ...has not been reported by virt-who yet, it will get a temporary guest subscription b) ...has been reported by virt-who, it will trigger an auto-attach on they parent hypervisor (which will grab a VDC) and then guest will get permanent guest subscription If this is not acceptable or causing problems, please expand on the issues involved for this RFE.
Hi Tom, is there any way to select which VDC pool will be used? We have different subs in the account that allow guests: * Unlimited guests (1-2 sockets) * Unlimited guests (4 sockets) * Unlimited guests (8 sockets) * Same as above but for 1 guest Additionally we have them in multiple batches, bought at different times, expiring at different times. As far as I know virt-who will not report socket-count for ESXi hypervisors. Will 3b) then just grab any available 1-2 sockets, unlimited guests sub? Regards Evgeni
Customer is requesting for an workaround on this issue. Is below workaround applicable to this problem ? https://github.com/RedHatSatellite/katello-attach-subscription Also kindly empathize that #comment 3.
Customer has also requested for the possibility to select the subscription based on (regexp)regular expression or some other method? preferred list: 1) regexp on VCenter cluster name 2) regexp on ESXi Host name" So that they can filer based on the *Cluster* name (not hostname) in the VCenter. Preetesh
(In reply to Preetesh Sharma from comment #9) > Customer has also requested for the possibility to select the subscription > based on (regexp)regular expression or some other method? > preferred list: > 1) regexp on VCenter cluster name That data is not available at the moment :( > 2) regexp on ESXi Host name" That works in katello-attache-subscription today, but yeah would be great if that would be inside Satellite.
*** This bug has been marked as a duplicate of bug 1308544 ***