Description of problem:
While VMs are live migrating between hosts the column "Virtual Machines" of the "Hosts" tab displays a left right arrow <---> with the number of live migrating machines for each host , but no indication of the direction of the live migrations is displayed.
Consequently users can not know if those VMs are migrating _in_ or _out_ of the host.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Select multiple VMs running on host A and request those to migrate out of the host.
2. Select multiple VMs running on separate host B and request those to migrate to host A.
2. Observe "Virtual Machines" column in "Hosts" tab.
A left right arrow with the total number of VMs migrating _in_ and _out_ of the host is displayed (e.g. <--6-->).
A separate arrow for VMs migrating _in_ and VMs migrating _out_ is displayed (e.g. --4--> <--2-- indicating 4 VMs migrating out of the host and 2 VMs migrating in to the host).
For large hosts with big amounts of memory (e.g. 1TB) running hundreds of VMs the live migrations can take a long time to complete (30 - 60 minutes or more).
Users can not easily tell how many VMs are migrating in and out of a host for long periods of time.
this has been implemented originally by SLA ~2 years ago by Laszlo, I'm sure there were some considerations about why it is the way it is…Doron?
(actually should be this one - bug 970195)
I think this is just an additional enhancement in getting a feeling what's going on in an environment.
Especially if you have a lot of migrations ongoing, you want to know if these are incoming or outgoing migrations.
So if there is a way (and I believe there is) to identify the incoming and outgoing migrations, it would be great to get this implemented within the RHEV 3 lifetime.
I'd propose to calculate the value in vdsm and just send it to the engine as opposed to engine doing the calculation based on monitoring DB state.
Since vdsm is reporting total migrations since ages it's simpler to just extend it a little instead of adding a new partially redundant calculation in engine (with the risk of not being compeltely in sync due to async updates and monitoring cycle in engine) It's a lot more simple on the engine side
oVirt Engine Version: 3.6.0-0.0.master.20150412172306.git55ba764.el6
3.6 host vdsm:vdsm-4.17.0-632
3.5 host vdsm:vdsm-4.16.16-1
Run tests cases:
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.