cloudstack/server/test/com/cloud/vm
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
..
dao merge master 2013-05-11 15:28:43 +05:30
snapshot use hypervisor capabilities to control if vm snapshot is enabled for hypervisors 2013-04-10 12:36:42 +08:00
DeploymentPlanningManagerImplTest.java CLOUDSTACK-4746: 2013-10-18 15:22:25 -07:00
MockUserVmManagerImpl.java CLOUDSTACK-1192: Add Disk I/O Statistics 2013-06-01 08:00:48 +02:00
MockVirtualMachineManagerImpl.java CLOUDSTACK-4746: 2013-10-18 15:22:25 -07:00
UserVmManagerTest.java CLOUDSTACK-4566: fix incorrect values in resource_count table for resource limitation 2013-08-30 08:51:01 +02:00
VirtualMachineManagerImplTest.java CLOUDSTACK-3779: Support System vm scaling on VMWare 2013-07-29 14:12:24 +05:30