cloudstack/engine
Nitin Mehta de28812add CLOUDSTACK-4746:
From functionality point of view following will be changes.
-> Threshold will not be applied for vms undergoing HA process (say during host going down event).
-> Threshold will not be applied for vms undergoing maintenance.
-> Threshold will apply for stop-start vm "after" the skip.counting.hours
(time till which we reserve the capacity for the stopped vm).
Reason being stop-start is a user initiated action and we are giving a time
window  (skip.counting.hours) till which its guaranteed to start in the same
cluster.
After that time, threshold check applies bcz we still want to reserve the
capacity for urgent situations like HA, putting host into maintenance rather than get it consumed in such user
initiated actions.

Signed off by : nitin mehta<nitin.mehta@citrix.com>
2013-10-18 15:22:25 -07:00
..
api CLOUDSTACK-4725: if storage pool has different path, but the uuid is the same, then treat them as the same storage pool 2013-10-16 15:22:45 -07:00
components-api Updating pom.xml version numbers for release 4.2.1-SNAPSHOT 2013-10-03 17:13:17 -07:00
compute Updating pom.xml version numbers for release 4.2.1-SNAPSHOT 2013-10-03 17:13:17 -07:00
network Updating pom.xml version numbers for release 4.2.1-SNAPSHOT 2013-10-03 17:13:17 -07:00
orchestration CLOUDSTACK-4746: 2013-10-18 15:22:25 -07:00
planning/src/org/apache/cloudstack/platform/planning Added engine 2012-11-05 09:14:14 -08:00
schema CLOUDSTACK-4882: 2013-10-16 15:01:33 -07:00
service Updating pom.xml version numbers for release 4.2.1-SNAPSHOT 2013-10-03 17:13:17 -07:00
storage CLOUDSTACK-4681: data disk with local disk offering are geting created on shared storage 2013-10-18 16:34:47 +05:30
pom.xml Updating pom.xml version numbers for release 4.2.1-SNAPSHOT 2013-10-03 17:13:17 -07:00