Red Hat Bugzilla – Bug 1259476
[RFE] Add RHEVM Targeted Refreshes.
Last modified: 2016-11-29 01:41:48 EST
Created attachment 1069557 [details]
log output from EmsRefresh.refresh on 100 vms on rhevm medium sized provider
Description of problem:
Refreshing specific Virtual Machines consume same amount of time regardless of the number of vm selected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Perform Initial Refresh of a RHEVM provider
2. Select a specific number of VMs and perform a refresh x X times (Change number of targets)
99th percentile timing values are shown for 4 iterations of the tests.
Environment tested was a simulated RHEVM 3.4 environment consisting of:
1000 Virtual Machines (500 online)
61 storage domains
Refresh against a single Vm should be far faster than refresh on 100 VMs for a medium sized environment. (Benchmarking a similar VMware provider exhibits this behavior.)
full_refresh_threshold is bumped above 100 to prevent targeted refreshes against 100 VMs from becoming a provider refresh.
This becomes even more apparent as the scale of the environment is bumped to 3000 virtual machines.
It appears that RHEVM is refreshing all virtual machines according to log output during refreshes as there are log lines for updating hosts and vms that are not targets.
I confirmed that RHEVM Refresh does not have capability to perform a targeted refresh yet, changed this to an RFE.
Verified in 184.108.40.206-beta2.4.20160503153816_1fb554f
Measured time was like ten times faster when refreshing single vm in 220.127.116.11 than in 5.5.2.
Also in evm.log there was only single vm update in 18.104.22.168, but in 5.5.2 all vms were updated.
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.