You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by an...@apache.org on 2020/03/11 20:06:01 UTC

[cloudstack] 01/01: Reduce nonsence value for capacity.skipcounting.hours

This is an automated email from the ASF dual-hosted git repository.

andrijapanic pushed a commit to branch lower-capacity-skipcounting-hours-setting
in repository https://gitbox.apache.org/repos/asf/cloudstack.git

commit bbedfbc9ce920abb393aa9b0da04aaa9f8744eba
Author: Andrija Panic <45...@users.noreply.github.com>
AuthorDate: Wed Mar 11 21:05:40 2020 +0100

    Reduce nonsence value for capacity.skipcounting.hours
---
 engine/schema/src/main/resources/META-INF/db/schema-41300to41400.sql | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/engine/schema/src/main/resources/META-INF/db/schema-41300to41400.sql b/engine/schema/src/main/resources/META-INF/db/schema-41300to41400.sql
index 2c9c7ab..933e9d6 100644
--- a/engine/schema/src/main/resources/META-INF/db/schema-41300to41400.sql
+++ b/engine/schema/src/main/resources/META-INF/db/schema-41300to41400.sql
@@ -19,6 +19,11 @@
 -- Schema upgrade from 4.13.0.0 to 4.14.0.0
 --;
 
+-- Don't reserve capacities for stopped VMs by default as this influences normal capacity checks when doing i.e. rolling host maintenance, etc.
+-- One is free to increase this to a high value in case it's needed in his environment, otherwise makes no sense in most environments,
+-- as new VM can't be started on an empty host which was consumed previously by many VMS which are now stopped
+UPDATE `cloud`.`configuration` SET `default_value`='10' WHERE  `name`='capacity.skipcounting.hours';
+
 -- KVM: enable storage data motion on KVM hypervisor_capabilities
 UPDATE `cloud`.`hypervisor_capabilities` SET `storage_motion_supported` = 1 WHERE `hypervisor_capabilities`.`hypervisor_type` = 'KVM';