Description of problem:
virt-who should be run soon after provisioning a new system to be able to attach subscriptions to the system. This makes problems for deployments with frequent  provisioning of new systems, that require lowering VIRTWHO_INTERVAL substantially.

What about virt-who re-mapping VMs to hypervisors not blindly every X minutes (that creates redundand load and/or still insufficient in some "rush provisioning hour") but rather make sure that during provisioning a new system, virt-who to re-map VMs soon on time, triggered by an automated request from foreman.

Something like:
- when foreman knows a new VM has been just created, it sends a request to virt-who to generate report in given SLA (i.e. if I know the VM will need the subscriptions ready in 10 minutes, let ask virt-who to re-map with 9 minutes SLA, to ensure the work is donew before subs are to be assigned to the VM)
- this "virt-who SLA" should be a foreman parameter configurable via WebUI
- virt-who accumulates the requests and based on some trivial heuristic (just to ensure SLAs are achieved but reports not generated too often), do the re-mapping and report it
- the heuristic could be e.g. "fire the re-map immediatelly upon receiving a request, but at least VIRTWHO_MIN_INTERVAL seconds after the previous run"

Then VIRTWHO_INTERVAL can be kept on some default high value (in hours) and virt-who will kick off the report only on demand.


Version-Release number of selected component (if applicable):
Sat 6.1.6


How reproducible:
100%


Steps to Reproduce:
1. Have appropriate (high) VIRTWHO_INTERVAL
2. Wait for virt-who to report the mapping
3. Soon after that, provision a new system and check if subscriptions will be attached.


Actual results:
3. Subs wont be attached.


Expected results:
3. Subs to be attached since virt-who will be requested to run extra report.


Additional info: