Re: 4.13.0.0 Triaging

All, Another reminder - we're getting close to the freeze date, due to this I've pushed several issues and PRs to 4.13.1.0 and 4.14.0.0 milestones. If there is/are any issue(s) or pull request(s) that we should include in 4.13.0.0 kindly share. Thanks. Regards, Rohit Yadav Software Archi

答复: Unable to release computing resources

Hi Andrija Why is it necessary to delete the VM before releasing the computing resources? The stopped VM has no consumption of computing resources, it should not be counted. Is there any way to automatically release resources after the virtual machine stops? 发件人: Andrija Panic

Re: Unable to release computing resources

Afaik, those resource limits are not released (i.e. number of CPUs ) when you stop a VM - it is permanent accounted against an account until VM is removed. Buy I might be wrong - on the specific Account page/tab in UI, there is something like " update resource count" button, which should give you t

答复: Unable to release computing resources

Hi Rohit Sorry, I didn’t make it clear. Account Info: Name: "ITDept", Accounttype: 2, Roletype: "DomainAdmin", Rolename: "Domain Admin", Cpulimit: "12", Cputotal: "12", Vmlimit: "4", Vmtotal: 2 Create 2 VMs under this account: Vm1 Name=vm1,vcpu=8,ram=16g,status=Stopped Vm1 Name=vm2,vcpu=4,r

Re: Unable to release computing resources

Jerry, The flag you've mentioned is an internal CloudStack flag, please don't change that (starting 4.13+ we'll limit showing such flags at least to users). What you want is to decrease the time CloudStack does capacity checks for which you can tune capacity.check.period, lowering which will c