mike-tutkowski commented on issue #2761: Add managed storage pool constraints to MigrateWithVolume API method URL: https://github.com/apache/cloudstack/pull/2761#issuecomment-408540260 I’ll have to take a look when I’m back at my computer. From memory, though, I thought there was only two checks in that managed-storage method: If it’s not managed storage, return. If it is managed storage, the ID of the current and target storage pools must be the same. I’m not sure how that breaks the use case you mentioned. I can take a look later, though. On Jul 27, 2018, at 2:59 PM, Rafael Weingärtner <[email protected]<mailto:[email protected]>> wrote: Yes, the second link has only one method. The problem with the second suggestion is that it causes a bug as I mentioned. I mean, it will create a situation where it will not allow the migration of VMs with volumes in cluster-wide managed storage, even though it should be supported. Imagine a VM that has two volumes one placed in local storage and other in a managed storage. The `migrateVirtualMachineWithVolume' is called to migrate the VM between hosts of the same cluster. The migration should be supported as long as the target host has a local storage to receive one of the volumes, and the other one does not need to be migrated as it is in a cluster-wide managed storage and the target host is in the same cluster as the source host. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://github.com/apache/cloudstack/pull/2761#issuecomment-408537220>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AC4SH7bzQEIpd3Q1sfF4IvzKtrjZnIH7ks5uK38XgaJpZM4Va8cN>.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
