cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebgoa <run...@gmail.com>
Subject Re: Cpu, cpu speed and memory in usage records
Date Thu, 05 Jun 2014 19:20:33 GMT

On Jun 5, 2014, at 1:29 PM, Olivier Lemasle <olivier.lemasle@apalia.net> wrote:

> Hi,
> 
> Thanks Harikrishna for your answer. I created a ticket for this
> (CLOUDSTACK-6880 [1]).
> I can submit a review request for this issue, but I cannot assign the issue
> to myself on Jira.

What's your jira id ?

> 
> --
> Olivier
> 
> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-6850
> 
> 
> On Wed, Jun 4, 2014 at 10:55 AM, Harikrishna Patnala <
> harikrishna.patnala@citrix.com> wrote:
> 
>> Hi,
>> We are recording the cpu and ram values in usage_vm_instance table while
>> parsing the usage events. These details needs to be populated in
>> cloud_usage table as well. Please feel free to file a ticket for this.
>> 
>> Thanks
>> Harikrishna
>> *From:* Olivier Lemasle [olivier.lemasle@apalia.net]
>> *Sent:* Tuesday, June 03, 2014 8:54 PM
>> *To:* dev@cloudstack.apache.org
>> *Cc:* Harikrishna Patnala; Kishan Kavala
>> *Subject:* Cpu, cpu speed and memory in usage records
>> 
>>  Hi,
>> 
>> Is it normal if CloudStack does not return usage details (cpu cores, cpu
>> speed and memory) in the usage records?
>> 
>> Since the introduction of dynamic compute offerings, these details are
>> recorded in table cloud_usage.usage_vm_instance, but they are not in table
>> cloud_usage.cloud_usage, and they aren't returned by the "listUsageRecords"
>> API command.
>> 
>> So, what was the purpose of these details in cloud_usage
>> (CLOUDSTACK-4737, CLOUDSTACK-5515, CLOUDSTACK-6466)? It seems they're saved
>> in database but never read. Am I wrong?
>> 
>> Thanks,
>> 
>> --
>> Olivier Lemasle
>> Software Engineer
>> *Apalia*™
>> Mobile: +33-611-69-12-11
>> 
>> *http://www.apalia.net <http://www.apalia.net>
>> <olivier.lemasle@apalia.net>olivier.lemasle@apalia.net
>> <olivier.lemasle@apalia.net>*
>> 


Mime
View raw message