Commit Graph

11 Commits

Author SHA1 Message Date
Abhinandan Prateek e65dbbc3cf Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 1b2b58fe35.
2013-12-16 15:42:51 +05:30
Abhinandan Prateek 1b2b58fe35 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-16 15:36:37 +05:30
Abhinandan Prateek 2bdd288605 Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit cc662445a5.
2013-12-13 11:53:40 +05:30
Abhinandan Prateek cc662445a5 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-13 11:46:08 +05:30
Abhinandan Prateek 3c561c6d79 Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 6ba071b159.
2013-12-03 17:46:18 +05:30
Abhinandan Prateek 6ba071b159 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-03 17:41:35 +05:30
Abhinandan Prateek 92254a5a2f Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 7fb9dcb131e1d2d5a7c87e0aab2929b772bcd008.
2013-12-03 17:16:18 +05:30
Abhinandan Prateek e8c3c650a7 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-12-03 17:16:17 +05:30
Abhinandan Prateek 4cb311530c Revert "Updating pom.xml version numbers for release 4.2.1"
This reverts commit 0b9eadaf14.
2013-11-12 21:17:27 +05:30
Abhinandan Prateek 0b9eadaf14 Updating pom.xml version numbers for release 4.2.1
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-11-12 21:15:01 +05:30
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