cloudstack presenting wrong used memory values

2014-01-28 Thread Rafael Weingartner
Hi all, I am mailing this to the dev and users list, since I am not sure which one would be the best to make such question. So, I deployed Zenoss to monitor my Cloud, and I noticed something weird on a graph that it was generating about the Cloud's memory. The graph was showing total memory as 2

Re: cloudstack presenting wrong used memory values

2014-01-29 Thread Rafael Weingartner
Doesn't anyone think that those memory values presented on infrastructure>hosts are a little odd? On Tue, Jan 28, 2014 at 2:54 PM, Rafael Weingartner < rafaelweingart...@gmail.com> wrote: > Hi all, > > I am mailing this to the dev and users list, since I am not sure which one > would be the best

Fwd: cloudstack presenting wrong used memory values

2014-01-29 Thread Marty Sweet
What hypervisor are you using? My CS System Capacity on the dashboard shows *Memory 157.05 GB / 1.37 TB *(which works + overprovisioning). I think this issue is slightly different to CLOUDSTACK-3048 as it should not effect VM allocation. I have never noticed about the memory used section: Memo

Re: cloudstack presenting wrong used memory values

2014-01-29 Thread Marty Sweet
I should also point out that this is on CS 4.2.0. This issue may have been fixed since then. Marty On Thu, Jan 30, 2014 at 7:41 AM, Marty Sweet wrote: > What hypervisor are you using? > > My CS System Capacity on the dashboard shows *Memory 157.05 GB / 1.37 TB > *(which > works + overprovisi

Re: cloudstack presenting wrong used memory values

2014-01-30 Thread Rafael Weingartner
I am using xen-hypervisor 4.1 and XCP 1.6 if I am not mistaken. I have also never noticed this used memory values until we deployed Zenoss to monitor the cloud. I just noticed that because the Zenoss was generating a graph that presented whole cloud memory usage and it was a little weird. With hig

Re: cloudstack presenting wrong used memory values

2014-01-31 Thread Rafael Weingartner
Well guys, yesterday I took a look at the CS source code and how it was getting those values. I think that I cracked it. It seems that there is a whole misunderstanding about the used memory value and It would be nice an update on the Cloudstack API documentation. Let's start: Here is a link for