Bug 1402452 - [RFE] - Storage migration metrics
Summary: [RFE] - Storage migration metrics
Keywords:
Status: CLOSED DUPLICATE of bug 1547937
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.0
: 4.4.0
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 15:09 UTC by marc skinner
Modified: 2023-09-07 18:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-01 11:48:56 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)
rhev manager UI storage migration actual screen shot (14.11 KB, image/png)
2016-12-07 15:09 UTC, marc skinner
no flags Details

Description marc skinner 2016-12-07 15:09:03 UTC
Created attachment 1229088 [details]
rhev manager UI storage migration actual screen shot

When you do a storage live migration - from 1 data store to another, 
there is no information provided for status, performance etc of the 
migration event.  Take a look at the screen shot.

It would be great to add the following:

Total Size
Completed Size
IOPs
Storage performance (MB/s or GB/s)
Estimated time
Completed time

Comment 1 Yaniv Kaul 2018-02-26 12:46:16 UTC
Yaniv, that sounds to me more like a storage RFE and not metrics?

Comment 2 Yaniv Lavi 2018-02-26 13:43:30 UTC
(In reply to Yaniv Kaul from comment #1)
> Yaniv, that sounds to me more like a storage RFE and not metrics?

We need a to create a collectd collector for this stats. It's in between storage and metrics.

Comment 3 spower 2018-07-03 10:13:24 UTC
We agreed to remove the component RFEs from Bugzilla. If you feel the component has been named incorrectly, please reach out.

Comment 4 Sandro Bonazzola 2019-01-28 09:41:10 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 6 Doron Fediuck 2020-01-01 11:48:56 UTC

*** This bug has been marked as a duplicate of bug 1547937 ***


Note You need to log in before you can comment on or make changes to this bug.