andrijapanicsb merged pull request #61: Added Instance Settings section
URL: https://github.com/apache/cloudstack-documentation/pull/61
This is an automated message from the Apache Git Service.
To respond to the message, plea
andrijapanicsb commented on issue #61: Added Instance Settings section
URL:
https://github.com/apache/cloudstack-documentation/pull/61#issuecomment-516022379
Thx @nvazquez. Merging.
This is an automated message from the Apach
andrijapanicsb commented on issue #61: Added Instance Settings section
URL:
https://github.com/apache/cloudstack-documentation/pull/61#issuecomment-515983010
@rhtyd @anuragaw @nvazquez @shwstppr - someone kindly review and LGTM if OK.
---
ACSGitBot commented on issue #61: Added Instance Settings section
URL:
https://github.com/apache/cloudstack-documentation/pull/61#issuecomment-515970177
Build finished. You can review it at:
https://acs-www.shapeblue.com/docs/pr61
Build Log Output:
No log errors found
andrijapanicsb commented on issue #61: Added Instance Settings section
URL:
https://github.com/apache/cloudstack-documentation/pull/61#issuecomment-515969701
requesting docbuild
This is an automated message from the Apache Gi
ACSGitBot commented on issue #61: Added Instance Settings section
URL:
https://github.com/apache/cloudstack-documentation/pull/61#issuecomment-515969733
Your request had been received, i'll go and build the documentation and
check the output log for errors.
This shouldn't take long.
andrijapanicsb opened a new pull request #61: Added Instance Settings section
URL: https://github.com/apache/cloudstack-documentation/pull/61
This is an automated message from the Apache Git Service.
To respond to the message
Pavn is right. The "StatsCollector.VmStatsCollector" class is executed as a
periodic task and collects and updates the database for VmStats. A VM Launched
by virt-manager is not considered as part of this background task.
Regards,
Anurag
From: Pavan Kumar Aravapa
Hi Ng'ang'a Kioi,
Stats are collected at very first time, When a host [KVM] is on-boarded to
Cloud stack. There after for every vm resource deployment done on the on-boarded
KVM host , the stats will get updated in cloud stack DB by Management Server
after deducing the utilised resource amoun
This seems to be an bug if we go with documentation and your observations. I
had recently also seen a bug where VMWare would always report a zero memory
consumed and it was a parsing issue in ACS VMWareResource.java class which I
fixed in 4.13.0. Perhaps something similar may be at play here. Ma
10 matches
Mail list logo
