| Summary: | [RFE] Separate indication of incoming and outgoing live migrations in "Virtual Machines" column of "Hosts" tab | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Julio Entrena Perez <jentrena> |
| Component: | ovirt-engine | Assignee: | Martin Perina <mperina> |
| Status: | CLOSED ERRATA | QA Contact: | Israel Pinto <ipinto> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | bgraveno, dfediuck, gklein, iheim, istein, lsurette, michal.skrivanek, mperina, mtessun, rbalakri, Rhev-m-bugs, sherold, yeylon, ykaul |
| Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature |
| Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
When performing migrations, numbered left and right arrows now indicate incoming and outgoing migrations in the 'Hosts' tab.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-09 20:48:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Julio Entrena Perez
2014-06-26 15:00:28 UTC
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) Hi Michal, 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. Cheers, Martin 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 Verify with: 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: https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/wiki/Compute/VIRT_Migration_tests Cases: https://polarion.engineering.redhat.com/polarion/redirect/project/RHEVM3/workitem?id=RHEVM3-10554 https://polarion.engineering.redhat.com/polarion/redirect/project/RHEVM3/workitem?id=RHEVM3-10445 https://polarion.engineering.redhat.com/polarion/redirect/project/RHEVM3/workitem?id=RHEVM3-10895 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. https://rhn.redhat.com/errata/RHEA-2016-0376.html |