cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pranali Mande (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-10060) ListUsage API always displays the Virtual size as '0' for Usage type=9 (snapshot)
Date Fri, 01 Sep 2017 11:06:01 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-10060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pranali Mande updated CLOUDSTACK-10060:
---------------------------------------
    Description: 
*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.



  was:
*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. 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'.

The ListSnapshot API displays both, the physical as well as Virtual size and that can be used
to know both the sizes.




> 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)

Mime
View raw message