[
https://issues.apache.org/jira/browse/CLOUDSTACK-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226780#comment-14226780
]
Olivier Lemasle commented on CLOUDSTACK-6850:
---------------------------------------------
Hi [~bhaisaab], this fix requires a database model modification (3 additional
columns in table `cloud_usage`.`cloud_usage`).
Is it really possible to backport it to 4.3? Because if the db model for 4.3 is
changed now, I guess that the update to 4.4 will not work anymore...
> Cpu cores, cpu speed and memory are not returned by listUsageRecords
> --------------------------------------------------------------------
>
> Key: CLOUDSTACK-6850
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6850
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Usage
> Affects Versions: 4.3.0, 4.4.0
> Reporter: Olivier Lemasle
> Assignee: Olivier Lemasle
> Priority: Critical
> Fix For: 4.4.0
>
>
> When using dynamic custom offerings, cpu cores, cpu speed and ram values are
> recorded in usage_vm_instance table while parsing the usage events.
> But these details are not populated in cloud_usage table, and are not
> returned by the listUsageRecords command. Therefore, there is no way to know
> the historical values for cpu and memory using API.
> We should add cpu_cores, cpu_speed and memory in cloud_usage.cloud_usage and
> return them in listUsageRecords response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
