Description of problem:

1. The virt-who application needs better log file management and configuration.  In one case we have 44 vCenters in the 1 configuration file.  When it starts up is the only time you can figure out if there is a problem with one.  Later on if one becomes unresponsive you can see the messages in the log file, but you can't tell which vCenter is having a problem.  When the log rotation does happen you get a new log file but the old process has the old log files open.  If one of the processes dies then it just sits there and doesn't get managed or restarted.  I almost think that virt-who should maybe have a log file for each vCenter/hypervisor that it manages and also some process management to manage and restart if the process dies.  I would also think that the interval that each vCenter is checked should be able to have its own value.  I wonder if this could maybe be self tuning depending on how many changes are going on?

2. Activation keys and virt-who.  Activations keys should be more generic.  Meaning I have an activation key and I want to select the subscription at the DERIVED SKU and not at the individual ESX host level.  I would just select the DERIVED SKU at the top and not at the lower level.  When ESX hosts come and go they would just be added or removed as the VM's guests move around between the different ESX host or hyper-visor.  I shouldn't have to go in everyday and click and select things and have to be manually adding them.  You configure it 1 time and you should be done.  You just say I want DERIVED SKU's added I don't care what they are.  I don't want to have to select 600 of them.

3. ESX host subscriptions should just happen.  It knows that it is a virtual host and it knows which VM's belong to it.  The subscriptions should just happen both at the Virtual DataCenter level and the DERIVED SKU should just get added to the VM.  It shouldn't depend on a product certificate, it knows what it is already.  I don't want to have to click on 6,000 VM's and manage their subscription.  virt-who should just work and should not require more than some simple configuration settings.  It shouldn't be a full time job for a person.


Additional info: