Sateesh Chodapuneedi 893d524d57 CLOUDSTACK-4375 VM Migration is failing from one cluster to another cluster. ... Updating the fix to cover one more scenario when user directly calls API migrateVirtualMachineWithVolume. If currentPool is accessible to destination host, skip calling allocators and move on to next volume to process. This means if user calls migrateVirtualMachineWithVolume API where all volumes of VM are accessible on specified target host, then API fails as there is no storage migration involved. Instead user should call migrateVirtualMachine API. Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>		2013-08-20 04:25:46 +05:30
..
conf	conf: Add a @ so @MSUSER@ is replaced by "cloud"	2013-04-03 16:54:00 +02:00
resources/com/cloud/upgrade	CLOUDSTACK-1818: add a missing file that is missed in previous patch	2013-03-29 11:12:36 -07:00
scripts	License header updates for the server folder.	2012-08-03 09:41:27 -04:00
src	CLOUDSTACK-4375 VM Migration is failing from one cluster to another cluster.	2013-08-20 04:25:46 +05:30
test	CLOUDSTACK-4068 scaling up user vm and system vm is failing with NPE if current service offering is deleted	2013-08-16 15:10:36 +05:30
pom.xml	Added the git commit and branch to war file	2013-07-11 17:37:36 -07:00