Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 16 Oct 2017 12:15:00 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13099198.1504263810000.4789.1508156100151@Atlassian.JIRA>
In-Reply-To: <JIRA.13099198.1504263810000@Atlassian.JIRA>
References: <JIRA.13099198.1504263810000@Atlassian.JIRA> <JIRA.13099198.1504263810276@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-10060) ListUsage API always displays
 the Virtual size as '0' for Usage type=9 (snapshot)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 16 Oct 2017 12:15:08 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205808#comment-16205808 ] 

ASF subversion and git services commented on CLOUDSTACK-10060:
--------------------------------------------------------------

Commit 189b0e4487c0caa0204b1dbb3cb5882ad2e7726e in cloudstack's branch refs/heads/CLOUDSTACK-10012 from [~pranalim]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=189b0e4 ]

CLOUDSTACK-10060: ListUsage API always displays the Virtual size as '0' for Usage type=9 (snapshot) (#2257)

Bug Description:
In the listUsage API, the Virtual Size of Snapshot is always displayed as '0'.

Root Cause:
In case of snapshots, the usage is accounted for depending on the value of the global parameter, 'usage.snapshot.virtualsize.select'. If set to 'true', the usage calculation is done based on the Virtual Size, and if set to false, it is done based on the Physical size. In the Usage API, this value, (i.e. virtual or physical) is displayed as 'Size' field correctly, but the field 'VirtualSize' is always displayed as 0. This is misleading.

Expected Output:
Since this is a Usage API, ideally only that size should be displayed which is used for billing, depending on the value of 'usage.snapshot.virtualsize.select'.
There is another API - the ListSnapshot API that displays both, the physical as well as Virtual size and can be used to know both the sizes.

Fix Implemented:
Skipped showing the 'VirtualSize' Field for type=snapshot

> ListUsage API always displays the Virtual size as '0' for Usage type=9 (snapshot)
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10060
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10060
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Pranali Mande
>            Priority: Minor
>         Attachments: usageAPI_VirtualSize_0_snapshot.png
>
>
> *Bug Description:*
> In the listUsage API, the Virtual Size of Snapshot is always displayed as '0'.
> *Root Cause:*
> In case of snapshots, the usage is accounted for depending on the value of the global parameter, 'usage.snapshot.virtualsize.select'. If set to 'true', the usage is done based on the Virtual Size, and if set to false, it is done based on the Physical size. In the Usage API, this value, (i.e. virtual or physical) is displayed as 'Size' field in the Usage API and the field 'VirtualSize' is always displayed as 0.
> *Expected Output:*
> Since this is a Usage API, ideally only that size should be displayed which is used for billing, depending on the value of 'usage.snapshot.virtualsize.select'.
> There is another API - the ListSnapshot API that displays both, the physical as well as Virtual size and can be used to know both the sizes.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)