cloudstack

History

Anshul Gangwar af37ade9e3 CLOUDSTACK-6830: Fixed [hyper-v] during VM migration, volumes on zone wide primary store requires storage migration resulting in failure of VM migration. This also improves the hostsformigration api. Firstly we were trying to list all hosts and then finding suitable storage pools for all volumes and then we were checking whether vm migration requires storage migration to that host. Now the process is updated. We are checking for only those volumes which are not in zone wide primary store. We are verifying by comparing volumes->poolid->clusterid to host clusterid. If it uses local or clusterids are different then verifying whether host has suitable storage pools for the volume of the vm to be migrated too. (cherry picked from commit `64153a4371`) Conflicts: engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java	2014-06-23 09:56:17 +02:00
..
com/cloud	CLOUDSTACK-6830: Fixed [hyper-v] during VM migration, volumes on zone wide primary	2014-06-23 09:56:17 +02:00
org/apache/cloudstack/engine	CLOUDSTACK-6865 , CLOUDSTACK-6868: [hyperv] while attaching the volume we were changing the volume's Image format to hypervisor's default Image format, hence it was failing to find the volume with vhdx format. Now changed the behavior to set Image Format for volume only when it is not set	2014-06-13 12:41:18 +02:00

Anshul Gangwar af37ade9e3 CLOUDSTACK-6830: Fixed [hyper-v] during VM migration, volumes on zone wide primary

store requires storage migration resulting in failure of VM migration. This also
improves the hostsformigration api. Firstly we were trying to list all hosts and
then finding suitable storage pools for all volumes and then we were checking
whether vm migration requires storage migration to that host. Now the process is
updated. We are checking for only those volumes which are not in zone wide primary
store. We are verifying by comparing volumes->poolid->clusterid to host clusterid.
If it uses local or clusterids are different then verifying whether host has
suitable storage pools for the volume of the vm to be migrated too.

(cherry picked from commit 64153a4371)

Conflicts:
	engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java

2014-06-23 09:56:17 +02:00

com/cloud CLOUDSTACK-6830: Fixed [hyper-v] during VM migration, volumes on zone wide primary 2014-06-23 09:56:17 +02:00

org/apache/cloudstack/engine CLOUDSTACK-6865 , CLOUDSTACK-6868: [hyperv] while attaching the volume we were changing the volume's Image format to hypervisor's default Image format, hence it was failing to find the volume with vhdx format. Now changed the behavior to set Image Format for volume only when it is not set 2014-06-13 12:41:18 +02:00