Alright I have opened an issue: https://github.com/apache/cloudstack/issues/4155
Greetings,
Vincent
On 2020/06/18 10:00:35, Andrija Panic wrote:
> Nice...
>
> Can you please file a bug here https://github.com/apache/cloudstack/issues
> with
> explanation on how to reproduce etc
>
> Thanks
>
Nice...
Can you please file a bug here https://github.com/apache/cloudstack/issues with
explanation on how to reproduce etc
Thanks
Andrija
On Thu, 18 Jun 2020 at 11:23, Vincent Hermes
wrote:
> Hi Andrija,
>
> I just tested if it intervenes at any other point after changing the
> settings but e
Hi Andrija,
I just tested if it intervenes at any other point after changing the settings
but even if the running ones are already exceeding the limits you can start all
of your cheated machines anyway.
Regards,
Vincent
On 2020/06/18 07:36:16, Vincent Hermes wrote:
> Hi Andrija,
>
> I have
Hi Andrija,
I have tested it on Cloudstack 4.11.3 and 4.14. Yes thats correct. The Settings
tab of a stopped VM is completely unaware of the Domain and User Limits if a
custom offering is chosen. You could eventually create 16 VMs with 1 core per
VM to max out the Domain/Account Limit and after
If I read that correctly - you are saying that the domain settings are
applied when deploying a VM, but not when you change the compute offering
to more CPU (than the domain limit) and start the VM like that? If so, than
that's a bug.
Which ACS release?
Regards,
Andrija
On Wed, 17 Jun 2020 at 15:
Hi Guys,
is it a normal behaviour that a Domain Admin Account can set VM Parameters
above his own Domain restrictions? For example 16 CPU's are the Domain and
Account restrictions for the Domain Admins Account and when he creates a
machine this works properly but he can change the VM Settings i
