Hi Adrian,
The cpu number in the host details view, is the actual host cpu number *
cpu overprovisioning factor
On the overall dashboard, it does not take the cpu overprovisioning factor
into consideration. The value is the sum of host cpu numbers.
-Wei
On Fri, 30 Jul 2021 at 08:47, Michael Kes
Hi Eric,
Am 29.07.21 um 19:55 schrieb Eric Green:
> On 7/29/2021 3:48 AM, Andrija Panic wrote:
>> AND, the "insufficient capacity" has, wait one 99% of the case NOTHING
>> to do with not having enough capacity here or there, it's the stupid,
>> generic message on failure.
>
> Talking about wh
On 7/29/2021 3:48 AM, Andrija Panic wrote:
AND, the "insufficient capacity" has, wait one 99% of the case NOTHING
to do with not having enough capacity here or there, it's the stupid,
generic message on failure.
Talking about which, a bit off-topic here I know, I dug through the
source cod
Thanks Andrija,
I found the issue from the logs. I had hit a threshold so it had suspended the
cluster, I've increased the allowance a little until I can get some more
resources introduced.
Thanks for your help.
Adrian.
On 2021/07/29 10:48:24, Andrija Panic wrote:
> Old UI or new UI, which ACS
Old UI or new UI, which ACS version?
Core count has NOTHIGN to do with capacity - keep that in mind, i.e. the
pure number of cores shown in Dashboard. (it's the core count x core
frequency per each hypervisor that counts towards capacity)
AND, the "insufficient capacity" has, wait one 99% of
Hi Everyone,
We have an issue where the core count on our cloudstack is showing incorrectly
on the dashboard, I think this is then leading to an insufficient server
capacity error we now receive on setting up guests.
The core count on the physical hosts shows correct at 96 cores across 3 hosts
