Bug 1617977 – Report space saving values in vdo stats

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1617977 - Report space saving values in vdo stats

Summary:	Report space saving values in vdo stats

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	vdsm
Classification:	oVirt
Component:	Gluster (Show other bugs)
Sub Component:
Version:	4.30.0
Hardware:	Unspecified Unspecified

Priority	high Severity medium (vote)
Target Milestone:	ovirt-4.2.6
Target Release:	---
Assigned To:	Denis Chaplygin
QA Contact:	SATHEESARAN
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1590967
	Show dependency tree / graph

Reported:	2018-08-16 06:13 EDT by Sahina Bose
Modified:	2018-09-13 03:41 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	VDO savings are displayed as part of the brick properties in the Manager UI. This feature allows administrators to see the actual space savings resulting from VDO duplication and compression.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-09-13 03:41:10 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Gluster
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	rule-engine: ovirt‑4.2+ rule-engine: exception+ ylavi: planning_ack+ sabose: devel_ack+ bshetty: testing_ack+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	92739	master	MERGED	gluster: Added savings data to the vdoVolumeList output	2018-08-21 10:35 EDT

Groups: None (edit)

Description Sahina Bose 2018-08-16 06:13:10 EDT

Description of problem:

To display space savings to user in oVirt engine, when vdo is turned on for a device, these values need to be reported from vdsm in the vdo verbs.

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


How reproducible:
NA

Comment 1 SATHEESARAN 2018-09-04 08:05:24 EDT

vdsm reports the size values properly

#  vdsm-client --gluster-enabled GlusterHost vdoVolumeList
{
    "vdoVolumeList": [
        {
            "name": "/dev/mapper/vdo_sdb", 
            "free": 19954217996288, 
            "device": "/dev/sdb", 
            "physicalBytesUsed": 3286122496, 
            "logicalBytesUsed": 12486795264, 
            "size": 19998441472000
        }
    ]
}

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