You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kishan Kavala (JIRA)" <ji...@apache.org> on 2016/01/25 11:00:47 UTC

[jira] [Commented] (CLOUDSTACK-9232) Usage data does not reflect changes of VM parameters

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

Kishan Kavala commented on CLOUDSTACK-9232:
-------------------------------------------

Vm usage data contain service offering id. CPU/memory info can fetched using service offering.
Only incase of custom service offering cpu/memory etc are populated in Vm usage records.

> Usage data does not reflect changes of VM parameters
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-9232
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9232
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.5.2
>            Reporter: Norbert Klein
>              Labels: billing, usage
>
> The usage data is created without including the information of properties of the usage object. For example if we want to bill a vm with usagetype 1 we only see the time the vm was used. But we don't see in the usage data how many cpus, etc. the vm had at the time the usage record was created. Thus we cannot bill changes of the vm. For example if a customer adds a cpu core to his vm and later removes it, this should be seen in the usage records. But as far as I know the database records are all set to NULL and cloudmonkey does not return these fields although they are availble in the API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)