Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1140735

Summary: [RFE] [ovirt optimizer] Improve current/target cluster for better readability
Product: [Retired] ovirt-optimizer Reporter: Lukas Svaty <lsvaty>
Component: RFEsAssignee: Martin Sivák <msivak>
Status: CLOSED WONTFIX QA Contact: Shira Maximov <mshira>
Severity: medium Docs Contact:
Priority: low    
Version: ---CC: bugs, dfediuck
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: ylavi: ovirt-future?
sherold: Triaged+
rule-engine: planning_ack?
lsvaty: devel_ack?
rule-engine: testing_ack?
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-17 13:23:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Lukas Svaty 2014-09-11 14:51:47 UTC 
Description of problem:
In Ovirt optimizer cluster tab VMs that are running are shown under incorrect host. Please see screen attached. This 

Version-Release number of selected component (if applicable):
vt2.2

How reproducible:
100%

Steps to Reproduce:
1. Run 1 VM 'test_HA_VM' on host purple
2. Edit VM 'foo' to start running on specific host (purple)
3. Run 2 VM

Actual results:
See screenshot attached
Comment 1 Lukas Svaty 2014-09-11 14:53:28 UTC 
Created attachment 936584 [details]
Screenshot

You can clearly see that VM is running on host 'venus' and optimizer is suggesting to move VM to host 'venus'... what?
Comment 2 Lukas Svaty 2014-09-11 15:20:45 UTC 
After further investigation table is suggesting target state for cluster. Which is a bit confusing as admin might not know what is the current state if there are more than 20 (default) steps needed to perform. If admin need to find where is a VM running at the moment and what is suggested host he need to look around which is not really user friendly.

I would suggest creating two tables not just one side-by-side.

Current State                                    Target State
host1:                                           host1:
vm1                                              vm1
vm2                                              host2:
host2:                                           vm2
Comment 3 Doron Fediuck 2014-09-14 08:12:30 UTC 
(In reply to Lukas Svaty from comment #2)
> After further investigation table is suggesting target state for cluster.
> Which is a bit confusing as admin might not know what is the current state
> if there are more than 20 (default) steps needed to perform. If admin need
> to find where is a VM running at the moment and what is suggested host he
> need to look around which is not really user friendly.
> 
> I would suggest creating two tables not just one side-by-side.
> 
> Current State                                    Target State
> host1:                                           host1:
> vm1                                              vm1
> vm2                                              host2:
> host2:                                           vm2


Lukas,
the admin does not have to look for a host the VM is running on.
All he needs to do is use the VMs tab to select the VM he wish to migrate.
Generally speaking we care less about the source and more about the destination.

Having that said, we'll look into improving the UI in the coming versions.
Comment 5 Martin Sivák 2016-10-17 13:23:55 UTC 
Closing as we have a different direction with all the reactjs and dashboard plans.