Devdeep Singh 7dec27e844 CLOUDSTACK-3708, Migration of a volume attached to a running instance isn't working (Storage motion). ... The request to migrate was coming till ancient data motion strategy but wasn't worked on and forwarded to the resource. The code probably got removed by a bad merge. Bringing it back.		2013-07-23 10:49:51 +05:30
..
api	Changed VirtualMachineProfile to be non-generic. From here on VirtualMachineManager will only manage vm instance. It doesn't understand the difference between different types of VMs. This makes the vmsync code to be generic across all vms.	2013-07-22 11:48:11 -07:00
components-api	Added missing files	2013-07-16 11:24:21 -07:00
compute	CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms	2013-02-20 16:42:56 +05:30
network	CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms	2013-02-20 16:42:56 +05:30
orchestration	Changed virtual machine stop to use uuid	2013-07-22 20:06:04 -07:00
planning/src/org/apache/cloudstack/platform/planning	Added engine	2012-11-05 09:14:14 -08:00
schema	don't update VM state if the state doesn't really change. updating VM state increases the update count, which might cause real VM update fail	2013-07-22 15:56:37 -07:00
service	CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms	2013-02-20 16:42:56 +05:30
storage	CLOUDSTACK-3708, Migration of a volume attached to a running instance isn't working (Storage motion).	2013-07-23 10:49:51 +05:30
pom.xml	integration test is passed again	2013-05-12 14:41:06 -07:00