Try to o provision CPU on a cluster level, thought I can't say if shortage
of CPU or RAM, on my mobile atm...
On Sun, Mar 10, 2019, 10:03 Andrija Panic wrote:
> Cannot allocate cluster list [1] for vm creation since their allocated
> percentage crosses the disable capacity threshold defined at e
Cannot allocate cluster list [1] for vm creation since their allocated
percentage crosses the disable capacity threshold defined at each cluster/
at global value for capacity Type : 1, skipping these clusters
On Sat, Mar 9, 2019, 20:54 Fariborz Navidan wrote:
> Any idea?
>
> On Sat, Mar 9, 201
I've already set cluster.cpu.allocated.capacity.disablethreshold to
maximum value in both cluster and global settings. Is it possible to to
makeACS ignore cpu capacity check?
On Sun, Mar 10, 2019 at 12:43 PM Andrija Panic
wrote:
> Try to o provision CPU on a cluster level, thought I can't say
Cpu.overprovisioning.ratio or such - set it to 2.0 - means CloudStack will
see your cluster having 200% cpu of that it really has, 3.5= 350% etc.
On Sun, Mar 10, 2019, 10:24 Fariborz Navidan wrote:
> I've already set cluster.cpu.allocated.capacity.disablethreshold to
> maximum value in both c
Thanks!
Any similar replacement suggestion to provide kibernets like stuff to users
outofbox?
On Sat, 9 Mar 2019 at 17:18, Ivan Kudryavtsev
wrote:
> AFAIK, the last CS compatible with container service is 4.6 or smth like
> that.
>
> сб, 9 мар. 2019 г., 9:04 Konstantin :
>
> > Hello!
> >
> > I
Even with cpu overprovisioning factor of 20 set on both cluster and global
settings, still I cannot deploy new VMs. It show 672GHz in
dashboardinstead of 33.6GHz (actual capacity) but still I get in the log
"The host is in avoid list".
Please advise.
Thanks
On Sun, Mar 10, 2019 at 4:04 PM Andri
Can you send your complete logs, right after an ACS reboot, and when you
try to start a new VM?
On Sun, Mar 10, 2019 at 10:11 AM Fariborz Navidan
wrote:
> Even with cpu overprovisioning factor of 20 set on both cluster and global
> settings, still I cannot deploy new VMs. It show 672GHz in
> d
I guess the issue is that allocated cpu is also grown by overprovisioning
factor such thatusage percentage remains the same. So, by increasing cpu
overprovisiong factor you don't gain access to un-utilized cpu capacity. My
real cpu utilization on the host is 31% but 84.82% is allocated and by
incre
Ah, this happens for a simple reason.
When you allocate a VM with over-provision of 1, you are charging by that,
and later if you change the over-provisioning to two; what would you expect
to happen with that VM that was allocated when over-provisioning was set to
1? ACS is doing that do maintain
I just rebooted the ACS and now get this error: "Unable to attach storage
pool3 to host[id]. Primary storages are both are in state "Up"
Please send compete log to pastebin.com or such...and link here.
On Sun, Mar 10, 2019, 14:36 Rafael Weingärtner
wrote:
> Ah, this happens for a simple reason.
>
> When you allocate a VM with over-provision of 1, you are charging by that,
> and later if you change the over-provisioning to two; wh
Can you share more details (Hypervisor, States before restart, etc) and error
logs.
On 10/03/19, 9:02 PM, "Fariborz Navidan" wrote:
I just rebooted the ACS and now get this error: "Unable to attach storage
pool3 to host[id]. Primary storages are both are in state "Up"
DISCLA
Hello All,
I solved the issue. When you have running VMs, after changing
cpu.overprovising.factor and restart management server, you need to stop
all VMs, put the host in Maintenance mode and remove it. The host will be
automatically re-added to the cluster and you will get additional CPU
capacity
Sorry, It was a miss-configuration. I had a second primary storage at
/home2 which was mounted manually and I had forgot to add entry for it in
/etc/fstab
It has been resolved
On Sun, Mar 10, 2019 at 7:49 PM Suresh Anaparti <
[email protected]> wrote:
> Can you share more details (H
It was enough to just stop VMs and start again (assuming you change
cpu.overprovisioning on the cluster level - i.e. settings tab of the actual
cluster). If global settings changed, then yes, restart of mgmt server and
again stop/start existing VMs, but definitely NOT removing and re-adding
the hos
Yes, but when I stopped VMs, I couldn't start them even after several
minutes (capacity check interval). ACS was showing CPU has freed up but
still couldn't start same VMs. That's why I removed and re-added the host.
Regards
On Sun, Mar 10, 2019 at 9:49 PM Andrija Panic
wrote:
> It was enough
Ok. Thanks for the update.
On 10/03/19, 10:04 PM, "Fariborz Navidan" wrote:
Sorry, It was a miss-configuration. I had a second primary storage at
/home2 which was mounted manually and I had forgot to add entry for it in
/etc/fstab
It has been resolved
On Sun, Mar 1
17 matches
Mail list logo
