From users-return-34546-apmail-cloudstack-users-archive=cloudstack.apache.org@cloudstack.apache.org Thu Jun 18 07:44:59 2020 Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by minotaur.apache.org (Postfix) with SMTP id E98ED19B0F for ; Thu, 18 Jun 2020 07:44:58 +0000 (UTC) Received: (qmail 68211 invoked by uid 500); 18 Jun 2020 07:44:56 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 68172 invoked by uid 500); 18 Jun 2020 07:44:55 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Delivered-To: moderator for users@cloudstack.apache.org Received: (qmail 43121 invoked by uid 99); 18 Jun 2020 07:36:17 -0000 To: Content-Type: text/plain; charset=utf-8 In-Reply-To: X-Mailer: LuaSocket 3.0-rc1 From: Vincent Hermes Subject: Re: Domain Limits ignored Message-ID: x-ponymail-sender: 7f24dca28911320c26fe5808aaafc923aa5f68ba References: x-ponymail-agent: PonyMail Composer/0.2 MIME-Version: 1.0 Date: Thu, 18 Jun 2020 07:36:16 -0000 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 afterwards set all the CPUs and RAM to ridiculous levels. As long as the hosts are capable of booting the VM with these parameters, cloudstack will not intervene when starting them. So you could essentially have 16 VMs with 32 Cores each and thats fine. Regards, Vincent On 2020/06/17 15:42:28, Andrija Panic wrote: > 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:42, Vincent Hermes > wrote: > > > 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 in the > > Settings tab (user-defined offering) even above 16 CPUs. In fact none of > > the Domain Restrictions apply on settings done in this tab so RAM is > > completely open as well. > > > > Thanks in advance and best Regards > > Vincent > > > > > -- > > Andrija Panić >